View on GitHub

DNSViz: A DNS visualization tool

nsa.gov

Updated: 2024-08-23 06:51:23 UTC (27 days ago) Update now
« 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 (12)
  • nsa.gov/A
  • nsa.gov/A
  • nsa.gov/A
  • nsa.gov/A
  • nsa.gov/A
  • nsa.gov/A
  • nsa.gov/A
  • nsa.gov/MX
  • nsa.gov/NS
  • nsa.gov/NSEC3PARAM
  • nsa.gov/SOA
  • nsa.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (10)
  • ./DNSKEY (alg 8, id 20038)
  • ./DNSKEY (alg 8, id 20326)
  • gov/DNSKEY (alg 13, id 2536)
  • gov/DNSKEY (alg 13, id 35496)
  • gov/DS (alg 13, id 2536)
  • nsa.gov/DNSKEY (alg 7, id 29356)
  • nsa.gov/DNSKEY (alg 7, id 60584)
  • nsa.gov/DNSKEY (alg 7, id 62806)
  • nsa.gov/DNSKEY (alg 7, id 6668)
  • nsa.gov/DS (alg 7, id 29356)

Delegation statusDelegation status

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

NoticesNotices

Errors (5)
  • nsa.gov/CDS has errors; select the "Denial of existence" DNSSEC option to see them.
  • nsa.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • 3vcra.rj3v0.nsa.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • nsa.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • nsa.gov/CDNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (34)
  • ./DNSKEY (alg 8, id 20038): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
  • ./DNSKEY (alg 8, id 20326): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
  • RRSIG nsa.gov/A alg 7, id 6668: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nsa.gov/A alg 7, id 6668: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nsa.gov/A alg 7, id 6668: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nsa.gov/A alg 7, id 6668: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nsa.gov/A alg 7, id 6668: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nsa.gov/A alg 7, id 6668: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nsa.gov/A alg 7, id 6668: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nsa.gov/DNSKEY alg 7, id 29356: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nsa.gov/DNSKEY alg 7, id 29356: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nsa.gov/DNSKEY alg 7, id 29356: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nsa.gov/DNSKEY alg 7, id 29356: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nsa.gov/DNSKEY alg 7, id 62806: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nsa.gov/DNSKEY alg 7, id 62806: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nsa.gov/DNSKEY alg 7, id 62806: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nsa.gov/DNSKEY alg 7, id 62806: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nsa.gov/MX alg 7, id 6668: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nsa.gov/NS alg 7, id 6668: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nsa.gov/NSEC3PARAM alg 7, id 6668: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nsa.gov/SOA alg 7, id 6668: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nsa.gov/TXT alg 7, id 6668: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • gov/DS (alg 13, id 2536): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
  • gov/DS (alg 13, id 2536): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
  • nsa.gov/DNSKEY (alg 7, id 29356): 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:f000::43, UDP_-_EDNS0_4096_D_KN)
  • nsa.gov/DNSKEY (alg 7, id 60584): 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:f000::43, UDP_-_EDNS0_4096_D_KN)
  • nsa.gov/DNSKEY (alg 7, id 62806): 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:f000::43, UDP_-_EDNS0_4096_D_KN)
  • nsa.gov/DNSKEY (alg 7, id 6668): 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:f000::43, UDP_-_EDNS0_4096_D_KN)
  • nsa.gov/CDS has warnings; select the "Denial of existence" DNSSEC option to see them.
  • nsa.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • nsa.gov/CDNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • nsa.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • nsa.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • 3vcra.rj3v0.nsa.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