View on GitHub

DNSViz: A DNS visualization tool

disa.mil

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

RRset statusRRset status

Secure (5)
  • disa.mil/A
  • disa.mil/NS
  • disa.mil/NSEC3PARAM
  • disa.mil/SOA
  • disa.mil/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (11)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 60955)
  • disa.mil/DNSKEY (alg 8, id 46534)
  • disa.mil/DNSKEY (alg 8, id 6036)
  • disa.mil/DNSKEY (alg 8, id 9934)
  • disa.mil/DS (alg 8, id 46534)
  • disa.mil/DS (alg 8, id 46534)
  • mil/DNSKEY (alg 8, id 1773)
  • mil/DNSKEY (alg 8, id 40318)
  • mil/DNSKEY (alg 8, id 62470)
  • mil/DS (alg 8, id 62470)

Delegation statusDelegation status

Secure (2)
  • . to mil
  • mil to disa.mil

NoticesNotices

Errors (8)
  • disa.mil zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2608:102:0:182d:1001:9012:c00:21, 2608:125:0:1811:1001:9012:f00:21, 2608:145:0:180b:1001:9012:d00:21)
  • disa.mil/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2608:102:0:182d:1001:9012:c00:21, 2608:125:0:1811:1001:9012:f00:21, 2608:145:0:180b:1001:9012:d00:21, UDP_-_NOEDNS_)
  • disa.mil/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2608:102:0:182d:1001:9012:c00:21, 2608:125:0:1811:1001:9012:f00:21, 2608:145:0:180b:1001:9012:d00:21, UDP_-_NOEDNS_)
  • mil/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (2608:4163:1:143::234, UDP_-_EDNS0_512_D_KN)
  • disa.mil/MX has errors; select the "Denial of existence" DNSSEC option to see them.
  • disa.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • esqwuz217h.disa.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • disa.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (16)
  • disa.mil/DS (alg 8, id 46534): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • disa.mil/DS (alg 8, id 46534): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • disa.mil/DS (alg 8, id 46534): 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.
  • disa.mil/DS (alg 8, id 46534): 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.
  • disa.mil/DS (alg 8, id 46534): 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. (2608:140:c:157::234, UDP_-_EDNS0_4096_D_KN)
  • disa.mil/DS (alg 8, id 46534): 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. (2608:140:c:157::234, UDP_-_EDNS0_4096_D_KN)
  • disa.mil/DS (alg 8, id 46534): 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. (2608:140:c:157::234, UDP_-_EDNS0_4096_D_KN)
  • disa.mil/DS (alg 8, id 46534): 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. (2608:140:c:157::234, UDP_-_EDNS0_4096_D_KN)
  • mil to disa.mil: AAAA glue records exist for ns.cybercom.mil, but there are no corresponding authoritative AAAA records. See RFC 1034, Sec. 4.2.2.
  • mil to disa.mil: AAAA glue records exist for ns.jtfgno.mil, but there are no corresponding authoritative AAAA records. See RFC 1034, Sec. 4.2.2.
  • mil to disa.mil: AAAA glue records exist for ns1.csd.disa.mil, but there are no corresponding authoritative AAAA records. See RFC 1034, Sec. 4.2.2.
  • disa.mil/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
  • disa.mil/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • disa.mil/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • esqwuz217h.disa.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • disa.mil/DS 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