View on GitHub

DNSViz: A DNS visualization tool

dia.mil

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

RRset statusRRset status

Bogus (4)
  • dia.mil/MX
  • dia.mil/NS
  • dia.mil/SOA
  • dia.mil/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Bogus (5)
  • dia.mil/DNSKEY (alg 8, id 18141)
  • dia.mil/DNSKEY (alg 8, id 2148)
  • dia.mil/DNSKEY (alg 8, id 27544)
  • dia.mil/DNSKEY (alg 8, id 43500)
  • dia.mil/DNSKEY (alg 8, id 56689)
Secure (8)
  • ./DNSKEY (alg 8, id 14631)
  • ./DNSKEY (alg 8, id 20326)
  • dia.mil/DS (alg 8, id 63334)
  • mil/DNSKEY (alg 8, id 11853)
  • mil/DNSKEY (alg 8, id 16560)
  • mil/DNSKEY (alg 8, id 51349)
  • mil/DS (alg 8, id 51349)
  • mil/DS (alg 8, id 51349)
Non_existent (1)
  • dia.mil/DNSKEY (alg 8, id 63334)

Delegation statusDelegation status

Bogus (1)
  • mil to dia.mil
Secure (1)
  • . to mil

NoticesNotices

Errors (6)
  • mil to dia.mil: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (198.201.23.26, 214.3.138.10, 214.3.138.13, UDP_-_EDNS0_4096_D_KN)
  • mil to dia.mil: The DS RRset for the zone included algorithm 8 (RSASHA256), but no DS RR matched a DNSKEY with algorithm 8 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (198.201.23.26, 214.3.138.10, 214.3.138.13, UDP_-_EDNS0_4096_D_KN)
  • dia.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • bdm9x81vp2.dia.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • dia.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • dia.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (9)
  • dia.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. (214.3.138.10, UDP_-_EDNS0_4096_D_KN)
  • 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.
  • dia.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • bdm9x81vp2.dia.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • dia.mil/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • dia.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