usno.navy.mil
Updated:
2020-04-23 00:11:39 UTC (1675 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (4)
- usno.navy.mil/MX
- usno.navy.mil/NS
- usno.navy.mil/SOA
- usno.navy.mil/TXT
Secure (1)
- navy.mil/SOA
DNSKEY/DS/NSEC status
Secure (13)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 48903)
- NSEC3 proving non-existence of usno.navy.mil/DS
- mil/DNSKEY (alg 8, id 27843)
- mil/DNSKEY (alg 8, id 47763)
- mil/DNSKEY (alg 8, id 7765)
- mil/DS (alg 8, id 7765)
- mil/DS (alg 8, id 7765)
- navy.mil/DNSKEY (alg 8, id 33826)
- navy.mil/DNSKEY (alg 8, id 3624)
- navy.mil/DNSKEY (alg 8, id 43186)
- navy.mil/DS (alg 8, id 43186)
- navy.mil/DS (alg 8, id 43186)
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 to usno.navy.mil: No NSEC RR(s) were returned to validate the NXDOMAIN response. See RFC 4035, Sec. 3.1.3.2, RFC 5155, Sec. 7.2.2. (152.229.110.235, UDP_-_EDNS0_4096_D_K)
- navy.mil to usno.navy.mil: The NXDOMAIN response did not include an SOA record. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.1. (152.229.110.235, UDP_-_EDNS0_4096_D_K)
- usno.navy.mil zone: The following NS name(s) did not resolve to address(es): psyche.usno.navy.mil
- usno.navy.mil zone: There was an error resolving the following NS name(s) to address(es): metis.usnogps.navy.mil, tycho.usnogps.navy.mil
- usno.navy.mil/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (11)
- 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/DS (alg 8, id 7765): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- mil/DS (alg 8, id 7765): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- mil/DS (alg 8, id 7765): 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 7765): 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 43186): 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 43186): 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 43186): 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 43186): 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/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
