View on GitHub

DNSViz: A DNS visualization tool

treasurydirect.gov

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

RRset statusRRset status

Secure (6)
  • treasurydirect.gov/A
  • treasurydirect.gov/AAAA
  • treasurydirect.gov/MX
  • treasurydirect.gov/NS
  • treasurydirect.gov/SOA
  • treasurydirect.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (11)
  • ./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)
  • treasurydirect.gov/DNSKEY (alg 8, id 39876)
  • treasurydirect.gov/DNSKEY (alg 8, id 44890)
  • treasurydirect.gov/DNSKEY (alg 8, id 58155)
  • treasurydirect.gov/DS (alg 8, id 44890)
  • treasurydirect.gov/DS (alg 8, id 44890)

Delegation statusDelegation status

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

NoticesNotices

Errors (14)
  • gov to treasurydirect.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. (166.123.208.249, 2610:108:4000:100a::249, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • gov to treasurydirect.gov: The DS RRset for the zone included algorithm 8 (RSASHA256), but no DS RR matched a DNSKEY with algorithm 8 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (166.123.208.249, 2610:108:4000:100a::249, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • treasurydirect.gov/A: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (166.123.208.249, 2610:108:4000:100a::249, UDP_-_EDNS0_4096_D_K)
  • treasurydirect.gov/AAAA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (166.123.208.249, 2610:108:4000:100a::249, UDP_-_EDNS0_4096_D_K)
  • treasurydirect.gov/DNSKEY (alg 8, id 39876): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (166.123.208.249, 2610:108:4000:100a::249, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • treasurydirect.gov/DNSKEY (alg 8, id 44890): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (166.123.208.249, 2610:108:4000:100a::249, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • treasurydirect.gov/DNSKEY (alg 8, id 58155): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (166.123.208.249, 2610:108:4000:100a::249, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • treasurydirect.gov/MX: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (166.123.208.249, 2610:108:4000:100a::249, UDP_-_EDNS0_4096_D_K)
  • treasurydirect.gov/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (166.123.208.249, 2610:108:4000:100a::249, UDP_-_EDNS0_4096_D_K)
  • treasurydirect.gov/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (166.123.208.249, 2610:108:4000:100a::249, TCP_-_EDNS0_4096_D, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K_0x20)
  • treasurydirect.gov/TXT: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (166.123.208.249, 2610:108:4000:100a::249, UDP_-_EDNS0_4096_D_K)
  • uyixp52sbj.treasurydirect.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • treasurydirect.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • treasurydirect.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (14)
  • 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)
  • treasurydirect.gov/DS (alg 8, id 44890): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • treasurydirect.gov/DS (alg 8, id 44890): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • treasurydirect.gov/DS (alg 8, id 44890): 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.
  • treasurydirect.gov/DS (alg 8, id 44890): 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.
  • uyixp52sbj.treasurydirect.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • treasurydirect.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