repi.mil
Updated:
2020-05-18 13:14:30 UTC (1678 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Bogus (3)
- repi.mil/NS
- repi.mil/SOA
- repi.mil/TXT
DNSKEY/DS/NSEC status
Bogus (4)
- repi.mil/DNSKEY (alg 8, id 15807)
- repi.mil/DNSKEY (alg 8, id 30691)
- repi.mil/DNSKEY (alg 8, id 45109)
- repi.mil/DNSKEY (alg 8, id 54560)
Secure (9)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 48903)
- mil/DNSKEY (alg 8, id 47763)
- mil/DNSKEY (alg 8, id 48726)
- mil/DNSKEY (alg 8, id 7765)
- mil/DS (alg 8, id 7765)
- mil/DS (alg 8, id 7765)
- repi.mil/DS (alg 8, id 54560)
- repi.mil/DS (alg 8, id 54560)
Delegation status
Bogus (1)
- mil to repi.mil
Secure (1)
- . to mil
Notices
Errors (8)
- mil to repi.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. (155.7.145.112, 155.7.145.113, 155.7.208.112, 155.7.208.113, UDP_-_EDNS0_4096_D_K)
- mil to repi.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. (155.7.145.112, 155.7.145.113, 155.7.208.112, 155.7.208.113, UDP_-_EDNS0_4096_D_K)
- mil/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (199.252.155.234, UDP_-_EDNS0_512_D_K)
- repi.mil/MX has errors; select the "Denial of existence" DNSSEC option to see them.
- repi.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- ws2pjcrmzn.repi.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
- repi.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- repi.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (13)
- 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.
- repi.mil/DS (alg 8, id 54560): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- repi.mil/DS (alg 8, id 54560): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- repi.mil/DS (alg 8, id 54560): 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.
- repi.mil/DS (alg 8, id 54560): 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.
- repi.mil/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
- repi.mil/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- ws2pjcrmzn.repi.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- repi.mil/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
- repi.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
