usno.navy.mil
Updated:
2025-08-08 20:10:38 UTC (119 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (3)
- usno.navy.mil/NS
- usno.navy.mil/SOA
- usno.navy.mil/TXT
Secure (1)
- navy.mil/SOA
DNSKEY/DS/NSEC status
Secure (14)
- ./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/DS (alg 8, id 52315)
- navy.mil/DS (alg 8, id 52315)
Delegation status
Insecure (1)
- navy.mil to usno.navy.mil
Secure (2)
- . to mil
- mil to navy.mil
Notices
Errors (5)
- 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 zone: The following NS name(s) did not resolve to address(es): squad.navo.mil, squid.navo.mil, minnow.navo, squid.navo
- navy.mil/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (152.229.110.232, 214.3.125.232, UDP_-_EDNS0_4096_D_KN)
- usno.navy.mil/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (9)
- 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.
- mil to navy.mil: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the mil zone): minnow.navo, squid.navo, squad.navo.mil, squid.navo.mil See RFC 1034, Sec. 4.2.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): 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.
JavaScript is required to make the graph below interactive.
