dnsops.gov
Updated:
2022-02-22 23:23:08 UTC (1041 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Bogus (5)
- dnsops.gov/A
- dnsops.gov/MX
- dnsops.gov/NS
- dnsops.gov/SOA
- dnsops.gov/TXT
DNSKEY/DS/NSEC status
Bogus (2)
- dnsops.gov/DNSKEY (alg 13, id 17593)
- dnsops.gov/DNSKEY (alg 13, id 49973)
Secure (6)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 9799)
- dnsops.gov/DS (alg 13, id 3836)
- gov/DNSKEY (alg 8, id 7030)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
Non_existent (1)
- dnsops.gov/DNSKEY (alg 13, id 3836)
Delegation status
Bogus (1)
- gov to dnsops.gov
Secure (1)
- . to gov
Notices
Errors (3)
- ./DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (192.112.36.4, UDP_-_EDNS0_512_D_KN)
- gov to dnsops.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. (129.6.100.203, 129.6.100.204, 2610:20:6005:100::203, 2610:20:6005:100::204, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- gov to dnsops.gov: The DS RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no DS RR matched a DNSKEY with algorithm 13 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (129.6.100.203, 129.6.100.204, 2610:20:6005:100::203, 2610:20:6005:100::204, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
JavaScript is required to make the graph below interactive.
