View on GitHub

DNSViz: A DNS visualization tool

treas.gov

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

RRset statusRRset status

Insecure (8)
  • treas.gov/A
  • treas.gov/AAAA
  • treas.gov/NS
  • treas.gov/NSEC3PARAM
  • treas.gov/NSEC3PARAM
  • treas.gov/NSEC3PARAM
  • treas.gov/SOA
  • treas.gov/TXT
Secure (1)
  • gov/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Insecure (2)
  • treas.gov/DNSKEY (alg 7, id 29864)
  • treas.gov/DNSKEY (alg 7, id 37758)
Secure (6)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 60955)
  • NSEC3 proving non-existence of treas.gov/DS
  • gov/DNSKEY (alg 8, id 50011)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)

Delegation statusDelegation status

Insecure (1)
  • gov to treas.gov
Secure (1)
  • . to gov

NoticesNotices

Errors (9)
  • NSEC3 proving non-existence of treas.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of treas.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • treas.gov/SOA: DNSSEC was effectively downgraded because the response had an invalid RCODE (SERVFAIL) with EDNS enabled. See RFC 6891, Sec. 7, RFC 2671, Sec. 5.3. (172.64.52.110, UDP_-_NOEDNS_)
  • treas.gov/SOA: The DNSSEC records necessary to validate the response could not be retrieved from the server. See RFC 4035, Sec. 3.1.1, RFC 4035, Sec. 3.1.3. (172.64.52.110, UDP_-_EDNS0_4096_D_KN)
  • treas.gov/SOA: The response had an invalid RCODE (SERVFAIL) until EDNS was disabled (however, this server appeared to respond legitimately to other queries with EDNS enabled). See RFC 6891, Sec. 6.2.6. (172.64.52.110, UDP_-_EDNS0_4096_D_KN)
  • 6y2rba3lzk.treas.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • treas.gov/DS has errors; select the "Denial of existence" DNSSEC option to see them.
  • treas.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
  • treas.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (35)
  • NSEC3 proving non-existence of treas.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of treas.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • RRSIG treas.gov/A alg 7, id 29864: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treas.gov/A alg 7, id 29864: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treas.gov/AAAA alg 7, id 29864: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treas.gov/AAAA alg 7, id 29864: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treas.gov/DNSKEY alg 7, id 29864: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treas.gov/DNSKEY alg 7, id 29864: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treas.gov/DNSKEY alg 7, id 29864: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treas.gov/DNSKEY alg 7, id 29864: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treas.gov/DNSKEY alg 7, id 29864: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treas.gov/DNSKEY alg 7, id 29864: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treas.gov/DNSKEY alg 7, id 37758: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treas.gov/DNSKEY alg 7, id 37758: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treas.gov/DNSKEY alg 7, id 37758: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treas.gov/DNSKEY alg 7, id 37758: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treas.gov/DNSKEY alg 7, id 37758: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treas.gov/DNSKEY alg 7, id 37758: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treas.gov/NS alg 7, id 29864: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treas.gov/NS alg 7, id 29864: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treas.gov/NSEC3PARAM alg 7, id 29864: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treas.gov/NSEC3PARAM alg 7, id 29864: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treas.gov/NSEC3PARAM alg 7, id 29864: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treas.gov/SOA alg 7, id 29864: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treas.gov/SOA alg 7, id 29864: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treas.gov/SOA alg 7, id 29864: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treas.gov/TXT alg 7, id 29864: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treas.gov/TXT alg 7, id 29864: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG treas.gov/TXT alg 7, id 29864: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • treas.gov/DNSKEY: The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (172.64.52.110, 172.64.53.149, 2606:4700:52::ac40:346e, 2606:4700:5a::ac40:3595, UDP_-_EDNS0_512_D_KN)
  • treas.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • treas.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
  • treas.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • treas.gov/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
  • 6y2rba3lzk.treas.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