View on GitHub

DNSViz: A DNS visualization tool

us-cert.gov

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

RRset statusRRset status

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (7)
  • ./DNSKEY (alg 8, id 11019)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 60955)
  • gov/DNSKEY (alg 8, id 50011)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • us-cert.gov/DS (alg 8, id 30121)
Non_existent (1)
  • us-cert.gov/DNSKEY (alg 8, id 30121)

Delegation statusDelegation status

Bogus (1)
  • gov to us-cert.gov
Secure (1)
  • . to gov

NoticesNotices

Errors (18)
  • gov to us-cert.gov: 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.
  • us-cert.gov zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (208.73.184.110, 208.73.191.39)
  • us-cert.gov zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (208.73.184.110, 208.73.191.39)
  • us-cert.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2620:112:5000:1::2)
  • us-cert.gov/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2620:112:5000:1::2, UDP_-_NOEDNS_)
  • us-cert.gov/A: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (208.73.184.110, 208.73.191.39, UDP_-_NOEDNS_)
  • us-cert.gov/AAAA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (208.73.184.110, 208.73.191.39, UDP_-_NOEDNS_)
  • us-cert.gov/DNSKEY: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (208.73.184.110, 208.73.191.39, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
  • us-cert.gov/MX: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (208.73.184.110, 208.73.191.39, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
  • us-cert.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2620:112:5000:1::2, UDP_-_NOEDNS_)
  • us-cert.gov/NS: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (208.73.184.110, 208.73.191.39, UDP_-_NOEDNS_)
  • us-cert.gov/NSEC3PARAM: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (208.73.184.110, 208.73.191.39, UDP_-_NOEDNS_)
  • us-cert.gov/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (208.73.184.110, 208.73.191.39, TCP_-_NOEDNS_)
  • us-cert.gov/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (208.73.184.110, 208.73.191.39, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
  • us-cert.gov/TXT: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (208.73.184.110, 208.73.191.39, UDP_-_NOEDNS_)
  • 6cpdgfu90v.us-cert.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • us-cert.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • us-cert.gov/DNSKEY has errors; 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