View on GitHub

DNSViz: A DNS visualization tool

postbank.de

DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
  10. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Insecure (3)
  • postbank.de/NS
  • postbank.de/NSEC3PARAM
  • postbank.de/SOA
Secure (3)
  • de/SOA
  • de/SOA
  • de/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (7)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 9799)
  • NSEC3 proving non-existence of postbank.de/DS
  • de/DNSKEY (alg 8, id 26019)
  • de/DNSKEY (alg 8, id 26755)
  • de/DNSKEY (alg 8, id 58473)
  • de/DS (alg 8, id 26755)
Non_existent (2)
  • postbank.de/DNSKEY (alg 7, id 12287)
  • postbank.de/DNSKEY (alg 7, id 63119)

Delegation statusDelegation status

Insecure (1)
  • de to postbank.de
Secure (1)
  • . to de

NoticesNotices

Errors (17)
  • NSEC3 proving non-existence of postbank.de/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of postbank.de/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • postbank.de zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (185.157.33.32, 185.157.35.19)
  • postbank.de zone: There was an error resolving the following NS name(s) to address(es): ns1.postbank.de, ns2.postbank.de, ns3.postbank.de
  • postbank.de/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (185.157.33.19, 185.157.33.32, 185.157.35.19, UDP_-_NOEDNS_)
  • postbank.de/AAAA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (185.157.33.19, UDP_-_NOEDNS_)
  • postbank.de/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (185.157.33.19, UDP_-_NOEDNS_)
  • postbank.de/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (185.157.33.19, UDP_-_EDNS0_512_D_KN)
  • postbank.de/MX: No response was received from the server over TCP (tried 7 times). See RFC 1035, Sec. 4.2. (185.157.33.19, TCP_-_EDNS0_4096_D_KN)
  • postbank.de/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (185.157.33.19, UDP_-_EDNS0_512_D_KN)
  • postbank.de/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (185.157.33.32, 185.157.35.19, UDP_-_NOEDNS_)
  • postbank.de/SOA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (185.157.33.19, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
  • postbank.de/TXT: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (185.157.33.19, UDP_-_NOEDNS_)
  • postbank.de/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • 61gja8itzy.postbank.de/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • postbank.de/DS has errors; select the "Denial of existence" DNSSEC option to see them.
  • postbank.de/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (11)
  • NSEC3 proving non-existence of postbank.de/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of postbank.de/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • RRSIG postbank.de/NS alg 7, id 12287: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG postbank.de/NS alg 7, id 63119: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG postbank.de/NSEC3PARAM alg 7, id 12287: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG postbank.de/NSEC3PARAM alg 7, id 12287: The value of the Signature Inception field of the RRSIG RR (2022-02-10 12:53:54+00:00) is within possible clock skew range (10 seconds) of the current time (2022-02-10 12:54:04+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG postbank.de/NSEC3PARAM alg 7, id 63119: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG postbank.de/NSEC3PARAM alg 7, id 63119: The value of the Signature Inception field of the RRSIG RR (2022-02-10 12:53:54+00:00) is within possible clock skew range (10 seconds) of the current time (2022-02-10 12:54:04+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG postbank.de/SOA alg 7, id 12287: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG postbank.de/SOA alg 7, id 63119: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • postbank.de/DS has warnings; select the "Denial of existence" DNSSEC option to see them.

DNSKEY legend

Full legend
SEP bit setSEP bit set
Revoke bit setRevoke bit set
Trust anchorTrust anchor
Download: png | svg
Warning JavaScript is required to make the graph below interactive.
DNSSEC authentication graph