usfj.mil
Updated:
2022-10-15 17:53:36 UTC (799 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Bogus (4)
- usfj.mil/NS
- usfj.mil/NSEC3PARAM
- usfj.mil/SOA
- usfj.mil/TXT
DNSKEY/DS/NSEC status
Bogus (4)
- usfj.mil/DNSKEY (alg 8, id 35166)
- usfj.mil/DNSKEY (alg 8, id 46791)
- usfj.mil/DNSKEY (alg 8, id 58520)
- usfj.mil/DNSKEY (alg 8, id 61411)
Secure (7)
- ./DNSKEY (alg 8, id 18733)
- ./DNSKEY (alg 8, id 20326)
- mil/DNSKEY (alg 8, id 18301)
- mil/DNSKEY (alg 8, id 31869)
- mil/DNSKEY (alg 8, id 62470)
- mil/DS (alg 8, id 62470)
- usfj.mil/DS (alg 8, id 57704)
Non_existent (1)
- usfj.mil/DNSKEY (alg 8, id 57704)
Delegation status
Bogus (1)
- mil to usfj.mil
Secure (1)
- . to mil
Notices
Errors (7)
- mil to usfj.mil: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (199.211.150.66, 199.211.150.67, 205.56.181.106, 205.56.181.107, TCP_-_EDNS0_4096_D_KN)
- mil to usfj.mil: The DS RRset for the zone included algorithm 8 (RSASHA256), but no DS RR matched a DNSKEY with algorithm 8 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (199.211.150.66, 199.211.150.67, 205.56.181.106, 205.56.181.107, TCP_-_EDNS0_4096_D_KN)
- usfj.mil/MX has errors; select the "Denial of existence" DNSSEC option to see them.
- ldk4sy3xhv.usfj.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
- usfj.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- usfj.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
- usfj.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (11)
- mil to usfj.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: pnocxns1.pr.navy.mil, pnocxns2.pr.navy.mil See RFC 1034, Sec. 4.2.2.
- usfj.mil/DS (alg 8, id 57704): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- usfj.mil/DS (alg 8, id 57704): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- usfj.mil/DS (alg 8, id 57704): 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.
- usfj.mil/DS (alg 8, id 57704): 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.
- usfj.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. (205.56.181.107, UDP_-_EDNS0_4096_D_KN)
- usfj.mil/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
- usfj.mil/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- ldk4sy3xhv.usfj.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- usfj.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- usfj.mil/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
