View on GitHub

DNSViz: A DNS visualization tool

dtic.mil

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

RRset statusRRset status

Secure (5)
  • dtic.mil/A
  • dtic.mil/MX
  • dtic.mil/NS
  • dtic.mil/SOA
  • dtic.mil/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (12)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 60955)
  • dtic.mil/DNSKEY (alg 10, id 15680)
  • dtic.mil/DNSKEY (alg 10, id 51611)
  • dtic.mil/DNSKEY (alg 10, id 55959)
  • dtic.mil/DNSKEY (alg 10, id 63261)
  • dtic.mil/DS (alg 10, id 55959)
  • dtic.mil/DS (alg 10, id 55959)
  • mil/DNSKEY (alg 8, id 1773)
  • mil/DNSKEY (alg 8, id 53035)
  • mil/DNSKEY (alg 8, id 62470)
  • mil/DS (alg 8, id 62470)

Delegation statusDelegation status

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

NoticesNotices

Errors (11)
  • dtic.mil zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (140.18.188.250)
  • dtic.mil zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (140.18.189.250)
  • dtic.mil/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (140.18.189.250, UDP_-_NOEDNS_)
  • dtic.mil/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (140.18.188.250, UDP_-_EDNS0_512_D_KN)
  • dtic.mil/NSEC3PARAM: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (140.18.188.250, 140.18.189.250, UDP_-_NOEDNS_)
  • dtic.mil/SOA: No response was received from the server over TCP (tried 4 times). See RFC 1035, Sec. 4.2. (140.18.188.250, 140.18.189.250, TCP_-_EDNS0_4096_D_N)
  • dtic.mil/SOA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (140.18.189.250, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
  • dtic.mil/TXT: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (140.18.188.250, UDP_-_NOEDNS_)
  • dtic.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • dtic.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • 8lcxhwvzq0.dtic.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (26)
  • RRSIG dtic.mil/A alg 10, id 15680: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG dtic.mil/DNSKEY alg 10, id 15680: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG dtic.mil/DNSKEY alg 10, id 15680: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG dtic.mil/DNSKEY alg 10, id 15680: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG dtic.mil/DNSKEY alg 10, id 15680: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG dtic.mil/DNSKEY alg 10, id 55959: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG dtic.mil/DNSKEY alg 10, id 55959: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG dtic.mil/DNSKEY alg 10, id 55959: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG dtic.mil/DNSKEY alg 10, id 55959: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG dtic.mil/DNSKEY alg 10, id 63261: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG dtic.mil/DNSKEY alg 10, id 63261: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG dtic.mil/DNSKEY alg 10, id 63261: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG dtic.mil/DNSKEY alg 10, id 63261: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG dtic.mil/MX alg 10, id 15680: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG dtic.mil/NS alg 10, id 15680: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG dtic.mil/SOA alg 10, id 15680: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG dtic.mil/TXT alg 10, id 15680: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • dtic.mil/DS (alg 10, id 55959): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • dtic.mil/DS (alg 10, id 55959): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • dtic.mil/DS (alg 10, id 55959): 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.
  • dtic.mil/DS (alg 10, id 55959): 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.
  • dtic.mil/MX: 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. (140.18.188.250, UDP_-_EDNS0_4096_D_KN)
  • dtic.mil/SOA: No response was received from the server over UDP (tried 7 times) until the NSID EDNS option was removed (however, this server appeared to respond legitimately to other queries with the NSID EDNS option present). See RFC 6891, Sec. 6.1.2. (140.18.188.250, UDP_-_EDNS0_4096_D_KN)
  • dtic.mil/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. (140.18.189.250, UDP_-_EDNS0_4096_D_KN)
  • dtic.mil/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • dtic.mil/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