usno.navy.mil

Updated: 2025-07-19 07:27:44 UTC (140 days ago) Go to most recent »

DNSSEC options (hide)

Notices

DNSSEC Authentication Chain

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 38696)
./DNSKEY (alg 8, id 46441)
./DNSKEY (alg 8, id 53148)
NSEC3 proving non-existence of usno.navy.mil/DS
mil/DNSKEY (alg 8, id 47031)
mil/DNSKEY (alg 8, id 57246)
mil/DNSKEY (alg 8, id 63500)
mil/DS (alg 8, id 63500)
navy.mil/DNSKEY (alg 8, id 183)
navy.mil/DNSKEY (alg 8, id 52315)
navy.mil/DNSKEY (alg 8, id 59809)
navy.mil/DNSKEY (alg 8, id 62718)
navy.mil/DS (alg 8, id 52315)
navy.mil/DS (alg 8, id 52315)

NSEC3 proving non-existence of usno.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 usno.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/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (214.23.245.6, 215.65.126.185, UDP_-_EDNS0_4096_D_KN)
usno.navy.mil/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (215.65.126.185, UDP_-_EDNS0_512_D_KN)
usno.navy.mil/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
usno.navy.mil/DS has errors; select the "Denial of existence" DNSSEC option to see them.

NSEC3 proving non-existence of usno.navy.mil/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of usno.navy.mil/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
navy.mil/DS (alg 8, id 52315): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
navy.mil/DS (alg 8, id 52315): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
navy.mil/DS (alg 8, id 52315): 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.
navy.mil/DS (alg 8, id 52315): 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.
usno.navy.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:120:c:162::243, 2608:140:c:157::235, 2608:4163:1:143::243, UDP_-_EDNS0_4096_D_KN)
usno.navy.mil/DS has warnings; select the "Denial of existence" DNSSEC option to see them.