View on GitHub

DNSViz: A DNS visualization tool

dot.gov

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

RRset statusRRset status

Secure (6)
  • dot.gov/A
  • dot.gov/MX
  • dot.gov/NS
  • dot.gov/NSEC3PARAM
  • dot.gov/SOA
  • dot.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (10)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 26838)
  • dot.gov/DNSKEY (alg 8, id 23316)
  • dot.gov/DNSKEY (alg 8, id 49053)
  • dot.gov/DNSKEY (alg 8, id 49516)
  • dot.gov/DS (alg 8, id 49516)
  • dot.gov/DS (alg 8, id 49516)
  • gov/DNSKEY (alg 8, id 57735)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)

Delegation statusDelegation status

Secure (2)
  • . to gov
  • gov to dot.gov

NoticesNotices

Errors (8)
  • dot.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (204.68.194.100, 204.68.194.200, 2001:19e8:d::100, 2001:19e8:d::200)
  • dot.gov/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (204.68.194.100, 204.68.194.200, 2001:19e8:d::100, UDP_-_NOEDNS_)
  • dot.gov/A: No response was received from the server over UDP (tried 15 times). See RFC 1035, Sec. 4.2. (2001:19e8:d::200, UDP_-_EDNS0_4096_D)
  • dot.gov/NS: No response was received from the server over UDP (tried 11 times). See RFC 1035, Sec. 4.2. (2001:19e8:d::200, UDP_-_EDNS0_4096_D_KN)
  • dot.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (204.68.194.100, 204.68.194.200, 2001:19e8:d::100, UDP_-_NOEDNS_)
  • km5g0s3cne.dot.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • dot.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • dot.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (10)
  • dot.gov/DS (alg 8, id 49516): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • dot.gov/DS (alg 8, id 49516): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • dot.gov/DS (alg 8, id 49516): 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.
  • dot.gov/DS (alg 8, id 49516): 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 dot.gov: Authoritative AAAA records exist for edns1.dot.gov, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • gov to dot.gov: Authoritative AAAA records exist for edns2.dot.gov, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • gov to dot.gov: Authoritative AAAA records exist for edns3.dot.gov, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • km5g0s3cne.dot.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • dot.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • dot.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