View on GitHub

DNSViz: A DNS visualization tool

navy.mil

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

RRset statusRRset status

Insecure (4)
  • navy.mil/MX
  • navy.mil/NS
  • navy.mil/SOA
  • navy.mil/TXT
Secure (1)
  • mil/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (7)
  • ./DNSKEY (alg 8, id 20038)
  • ./DNSKEY (alg 8, id 20326)
  • NSEC3 proving non-existence of navy.mil/DS
  • mil/DNSKEY (alg 8, id 16801)
  • mil/DNSKEY (alg 8, id 21018)
  • mil/DNSKEY (alg 8, id 51405)
  • mil/DS (alg 8, id 16801)

Delegation statusDelegation status

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

NoticesNotices

Errors (6)
  • NSEC3 proving non-existence of navy.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 navy.mil/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • navy.mil zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2608:102:0:182d:1001:9012:c00:20, 2608:125:0:1811:1001:9012:f00:20, 2608:145:0:180b:1001:9012:d00:20, 2608:4122:0:1012:1001:9012:1400:20, 2608:c182::1001:9012:1600:20, 2608:c182:0:1012:1001:9012:1400:20)
  • navy.mil/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2608:102:0:182d:1001:9012:c00:20, 2608:125:0:1811:1001:9012:f00:20, 2608:145:0:180b:1001:9012:d00:20, 2608:4122:0:1012:1001:9012:1400:20, 2608:c182::1001:9012:1600:20, 2608:c182:0:1012:1001:9012:1400:20, UDP_-_NOEDNS_)
  • navy.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • navy.mil/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (8)
  • NSEC3 proving non-existence of navy.mil/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of navy.mil/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • mil to navy.mil: Authoritative AAAA records exist for dns1.disa.mil, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • mil to navy.mil: Authoritative AAAA records exist for dns2.disa.mil, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • mil to navy.mil: Authoritative AAAA records exist for dns3.disa.mil, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • mil to navy.mil: Authoritative AAAA records exist for dns4.disa.mil, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • mil to navy.mil: Authoritative AAAA records exist for dns5.disa.mil, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • navy.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