usno.navy.mil
Updated:
2024-02-17 02:28:18 UTC (280 days ago)
Go to most recent »
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 (12)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 30903)
- NSEC3 proving non-existence of usno.navy.mil/DS
- mil/DNSKEY (alg 8, id 16801)
- mil/DNSKEY (alg 8, id 29059)
- mil/DNSKEY (alg 8, id 49404)
- mil/DS (alg 8, id 16801)
- navy.mil/DNSKEY (alg 8, id 37189)
- navy.mil/DNSKEY (alg 8, id 47718)
- navy.mil/DNSKEY (alg 8, id 8425)
- navy.mil/DS (alg 8, id 8425)
- navy.mil/DS (alg 8, id 8425)
Delegation status
Insecure (1)
- navy.mil to usno.navy.mil
Secure (2)
- . to mil
- mil to navy.mil
Notices
Errors (20)
- 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) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (152.229.110.235)
- 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:21, 2608:125:0:1811:1001:9012:f00:21, 2608:145:0:180b:1001:9012:d00:21, 2608:4122:0:1012:1001:9012:1400:11, 2608:c182::1001:9012:1600:11)
- navy.mil/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (152.229.110.235, UDP_-_NOEDNS_)
- navy.mil/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (152.229.110.235, 214.23.245.4, UDP_-_EDNS0_512_D_KN)
- navy.mil/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (215.65.126.180, UDP_-_EDNS0_4096_D)
- usno.navy.mil/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (131.77.60.235, UDP_-_NOEDNS_)
- usno.navy.mil/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (131.77.60.235, 152.229.110.235, 214.23.245.4, UDP_-_EDNS0_512_D_KN)
- usno.navy.mil/DS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (131.77.60.235, 152.229.110.235, UDP_-_NOEDNS_)
- usno.navy.mil/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (131.77.60.235, 152.229.110.235, TCP_-_EDNS0_4096_D_N)
- usno.navy.mil/SOA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (131.77.60.235, 152.229.110.235, UDP_-_NOEDNS_)
- usno.navy.mil/TXT: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (152.229.110.235, 214.23.245.4, UDP_-_NOEDNS_)
- usno.navy.mil/MX has errors; select the "Denial of existence" DNSSEC option to see them.
- mf509tbeyx.usno.navy.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
- usno.navy.mil/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- usno.navy.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- usno.navy.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- usno.navy.mil/NSEC3PARAM 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 (23)
- 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: AAAA glue records exist for ns.cybercom.mil, but there are no corresponding authoritative AAAA records. See RFC 1034, Sec. 4.2.2.
- mil to navy.mil: AAAA glue records exist for ns.jtfgno.mil, but there are no corresponding authoritative AAAA records. See RFC 1034, Sec. 4.2.2.
- mil to navy.mil: AAAA glue records exist for ns1.csd.disa.mil, but there are no corresponding authoritative AAAA records. See RFC 1034, Sec. 4.2.2.
- mil to navy.mil: AAAA glue records exist for uforiftr01.csd.disa.mil, but there are no corresponding authoritative AAAA records. See RFC 1034, Sec. 4.2.2.
- mil to navy.mil: AAAA glue records exist for updciftr01.csd.disa.mil, but there are no corresponding authoritative AAAA records. See RFC 1034, Sec. 4.2.2.
- navy.mil to usno.navy.mil: No response was received from the server over UDP (tried 7 times) until the NSID EDNS option was removed (however, this server appeared to respond legitimately to other queries with the NSID EDNS option present). See RFC 6891, Sec. 6.1.2. (215.65.126.180, UDP_-_EDNS0_4096_D_KN)
- navy.mil/DS (alg 8, id 8425): 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 8425): 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 8425): 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 8425): 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. (214.23.245.4, UDP_-_EDNS0_4096_D_KN)
- usno.navy.mil/NS: No response was received from the server over UDP (tried 7 times) until the NSID EDNS option was removed (however, this server appeared to respond legitimately to other queries with the NSID EDNS option present). See RFC 6891, Sec. 6.1.2. (131.77.60.235, 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. (152.229.110.235, UDP_-_EDNS0_4096_D_KN)
- usno.navy.mil/SOA: No response was received from the server over UDP (tried 7 times) until the NSID EDNS option was removed (however, this server appeared to respond legitimately to other queries with the NSID EDNS option present). See RFC 6891, Sec. 6.1.2. (215.65.126.180, UDP_-_EDNS0_4096_D_KN)
- usno.navy.mil/SOA: 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. (199.252.154.243, 199.252.157.235, 199.252.162.243, 214.23.245.4, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
- usno.navy.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- usno.navy.mil/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
- mf509tbeyx.usno.navy.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- usno.navy.mil/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
- usno.navy.mil/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
- 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.
