marines.mil

Updated: 2021-08-18 19:11:46 UTC (1227 days ago) Go to most recent »

DNSSEC options (hide)

Notices

DNSSEC Authentication Chain

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 26838)
NSEC3 proving non-existence of marines.mil/DS
mil/DNSKEY (alg 8, id 39879)
mil/DNSKEY (alg 8, id 51349)
mil/DNSKEY (alg 8, id 9498)
mil/DS (alg 8, id 51349)
mil/DS (alg 8, id 51349)

NSEC3 proving non-existence of marines.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 marines.mil/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
marines.mil zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (192.156.7.120)
marines.mil/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (192.156.7.120, TCP_-_EDNS0_4096_D_N)
marines.mil/DS has errors; select the "Denial of existence" DNSSEC option to see them.

NSEC3 proving non-existence of marines.mil/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of marines.mil/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
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.
marines.mil/DS has warnings; select the "Denial of existence" DNSSEC option to see them.