NSEC3 proving non-existence of gov.bw/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 gov.bw/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
bw zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2c0f:ff00:1:5::218)
gov.bw zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (196.216.163.125, 196.216.163.126)
gov.bw zone: There was an error resolving the following NS name(s) to address(es): ns4.gov.bw, ns5.gov.bw
gov.bw/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (196.216.163.125, 196.216.163.126, UDP_-_NOEDNS_)
gov.bw/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (196.216.163.125, 196.216.163.126, UDP_-_NOEDNS_)
gov.bw/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (7)
NSEC3 proving non-existence of gov.bw/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of gov.bw/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
bw/DS (alg 8, id 18880): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
bw/DS (alg 8, id 18880): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
bw/DS (alg 8, id 18880): 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.
bw/DS (alg 8, id 18880): 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.bw/DS has warnings; select the "Denial of existence" DNSSEC option to see them.