View on GitHub

DNSViz: A DNS visualization tool

glb.cdc.gov

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

RRset statusRRset status

Secure (4)
  • glb.cdc.gov/NS
  • glb.cdc.gov/NSEC3PARAM
  • glb.cdc.gov/NSEC3PARAM
  • glb.cdc.gov/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (14)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 9799)
  • cdc.gov/DNSKEY (alg 7, id 49888)
  • cdc.gov/DNSKEY (alg 7, id 5492)
  • cdc.gov/DNSKEY (alg 7, id 56243)
  • cdc.gov/DS (alg 7, id 49888)
  • cdc.gov/DS (alg 7, id 49888)
  • glb.cdc.gov/DNSKEY (alg 7, id 11349)
  • glb.cdc.gov/DNSKEY (alg 7, id 8477)
  • glb.cdc.gov/DS (alg 7, id 11349)
  • gov/DNSKEY (alg 8, id 6229)
  • gov/DNSKEY (alg 8, id 7030)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)

Delegation statusDelegation status

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

NoticesNotices

Errors (8)
  • glb.cdc.gov zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (198.246.110.76, 198.246.125.102)
  • glb.cdc.gov/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (198.246.110.76, 198.246.125.102, TCP_-_EDNS0_4096_D_N)
  • glb.cdc.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • glb.cdc.gov/TXT has errors; select the "Denial of existence" DNSSEC option to see them.
  • glb.cdc.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • glb.cdc.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
  • glb.cdc.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • q95zfs61jk.glb.cdc.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (35)
  • RRSIG cdc.gov/DNSKEY alg 7, id 49888: 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 49888: 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 49888: 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 56243: 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 56243: 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 56243: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG glb.cdc.gov/DNSKEY alg 7, id 11349: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG glb.cdc.gov/DNSKEY alg 7, id 11349: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG glb.cdc.gov/DNSKEY alg 7, id 8477: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG glb.cdc.gov/DNSKEY alg 7, id 8477: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG glb.cdc.gov/DS alg 7, id 56243: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG glb.cdc.gov/NS alg 7, id 8477: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG glb.cdc.gov/NS alg 7, id 8477: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG glb.cdc.gov/NSEC3PARAM alg 7, id 8477: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG glb.cdc.gov/NSEC3PARAM alg 7, id 8477: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG glb.cdc.gov/NSEC3PARAM alg 7, id 8477: The value of the Signature Inception field of the RRSIG RR (2022-01-13 18:45:18+00:00) is within possible clock skew range (8 seconds) of the current time (2022-01-13 18:45:26+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG glb.cdc.gov/NSEC3PARAM alg 7, id 8477: The value of the Signature Inception field of the RRSIG RR (2022-01-13 18:45:18+00:00) is within possible clock skew range (8 seconds) of the current time (2022-01-13 18:45:26+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG glb.cdc.gov/SOA alg 7, id 8477: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG glb.cdc.gov/SOA alg 7, id 8477: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • cdc.gov/DS (alg 7, id 49888): 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 49888): 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 49888): 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 49888): 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.
  • glb.cdc.gov/DS (alg 7, id 11349): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • glb.cdc.gov/DS (alg 7, id 11349): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • 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.
  • glb.cdc.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • glb.cdc.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
  • glb.cdc.gov/TXT has warnings; select the "Denial of existence" DNSSEC option to see them.
  • glb.cdc.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • glb.cdc.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • glb.cdc.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • glb.cdc.gov/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
  • q95zfs61jk.glb.cdc.gov/A 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