ecfr.gov
Updated:
2020-05-27 17:17:42 UTC (1639 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Bogus (4)
- ecfr.gov/A
- ecfr.gov/NS
- ecfr.gov/SOA
- ecfr.gov/TXT
DNSKEY/DS/NSEC status
Secure (7)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 48903)
- ecfr.gov/DS (alg 7, id 61143)
- gov/DNSKEY (alg 8, id 40176)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
Non_existent (1)
- ecfr.gov/DNSKEY (alg 7, id 61143)
Delegation status
Bogus (1)
- gov to ecfr.gov
Secure (1)
- . to gov
Notices
Errors (11)
- ecfr.gov/A: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (173.245.58.88, 173.245.59.84, 2606:4700:50::adf5:3a58, 2606:4700:58::adf5:3b54, UDP_-_EDNS0_4096_D_K)
- ecfr.gov/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (173.245.58.88, 173.245.59.84, 2606:4700:50::adf5:3a58, 2606:4700:58::adf5:3b54, UDP_-_EDNS0_4096_D_K)
- ecfr.gov/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (173.245.58.88, 173.245.59.84, 2606:4700:50::adf5:3a58, 2606:4700:58::adf5:3b54, TCP_-_EDNS0_4096_D, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K_0x20)
- ecfr.gov/TXT: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (173.245.58.88, 173.245.59.84, 2606:4700:50::adf5:3a58, 2606:4700:58::adf5:3b54, UDP_-_EDNS0_4096_D_K)
- gov to ecfr.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. (173.245.58.88, 173.245.59.84, 2606:4700:50::adf5:3a58, 2606:4700:58::adf5:3b54, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
- gov to ecfr.gov: The DS RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no DS RR matched a DNSKEY with algorithm 7 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (173.245.58.88, 173.245.59.84, 2606:4700:50::adf5:3a58, 2606:4700:58::adf5:3b54, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
- ecfr.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- ecfr.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
- ecfr.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- ecfr.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- baj4720hcn.ecfr.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (8)
- ecfr.gov/DS (alg 7, id 61143): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- ecfr.gov/DS (alg 7, id 61143): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- ecfr.gov/DS (alg 7, id 61143): 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.
- ecfr.gov/DS (alg 7, id 61143): 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): 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.
