View on GitHub

DNSViz: A DNS visualization tool

www.cdc.gov

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

RRset statusRRset status

Bogus (3)
  • akam.cdc.gov/SOA
  • www.akam.cdc.gov/A (NXDOMAIN)
  • www.akam.cdc.gov/AAAA (NXDOMAIN)
Secure (5)
  • www.akam.cdc.gov/A
  • www.akam.cdc.gov/A
  • www.akam.cdc.gov/AAAA
  • www.akam.cdc.gov/AAAA
  • www.cdc.gov/CNAME

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (14)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 42351)
  • akam.cdc.gov/DNSKEY (alg 10, id 1993)
  • akam.cdc.gov/DNSKEY (alg 10, id 3510)
  • akam.cdc.gov/DNSKEY (alg 10, id 4524)
  • akam.cdc.gov/DNSKEY (alg 10, id 6393)
  • akam.cdc.gov/DS (alg 10, id 1993)
  • cdc.gov/DNSKEY (alg 7, id 42473)
  • cdc.gov/DNSKEY (alg 7, id 65139)
  • cdc.gov/DS (alg 7, id 65139)
  • cdc.gov/DS (alg 7, id 65139)
  • gov/DNSKEY (alg 8, id 27306)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)

Delegation statusDelegation status

Secure (3)
  • . to gov
  • cdc.gov to akam.cdc.gov
  • gov to cdc.gov

NoticesNotices

Errors (8)
  • akam.cdc.gov/DNSKEY (alg 10, id 1993): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (198.246.96.61, 198.246.96.92, 198.246.125.10, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • akam.cdc.gov/DNSKEY (alg 10, id 6393): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (198.246.96.61, 198.246.96.92, 198.246.125.10, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • akam.cdc.gov/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (198.246.96.61, 198.246.96.92, 198.246.125.10, UDP_-_EDNS0_4096_D_KN)
  • cdc.gov to akam.cdc.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. (198.246.96.61, 198.246.96.92, 198.246.125.10, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • cdc.gov to akam.cdc.gov: The DS RRset for the zone included algorithm 10 (RSASHA512), but no DS RR matched a DNSKEY with algorithm 10 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (198.246.96.61, 198.246.96.92, 198.246.125.10, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • www.akam.cdc.gov/A (NXDOMAIN): No NSEC RR(s) were returned to validate the NXDOMAIN response. See RFC 4035, Sec. 3.1.3.2, RFC 5155, Sec. 7.2.2. (198.246.96.61, 198.246.96.92, 198.246.125.10, UDP_-_EDNS0_4096_D_KN)
  • www.akam.cdc.gov/AAAA (NXDOMAIN): No NSEC RR(s) were returned to validate the NXDOMAIN response. See RFC 4035, Sec. 3.1.3.2, RFC 5155, Sec. 7.2.2. (198.246.96.61, 198.246.96.92, 198.246.125.10, UDP_-_EDNS0_4096_D_KN)
  • cdc.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (29)
  • RRSIG akam.cdc.gov/DNSKEY alg 10, id 1993: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG akam.cdc.gov/DNSKEY alg 10, id 1993: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG akam.cdc.gov/DNSKEY alg 10, id 1993: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG akam.cdc.gov/DNSKEY alg 10, id 1993: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG akam.cdc.gov/DNSKEY alg 10, id 4524: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG akam.cdc.gov/DNSKEY alg 10, id 4524: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG akam.cdc.gov/DNSKEY alg 10, id 4524: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG akam.cdc.gov/DNSKEY alg 10, id 4524: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG akam.cdc.gov/DS alg 7, id 42473: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG akam.cdc.gov/DS alg 7, id 42473: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG cdc.gov/DNSKEY alg 7, id 42473: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG cdc.gov/DNSKEY alg 7, id 42473: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG cdc.gov/DNSKEY alg 7, id 65139: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG cdc.gov/DNSKEY alg 7, id 65139: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG www.akam.cdc.gov/A alg 10, id 6393: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG www.akam.cdc.gov/A alg 10, id 6393: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG www.akam.cdc.gov/AAAA alg 10, id 6393: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG www.akam.cdc.gov/AAAA alg 10, id 6393: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG www.cdc.gov/CNAME alg 7, id 42473: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG www.cdc.gov/CNAME alg 7, id 42473: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • akam.cdc.gov/DNSKEY (alg 10, id 3510): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (198.246.96.61, 198.246.96.92, 198.246.125.10, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • akam.cdc.gov/DNSKEY (alg 10, id 4524): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (198.246.96.61, 198.246.96.92, 198.246.125.10, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • cdc.gov/DS (alg 7, id 65139): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • cdc.gov/DS (alg 7, id 65139): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • cdc.gov/DS (alg 7, id 65139): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
  • cdc.gov/DS (alg 7, id 65139): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
  • gov to cdc.gov: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the gov zone): icdc-us-ns1.cdc.gov, icdc-us-ns3.cdc.gov, icdc-us-ns2.cdc.gov See RFC 1034, Sec. 4.2.2.
  • gov to cdc.gov: The following NS name(s) were found in the delegation NS RRset (i.e., in the gov zone), but not in the authoritative NS RRset: auth00.ns.uu.net, auth100.ns.uu.net See RFC 1034, Sec. 4.2.2.
  • cdc.gov/CNAME 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