View on GitHub

DNSViz: A DNS visualization tool

www.zgt.de

Updated: 2023-04-04 20:07:20 UTC (552 days ago) Update now
« Previous analysis | Next analysis »
DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
  10. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Insecure (1)
  • zgt.de/SOA
Secure (2)
  • de/SOA
  • de/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (8)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 60955)
  • ./DNSKEY (alg 8, id 951)
  • NSEC3 proving non-existence of zgt.de/DS
  • de/DNSKEY (alg 8, id 26755)
  • de/DNSKEY (alg 8, id 46020)
  • de/DNSKEY (alg 8, id 64956)
  • de/DS (alg 8, id 26755)

Delegation statusDelegation status

Lame (1)
  • zgt.de to www.zgt.de
Insecure (1)
  • de to zgt.de
Secure (1)
  • . to de

NoticesNotices

Errors (20)
  • NSEC3 proving non-existence of zgt.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 zgt.de/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • de zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:678:2::53)
  • www.zgt.de zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (82.145.6.100, 89.246.87.100)
  • www.zgt.de zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (82.145.6.100, 89.246.87.100)
  • www.zgt.de zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (134.91.235.100)
  • www.zgt.de/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (134.91.235.100, UDP_-_NOEDNS_)
  • www.zgt.de/A: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (82.145.6.100, 89.246.87.100, UDP_-_EDNS0_4096_D_KN)
  • www.zgt.de/AAAA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (82.145.6.100, 89.246.87.100, UDP_-_EDNS0_4096_D_KN)
  • www.zgt.de/DNSKEY: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (82.145.6.100, 89.246.87.100, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • www.zgt.de/MX: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (82.145.6.100, 89.246.87.100, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • www.zgt.de/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (134.91.235.100, UDP_-_NOEDNS_)
  • www.zgt.de/NS: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (82.145.6.100, 89.246.87.100, UDP_-_EDNS0_4096_D_KN)
  • www.zgt.de/NSEC3PARAM: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (82.145.6.100, 89.246.87.100, UDP_-_EDNS0_4096_D_KN)
  • www.zgt.de/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (82.145.6.100, 89.246.87.100, TCP_-_EDNS0_4096_D_N)
  • www.zgt.de/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (82.145.6.100, 89.246.87.100, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • www.zgt.de/TXT: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (82.145.6.100, 89.246.87.100, UDP_-_EDNS0_4096_D_KN)
  • www.zgt.de/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • jbtam81yq7.www.zgt.de/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • www.zgt.de/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (7)
  • NSEC3 proving non-existence of zgt.de/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of zgt.de/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • de to zgt.de: The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2a02:568:fe02::de, UDP_-_EDNS0_4096_D_KN)
  • de/DNSKEY (alg 8, id 26755): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2a02:568:fe02::de, UDP_-_EDNS0_4096_D_KN)
  • de/DNSKEY (alg 8, id 46020): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2a02:568:fe02::de, UDP_-_EDNS0_4096_D_KN)
  • de/DNSKEY (alg 8, id 64956): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2a02:568:fe02::de, UDP_-_EDNS0_4096_D_KN)
  • de/DNSKEY: The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2a02:568:fe02::de, UDP_-_EDNS0_512_D_KN)

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