uscapitolpolice.gov
Updated:
2020-09-05 17:41:38 UTC (1538 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Bogus (2)
- uscapitolpolice.gov/NS
- uscapitolpolice.gov/SOA
DNSKEY/DS/NSEC status
Bogus (3)
- uscapitolpolice.gov/DNSKEY (alg 8, id 40159)
- uscapitolpolice.gov/DNSKEY (alg 8, id 44511)
- uscapitolpolice.gov/DNSKEY (alg 8, id 55504)
Secure (7)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 46594)
- gov/DNSKEY (alg 8, id 26665)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- uscapitolpolice.gov/DS (alg 8, id 16561)
Non_existent (1)
- uscapitolpolice.gov/DNSKEY (alg 8, id 16561)
Delegation status
Bogus (1)
- gov to uscapitolpolice.gov
Secure (1)
- . to gov
Notices
Errors (2)
- gov to uscapitolpolice.gov: 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. (128.177.179.2, 192.42.110.2, UDP_-_EDNS0_4096_D_K)
- gov to uscapitolpolice.gov: 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. (128.177.179.2, 192.42.110.2, UDP_-_EDNS0_4096_D_K)
Warnings (4)
- gov/DS (alg 8, id 7698): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- gov/DS (alg 8, id 7698): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- gov/DS (alg 8, id 7698): 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.
- gov/DS (alg 8, id 7698): 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.
JavaScript is required to make the graph below interactive.
