View on GitHub

DNSViz: A DNS visualization tool

developmentscout.com

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

RRset statusRRset status

Bogus (6)
  • developmentscout.com/A
  • developmentscout.com/AAAA
  • developmentscout.com/MX
  • developmentscout.com/NS
  • developmentscout.com/SOA
  • developmentscout.com/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (6)
  • ./DNSKEY (alg 8, id 20038)
  • ./DNSKEY (alg 8, id 20326)
  • com/DNSKEY (alg 13, id 19718)
  • com/DNSKEY (alg 13, id 59354)
  • com/DS (alg 13, id 19718)
  • developmentscout.com/DS (alg 8, id 3034)
Non_existent (1)
  • developmentscout.com/DNSKEY (alg 8, id 3034)

Delegation statusDelegation status

Bogus (1)
  • com to developmentscout.com
Secure (1)
  • . to com

NoticesNotices

Errors (24)
  • com to developmentscout.com: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (88.198.229.192, 193.47.99.5, 213.133.100.98, 2001:67c:192c::add:5, 2a01:4f8:0:1::add:1098, 2a01:4f8:0:1::add:2992, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • com to developmentscout.com: The DS RRset for the zone included algorithm 8 (RSASHA256), but no DS RR matched a DNSKEY with algorithm 8 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (88.198.229.192, 193.47.99.5, 213.133.100.98, 2001:67c:192c::add:5, 2a01:4f8:0:1::add:1098, 2a01:4f8:0:1::add:2992, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • developmentscout.com zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (46.105.206.200, 46.105.207.200)
  • developmentscout.com zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (46.105.206.200, 46.105.207.200)
  • developmentscout.com/A: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (88.198.229.192, 193.47.99.5, 213.133.100.98, 2001:67c:192c::add:5, 2a01:4f8:0:1::add:1098, 2a01:4f8:0:1::add:2992, UDP_-_EDNS0_4096_D_KN)
  • developmentscout.com/A: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (46.105.206.200, 46.105.207.200, UDP_-_EDNS0_4096_D_KN)
  • developmentscout.com/AAAA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (88.198.229.192, 193.47.99.5, 213.133.100.98, 2001:67c:192c::add:5, 2a01:4f8:0:1::add:1098, 2a01:4f8:0:1::add:2992, UDP_-_EDNS0_4096_D_KN)
  • developmentscout.com/AAAA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (46.105.206.200, 46.105.207.200, UDP_-_EDNS0_4096_D_KN)
  • developmentscout.com/DNSKEY: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (46.105.206.200, 46.105.207.200, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • developmentscout.com/MX: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (88.198.229.192, 193.47.99.5, 213.133.100.98, 2001:67c:192c::add:5, 2a01:4f8:0:1::add:1098, 2a01:4f8:0:1::add:2992, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • developmentscout.com/MX: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (46.105.206.200, 46.105.207.200, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • developmentscout.com/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (88.198.229.192, 193.47.99.5, 213.133.100.98, 2001:67c:192c::add:5, 2a01:4f8:0:1::add:1098, 2a01:4f8:0:1::add:2992, UDP_-_EDNS0_4096_D_KN)
  • developmentscout.com/NS: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (46.105.206.200, 46.105.207.200, UDP_-_EDNS0_4096_D_KN)
  • developmentscout.com/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (88.198.229.192, 193.47.99.5, 213.133.100.98, 2001:67c:192c::add:5, 2a01:4f8:0:1::add:1098, 2a01:4f8:0:1::add:2992, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • developmentscout.com/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (46.105.206.200, 46.105.207.200, TCP_-_EDNS0_4096_D_N)
  • developmentscout.com/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (46.105.206.200, 46.105.207.200, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • developmentscout.com/TXT: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (88.198.229.192, 193.47.99.5, 213.133.100.98, 2001:67c:192c::add:5, 2a01:4f8:0:1::add:1098, 2a01:4f8:0:1::add:2992, UDP_-_EDNS0_4096_D_KN)
  • developmentscout.com/TXT: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (46.105.206.200, 46.105.207.200, UDP_-_EDNS0_4096_D_KN)
  • en29z.obd4c.developmentscout.com/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • developmentscout.com/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • developmentscout.com/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • developmentscout.com/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
  • developmentscout.com/CDS has errors; select the "Denial of existence" DNSSEC option to see them.
  • developmentscout.com/CDNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (6)
  • ./DNSKEY (alg 8, id 20038): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
  • ./DNSKEY (alg 8, id 20326): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
  • com to developmentscout.com: Authoritative AAAA records exist for hydrogen.ns.hetzner.com, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • com to developmentscout.com: Authoritative AAAA records exist for oxygen.ns.hetzner.com, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • com to developmentscout.com: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the com zone): ns200.anycast.me, dns200.anycast.me See RFC 1034, Sec. 4.2.2.
  • com to developmentscout.com: The following NS name(s) were found in the delegation NS RRset (i.e., in the com zone), but not in the authoritative NS RRset: hydrogen.ns.hetzner.com, oxygen.ns.hetzner.com, helium.ns.hetzner.de See RFC 1034, Sec. 4.2.2.

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