View on GitHub

DNSViz: A DNS visualization tool

move.mil

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

RRset statusRRset status

Secure (4)
  • mil/SOA
  • move.mil/NS
  • move.mil/SOA
  • move.mil/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (12)
  • ./DNSKEY (alg 8, id 20038)
  • ./DNSKEY (alg 8, id 20326)
  • NSEC3 proving non-existence of move.mil/DS
  • mil/DNSKEY (alg 8, id 16801)
  • mil/DNSKEY (alg 8, id 21018)
  • mil/DNSKEY (alg 8, id 54036)
  • mil/DS (alg 8, id 16801)
  • move.mil/DNSKEY (alg 13, id 15830)
  • move.mil/DNSKEY (alg 13, id 28994)
  • move.mil/DNSKEY (alg 13, id 43792)
  • move.mil/DS (alg 13, id 15830)
  • move.mil/DS (alg 13, id 15830)

Delegation statusDelegation status

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

NoticesNotices

Errors (3)
  • NSEC3 proving non-existence of move.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 move.mil/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • move.mil/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (11)
  • ./DNSKEY: The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_512_D_KN)
  • NSEC3 proving non-existence of move.mil/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of move.mil/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • mil/DS (alg 8, id 16801): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
  • mil/DS (alg 8, id 16801): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
  • move.mil/DS (alg 13, id 15830): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • move.mil/DS (alg 13, id 15830): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • move.mil/DS (alg 13, id 15830): 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.
  • move.mil/DS (alg 13, id 15830): 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.
  • move.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. (2608:4122:2:154::243, 2608:4163:1:143::243, 2608:c144:1:155::243, 2608:c184:1:180::243, UDP_-_EDNS0_4096_D_KN)
  • move.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