View on GitHub

DNSViz: A DNS visualization tool

itrd.gov

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

RRset statusRRset status

Secure (4)
  • itrd.gov/MX
  • itrd.gov/NS
  • itrd.gov/SOA
  • itrd.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (10)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 47671)
  • gov/DNSKEY (alg 8, id 2706)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • itrd.gov/DNSKEY (alg 5, id 34698)
  • itrd.gov/DNSKEY (alg 5, id 62551)
  • itrd.gov/DNSKEY (alg 8, id 38373)
  • itrd.gov/DNSKEY (alg 8, id 55507)
  • itrd.gov/DS (alg 8, id 55507)

Delegation statusDelegation status

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

NoticesNotices

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