NSEC3 proving non-existence of bep.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of bep.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
zrkfwxl6mj.bep.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
bep.gov/DS 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 (7)
NSEC3 proving non-existence of bep.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of bep.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
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)
zrkfwxl6mj.bep.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
bep.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
bep.gov/DS 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.