usno.navy.mil
Updated:
2021-01-05 15:37:01 UTC (1418 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 (14)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 26116)
- ./DNSKEY (alg 8, id 42351)
- NSEC3 proving non-existence of usno.navy.mil/DS
- mil/DNSKEY (alg 8, id 24363)
- mil/DNSKEY (alg 8, id 35118)
- mil/DNSKEY (alg 8, id 51349)
- mil/DS (alg 8, id 51349)
- mil/DS (alg 8, id 51349)
- navy.mil/DNSKEY (alg 8, id 42750)
- navy.mil/DNSKEY (alg 8, id 43186)
- navy.mil/DNSKEY (alg 8, id 54382)
- 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 (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): uforiftr01.csd.disa.mil, uforiftr02.csd.disa.mil
- usno.navy.mil/MX 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 (15)
- 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): uforiftr07.csd.disa.mil, uforiftr06.csd.disa.mil See RFC 1034, Sec. 4.2.2.
- mil to navy.mil: The following NS name(s) were found in the delegation NS RRset (i.e., in the mil zone), but not in the authoritative NS RRset: uforiftr01.csd.disa.mil, uforiftr02.csd.disa.mil See RFC 1034, Sec. 4.2.2.
- mil/DS (alg 8, id 51349): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- mil/DS (alg 8, id 51349): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- mil/DS (alg 8, id 51349): 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 51349): 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/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
- usno.navy.mil/CNAME 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.
