bep.gov
Updated:
2023-05-14 05:13:50 UTC (563 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (8)
- bep.gov/A
- bep.gov/AAAA
- bep.gov/MX
- bep.gov/NS
- bep.gov/NSEC3PARAM
- bep.gov/NSEC3PARAM
- bep.gov/SOA
- bep.gov/TXT
DNSKEY/DS/NSEC status
Secure (9)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 60955)
- bep.gov/DNSKEY (alg 8, id 34504)
- bep.gov/DNSKEY (alg 8, id 46965)
- bep.gov/DS (alg 8, id 34504)
- bep.gov/DS (alg 8, id 34504)
- gov/DNSKEY (alg 8, id 50011)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
Delegation status
Secure (2)
- . to gov
- gov to bep.gov
Notices
Errors (2)
- k84d6jpao5.bep.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- bep.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (8)
- bep.gov/DNSKEY: The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (172.64.52.110, 172.64.53.149, 2606:4700:52::ac40:346e, 2606:4700:5a::ac40:3595, UDP_-_EDNS0_512_D_KN)
- bep.gov/DS (alg 8, id 34504): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- bep.gov/DS (alg 8, id 34504): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- bep.gov/DS (alg 8, id 34504): 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.
- bep.gov/DS (alg 8, id 34504): 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.
- bep.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
- k84d6jpao5.bep.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- bep.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
