View on GitHub

DNSViz: A DNS visualization tool

ustda.gov

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

RRset statusRRset status

Secure (7)
  • ustda.gov/A
  • ustda.gov/AAAA
  • ustda.gov/MX
  • ustda.gov/NS
  • ustda.gov/NSEC3PARAM
  • ustda.gov/SOA
  • ustda.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (11)
  • ./DNSKEY (alg 8, id 18733)
  • ./DNSKEY (alg 8, id 20326)
  • gov/DNSKEY (alg 8, id 56278)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • ustda.gov/DNSKEY (alg 10, id 13227)
  • ustda.gov/DNSKEY (alg 10, id 33666)
  • ustda.gov/DNSKEY (alg 10, id 3456)
  • ustda.gov/DNSKEY (alg 10, id 56547)
  • ustda.gov/DS (alg 10, id 3456)
  • ustda.gov/DS (alg 10, id 56547)

Delegation statusDelegation status

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

NoticesNotices

Errors (2)
  • a5iqmejw8u.ustda.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • ustda.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (22)
  • RRSIG ustda.gov/A alg 10, id 13227: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG ustda.gov/AAAA alg 10, id 13227: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG ustda.gov/DNSKEY alg 10, id 3456: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG ustda.gov/DNSKEY alg 10, id 3456: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG ustda.gov/DNSKEY alg 10, id 3456: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG ustda.gov/DNSKEY alg 10, id 3456: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG ustda.gov/DNSKEY alg 10, id 56547: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG ustda.gov/DNSKEY alg 10, id 56547: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG ustda.gov/DNSKEY alg 10, id 56547: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG ustda.gov/DNSKEY alg 10, id 56547: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG ustda.gov/MX alg 10, id 13227: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG ustda.gov/NS alg 10, id 13227: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG ustda.gov/NSEC3PARAM alg 10, id 13227: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG ustda.gov/SOA alg 10, id 13227: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG ustda.gov/TXT alg 10, id 13227: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • ustda.gov/DNSKEY (alg 10, id 13227): 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:1480:b000::40, UDP_-_EDNS0_4096_D_KN)
  • ustda.gov/DNSKEY (alg 10, id 33666): 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:1480:b000::40, UDP_-_EDNS0_4096_D_KN)
  • ustda.gov/DNSKEY (alg 10, id 3456): 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:1480:b000::40, UDP_-_EDNS0_4096_D_KN)
  • ustda.gov/DNSKEY (alg 10, id 56547): 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:1480:b000::40, UDP_-_EDNS0_4096_D_KN)
  • a5iqmejw8u.ustda.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • ustda.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • ustda.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