View on GitHub

DNSViz: A DNS visualization tool

usaspending.gov

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

RRset statusRRset status

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

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (11)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 42351)
  • gov/DNSKEY (alg 8, id 15489)
  • gov/DNSKEY (alg 8, id 27306)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • usaspending.gov/DNSKEY (alg 8, id 2647)
  • usaspending.gov/DNSKEY (alg 8, id 5328)
  • usaspending.gov/DS (alg 8, id 2647)
  • usaspending.gov/DS (alg 8, id 2647)

Delegation statusDelegation status

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

NoticesNotices

Errors (4)
  • ./DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (2001:500:12::d0d, UDP_-_EDNS0_512_D_KN)
  • csjv0pnxby.usaspending.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • usaspending.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
  • usaspending.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (13)
  • ./DNSKEY (alg 8, id 20326): 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. (2001:500:12::d0d, UDP_-_EDNS0_4096_D_KN)
  • ./DNSKEY (alg 8, id 42351): 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. (2001:500:12::d0d, UDP_-_EDNS0_4096_D_KN)
  • 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.
  • usaspending.gov/DS (alg 8, id 2647): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • usaspending.gov/DS (alg 8, id 2647): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • usaspending.gov/DS (alg 8, id 2647): 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.
  • usaspending.gov/DS (alg 8, id 2647): 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.
  • csjv0pnxby.usaspending.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • usaspending.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
  • usaspending.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