View on GitHub

DNSViz: A DNS visualization tool

dds.mil

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

RRset statusRRset status

Insecure (5)
  • dds.mil/A
  • dds.mil/MX
  • dds.mil/NS
  • dds.mil/SOA
  • dds.mil/TXT
Secure (2)
  • mil/SOA
  • mil/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Insecure (4)
  • dds.mil/DNSKEY (alg 13, id 3786)
  • dds.mil/DNSKEY (alg 13, id 59866)
  • dds.mil/DNSKEY (alg 13, id 62157)
  • dds.mil/DNSKEY (alg 13, id 7131)
Secure (9)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 60955)
  • ./DNSKEY (alg 8, id 951)
  • NSEC3 proving non-existence of dds.mil/DS
  • NSEC3 proving non-existence of dds.mil/DS
  • mil/DNSKEY (alg 8, id 53035)
  • mil/DNSKEY (alg 8, id 62470)
  • mil/DNSKEY (alg 8, id 8715)
  • mil/DS (alg 8, id 62470)

Delegation statusDelegation status

Insecure (1)
  • mil to dds.mil
Secure (1)
  • . to mil

NoticesNotices

Errors (5)
  • NSEC3 proving non-existence of dds.mil/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of dds.mil/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of dds.mil/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of dds.mil/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • dds.mil/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (8)
  • NSEC3 proving non-existence of dds.mil/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of dds.mil/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of dds.mil/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of dds.mil/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • mil/DNSKEY (alg 8, id 53035): 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:c144:1:155::234, UDP_-_EDNS0_4096_D_KN)
  • mil/DNSKEY (alg 8, id 62470): 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:c144:1:155::234, UDP_-_EDNS0_4096_D_KN)
  • mil/DNSKEY (alg 8, id 8715): 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:c144:1:155::234, UDP_-_EDNS0_4096_D_KN)
  • dds.mil/DS 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