View on GitHub

DNSViz: A DNS visualization tool

usa.gov

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

RRset statusRRset status

Secure (5)
  • usa.gov/A
  • usa.gov/AAAA
  • usa.gov/NS
  • usa.gov/SOA
  • usa.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (10)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 46594)
  • gov/DNSKEY (alg 8, id 26665)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • usa.gov/DNSKEY (alg 8, id 13555)
  • usa.gov/DNSKEY (alg 8, id 30165)
  • usa.gov/DS (alg 8, id 13555)
  • usa.gov/DS (alg 8, id 13555)

Delegation statusDelegation status

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

NoticesNotices

Errors (3)
  • usa.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
  • usa.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • uj1xifrq8c.usa.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (12)
  • gov/DS (alg 8, id 7698): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • gov/DS (alg 8, id 7698): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • gov/DS (alg 8, id 7698): 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/DS (alg 8, id 7698): 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/DS (alg 8, id 7698): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (192.112.36.4, UDP_-_EDNS0_4096_D_K)
  • gov/DS (alg 8, id 7698): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (192.112.36.4, UDP_-_EDNS0_4096_D_K)
  • gov/DS (alg 8, id 7698): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (192.112.36.4, UDP_-_EDNS0_4096_D_K)
  • gov/DS (alg 8, id 7698): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (192.112.36.4, UDP_-_EDNS0_4096_D_K)
  • usa.gov/DS (alg 8, id 13555): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • usa.gov/DS (alg 8, id 13555): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • usa.gov/DS (alg 8, id 13555): 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.
  • usa.gov/DS (alg 8, id 13555): 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.

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