usno.navy.mil
Updated:
2024-09-17 14:24:32 UTC (66 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 20038)
- ./DNSKEY (alg 8, id 20326)
- NSEC3 proving non-existence of usno.navy.mil/DS
- mil/DNSKEY (alg 8, id 16801)
- mil/DNSKEY (alg 8, id 20335)
- mil/DNSKEY (alg 8, id 51405)
- mil/DNSKEY (alg 8, id 63500)
- mil/DS (alg 8, id 16801)
- mil/DS (alg 8, id 63500)
- navy.mil/DNSKEY (alg 8, id 10320)
- navy.mil/DNSKEY (alg 8, id 11910)
- navy.mil/DNSKEY (alg 8, id 52315)
- 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 (7)
- 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 server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2608:102:0:182d:1001:9012:c00:20, 2608:125:0:1811:1001:9012:f00:20, 2608:145:0:180b:1001:9012:d00:20, 2608:4122:0:1012:1001:9012:1400:20, 2608:c182::1001:9012:1600:20, 2608:c182:0:1012:1001:9012:1400:20)
- navy.mil/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (152.229.110.232, 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. (2608:120:c:162::243, 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.
Warnings (14)
- 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: Authoritative AAAA records exist for dns1.disa.mil, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- mil to navy.mil: Authoritative AAAA records exist for dns2.disa.mil, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- mil to navy.mil: Authoritative AAAA records exist for dns3.disa.mil, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- mil to navy.mil: Authoritative AAAA records exist for dns4.disa.mil, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- mil to navy.mil: Authoritative AAAA records exist for dns5.disa.mil, but there are no corresponding AAAA glue records. 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 from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (2608:4163:1:143::243, UDP_-_EDNS0_4096_D_KN)
- 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, 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.
