move.mil

Updated: 2023-07-24 17:29:47 UTC (515 days ago) Go to most recent »

DNSSEC options (hide)

Notices

DNSSEC Authentication Chain

./DNSKEY (alg 8, id 11019)
./DNSKEY (alg 8, id 20326)
NSEC3 proving non-existence of move.mil/DS
mil/DNSKEY (alg 8, id 26446)
mil/DNSKEY (alg 8, id 62470)
mil/DNSKEY (alg 8, id 62514)
mil/DS (alg 8, id 62470)
move.mil/DNSKEY (alg 13, id 15830)
move.mil/DNSKEY (alg 13, id 52029)
move.mil/DS (alg 13, id 15830)
move.mil/DS (alg 13, id 15830)

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.

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.
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/DS has warnings; select the "Denial of existence" DNSSEC option to see them.