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 (2)
  • dla.mil/NS
  • dla.mil/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (12)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 26838)
  • dla.mil/DNSKEY (alg 8, id 58143)
  • dla.mil/DNSKEY (alg 8, id 60304)
  • dla.mil/DNSKEY (alg 8, id 6760)
  • dla.mil/DS (alg 8, id 6760)
  • dla.mil/DS (alg 8, id 6760)
  • mil/DNSKEY (alg 8, id 39879)
  • mil/DNSKEY (alg 8, id 51349)
  • mil/DNSKEY (alg 8, id 9498)
  • mil/DS (alg 8, id 51349)
  • mil/DS (alg 8, id 51349)

Delegation statusDelegation status

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

NoticesNotices

Errors (9)
  • dla.mil/A: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (131.78.81.254, 206.38.35.3, UDP_-_NOEDNS_)
  • dla.mil/MX: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (131.78.81.254, 206.38.35.3, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
  • dla.mil/NSEC3PARAM: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (131.78.81.254, 206.38.35.3, UDP_-_NOEDNS_)
  • dla.mil/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (131.78.81.254, 206.38.35.3, TCP_-_NOEDNS_)
  • dla.mil/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (131.78.81.254, 206.38.35.3, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
  • dla.mil/TXT: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (206.38.35.3, UDP_-_NOEDNS_)
  • yl8kdm1avg.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/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (9)
  • dla.mil/DS (alg 8, id 6760): 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 6760): 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 6760): 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 6760): 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 51349): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • mil/DS (alg 8, id 51349): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • mil/DS (alg 8, id 51349): 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 51349): 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/AAAA 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