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 (6)
  • dtic.mil/A
  • dtic.mil/MX
  • dtic.mil/NS
  • dtic.mil/NSEC3PARAM
  • dtic.mil/SOA
  • dtic.mil/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (12)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 47671)
  • dtic.mil/DNSKEY (alg 10, id 36092)
  • dtic.mil/DNSKEY (alg 10, id 5228)
  • dtic.mil/DNSKEY (alg 10, id 63261)
  • dtic.mil/DS (alg 10, id 1536)
  • dtic.mil/DS (alg 10, id 63261)
  • dtic.mil/DS (alg 10, id 63261)
  • mil/DNSKEY (alg 8, id 44790)
  • mil/DNSKEY (alg 8, id 4659)
  • mil/DNSKEY (alg 8, id 56347)
  • mil/DS (alg 8, id 56347)
Non_existent (1)
  • dtic.mil/DNSKEY (alg 10, id 1536)

Delegation statusDelegation status

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

NoticesNotices

Errors (4)
  • mil zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2608:c144:1:155::234)
  • dtic.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • zdstkba5u3.dtic.mil/A 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.
Warnings (23)
  • RRSIG dtic.mil/A alg 10, id 36092: 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 36092: 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 36092: 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 36092: 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 36092: 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 36092: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG dtic.mil/NSEC3PARAM alg 10, id 36092: 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 36092: 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 36092: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • dtic.mil/DS (alg 10, id 63261): 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 63261): 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 63261): 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 63261): 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.
  • mil/DNSKEY (alg 8, id 44790): 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:4163:1:143::234, UDP_-_EDNS0_4096_D_KN)
  • mil/DNSKEY (alg 8, id 4659): 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:4163:1:143::234, UDP_-_EDNS0_4096_D_KN)
  • mil/DNSKEY (alg 8, id 56347): 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:4163:1:143::234, UDP_-_EDNS0_4096_D_KN)
  • dtic.mil/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • zdstkba5u3.dtic.mil/A 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.
  • dtic.mil/CNAME 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