View on GitHub

DNSViz: A DNS visualization tool

huduser.gov

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

RRset statusRRset status

Secure (5)
  • huduser.gov/A
  • huduser.gov/MX
  • huduser.gov/NS
  • huduser.gov/SOA
  • huduser.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (10)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 60955)
  • gov/DNSKEY (alg 8, id 50011)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • huduser.gov/DNSKEY (alg 5, id 40890)
  • huduser.gov/DNSKEY (alg 5, id 50806)
  • huduser.gov/DNSKEY (alg 8, id 28312)
  • huduser.gov/DNSKEY (alg 8, id 5958)
  • huduser.gov/DS (alg 8, id 28312)

Delegation statusDelegation status

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

NoticesNotices

Warnings (23)
  • RRSIG huduser.gov/A alg 5, id 40890: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG huduser.gov/DNSKEY alg 5, id 40890: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG huduser.gov/DNSKEY alg 5, id 40890: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG huduser.gov/DNSKEY alg 5, id 40890: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG huduser.gov/DNSKEY alg 5, id 40890: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG huduser.gov/DNSKEY alg 5, id 50806: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG huduser.gov/DNSKEY alg 5, id 50806: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG huduser.gov/DNSKEY alg 5, id 50806: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG huduser.gov/DNSKEY alg 5, id 50806: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG huduser.gov/MX alg 5, id 40890: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG huduser.gov/NS alg 5, id 40890: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG huduser.gov/SOA alg 5, id 40890: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG huduser.gov/TXT alg 5, id 40890: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • huduser.gov/DNSKEY (alg 5, id 40890): 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. (2600:2000:2210::16, 2600:2000:2220::16, 2600:2000:2230::16, 2600:2000:2240::16, UDP_-_EDNS0_4096_D_KN)
  • huduser.gov/DNSKEY (alg 5, id 50806): 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. (2600:2000:2210::16, 2600:2000:2220::16, 2600:2000:2230::16, 2600:2000:2240::16, UDP_-_EDNS0_4096_D_KN)
  • huduser.gov/DNSKEY (alg 8, id 28312): 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. (2600:2000:2210::16, 2600:2000:2220::16, 2600:2000:2230::16, 2600:2000:2240::16, UDP_-_EDNS0_4096_D_KN)
  • huduser.gov/DNSKEY (alg 8, id 5958): 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. (2600:2000:2210::16, 2600:2000:2220::16, 2600:2000:2230::16, 2600:2000:2240::16, UDP_-_EDNS0_4096_D_KN)
  • huduser.gov/TXT: 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. (2600:2000:2210::16, 2600:2000:2220::16, 2600:2000:2230::16, 2600:2000:2240::16, UDP_-_EDNS0_4096_D_KN)
  • huduser.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • huduser.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • g914usopva.huduser.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • huduser.gov/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
  • huduser.gov/DNSKEY 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