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

Secure (3)
  • postbank.de/NS
  • postbank.de/SOA
  • postbank.de/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (18)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 9799)
  • de/DNSKEY (alg 8, id 26019)
  • de/DNSKEY (alg 8, id 26755)
  • de/DNSKEY (alg 8, id 58473)
  • de/DS (alg 8, id 26755)
  • postbank.de/DNSKEY (alg 7, id 12287)
  • postbank.de/DNSKEY (alg 7, id 29904)
  • postbank.de/DNSKEY (alg 7, id 30588)
  • postbank.de/DNSKEY (alg 7, id 30713)
  • postbank.de/DNSKEY (alg 7, id 37863)
  • postbank.de/DNSKEY (alg 7, id 46596)
  • postbank.de/DNSKEY (alg 7, id 47438)
  • postbank.de/DNSKEY (alg 7, id 63119)
  • postbank.de/DS (alg 7, id 29904)
  • postbank.de/DS (alg 7, id 30588)
  • postbank.de/DS (alg 7, id 37863)
  • postbank.de/DS (alg 7, id 46596)

Delegation statusDelegation status

Secure (2)
  • . to de
  • de to postbank.de

NoticesNotices

Errors (16)
  • postbank.de zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (185.157.33.32)
  • 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, 185.157.35.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, 185.157.35.19, UDP_-_EDNS0_512_D_KN)
  • postbank.de/MX: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (185.157.33.19, 185.157.35.19, UDP_-_NOEDNS_)
  • 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, 185.157.35.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, UDP_-_NOEDNS_)
  • postbank.de/NSEC3PARAM: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (185.157.33.19, 185.157.35.19, UDP_-_NOEDNS_)
  • postbank.de/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (185.157.35.19, TCP_-_EDNS0_4096_D_N)
  • 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_)
  • 73euhlk5is.postbank.de/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • postbank.de/DNSKEY 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 (52)
  • RRSIG postbank.de/DNSKEY 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/DNSKEY 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/DNSKEY 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/DNSKEY 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/DNSKEY 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/DNSKEY 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/DNSKEY 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/DNSKEY 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/DNSKEY alg 7, id 29904: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG postbank.de/DNSKEY alg 7, id 29904: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG postbank.de/DNSKEY alg 7, id 29904: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG postbank.de/DNSKEY alg 7, id 29904: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG postbank.de/DNSKEY alg 7, id 29904: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG postbank.de/DNSKEY alg 7, id 29904: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG postbank.de/DNSKEY alg 7, id 29904: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG postbank.de/DNSKEY alg 7, id 29904: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG postbank.de/DNSKEY alg 7, id 37863: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG postbank.de/DNSKEY alg 7, id 37863: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG postbank.de/DNSKEY alg 7, id 37863: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG postbank.de/DNSKEY alg 7, id 37863: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG postbank.de/DNSKEY alg 7, id 37863: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG postbank.de/DNSKEY alg 7, id 37863: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG postbank.de/DNSKEY alg 7, id 37863: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG postbank.de/DNSKEY alg 7, id 37863: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG postbank.de/DNSKEY 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/DNSKEY 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/DNSKEY 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/DNSKEY 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/DNSKEY 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/DNSKEY 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/DNSKEY 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/DNSKEY 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/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 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 12287: The value of the Signature Inception field of the RRSIG RR (2022-02-08 15:50:33+00:00) is within possible clock skew range (3 minutes) of the current time (2022-02-08 15:54:04+00:00). See RFC 4035, Sec. 5.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/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/NS alg 7, id 63119: The value of the Signature Inception field of the RRSIG RR (2022-02-08 15:50:33+00:00) is within possible clock skew range (3 minutes) of the current time (2022-02-08 15: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 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 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 12287: The value of the Signature Inception field of the RRSIG RR (2022-02-08 15:50:55+00:00) is within possible clock skew range (3 minutes) of the current time (2022-02-08 15:54:04+00:00). See RFC 4035, Sec. 5.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.
  • 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.
  • 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.
  • RRSIG postbank.de/SOA alg 7, id 63119: The value of the Signature Inception field of the RRSIG RR (2022-02-08 15:50:55+00:00) is within possible clock skew range (3 minutes) of the current time (2022-02-08 15:54:04+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG postbank.de/TXT 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/TXT alg 7, id 63119: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • postbank.de/NS: No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (185.157.33.19, UDP_-_EDNS0_4096_D_KN)
  • postbank.de/SOA: No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (185.157.35.19, UDP_-_EDNS0_4096_D_KN)
  • postbank.de/SOA: No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (185.157.35.19, UDP_-_EDNS0_4096_D_KN)
  • postbank.de/DNSKEY 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