View on GitHub

DNSViz: A DNS visualization tool

dla.mil

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

RRset statusRRset status

Secure (4)
  • dla.mil/MX
  • dla.mil/NS
  • dla.mil/SOA
  • dla.mil/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (12)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 46594)
  • dla.mil/DNSKEY (alg 8, id 44845)
  • dla.mil/DNSKEY (alg 8, id 58143)
  • dla.mil/DNSKEY (alg 8, id 60304)
  • dla.mil/DS (alg 8, id 60304)
  • dla.mil/DS (alg 8, id 60304)
  • mil/DNSKEY (alg 8, id 15684)
  • mil/DNSKEY (alg 8, id 7765)
  • mil/DNSKEY (alg 8, id 8223)
  • mil/DS (alg 8, id 7765)
  • mil/DS (alg 8, id 7765)

Delegation statusDelegation status

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

NoticesNotices

Errors (11)
  • dla.mil/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (131.78.81.254, UDP_-_EDNS0_512_D_K)
  • dla.mil/DS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (199.252.157.234, UDP_-_NOEDNS_)
  • dla.mil/MX: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (131.78.81.254, UDP_-_NOEDNS_)
  • dla.mil/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (131.78.81.254, UDP_-_EDNS0_512_D_K)
  • mil zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (199.252.180.234)
  • dla.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • dla.mil/DS has errors; select the "Denial of existence" DNSSEC option to see them.
  • 3cga0q6p82.dla.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • dla.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • dla.mil/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • dla.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (20)
  • dla.mil/DS (alg 8, id 60304): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • dla.mil/DS (alg 8, id 60304): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • dla.mil/DS (alg 8, id 60304): 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.
  • dla.mil/DS (alg 8, id 60304): 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.
  • dla.mil/NS: 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. (131.78.81.254, UDP_-_EDNS0_4096_D_K)
  • dla.mil/SOA: No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (131.78.81.254, UDP_-_EDNS0_4096_D_K_0x20)
  • mil/DNSKEY (alg 8, id 15684): No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (199.252.162.234, UDP_-_EDNS0_4096_D_K)
  • mil/DNSKEY (alg 8, id 15684): 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. (199.252.157.234, UDP_-_EDNS0_4096_D_K)
  • mil/DNSKEY (alg 8, id 7765): No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (199.252.162.234, UDP_-_EDNS0_4096_D_K)
  • mil/DNSKEY (alg 8, id 7765): 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. (199.252.157.234, UDP_-_EDNS0_4096_D_K)
  • mil/DNSKEY (alg 8, id 8223): No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (199.252.162.234, UDP_-_EDNS0_4096_D_K)
  • mil/DNSKEY (alg 8, id 8223): 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. (199.252.157.234, UDP_-_EDNS0_4096_D_K)
  • mil/DS (alg 8, id 7765): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • mil/DS (alg 8, id 7765): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • mil/DS (alg 8, id 7765): 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/DS (alg 8, id 7765): 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.
  • dla.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • dla.mil/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • 3cga0q6p82.dla.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • dla.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