gov.bw

Updated: 2021-02-02 10:32:16 UTC (1435 days ago) Go to most recent »

DNSSEC options (hide)

Notices

DNSSEC Authentication Chain

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 42351)
NSEC3 proving non-existence of gov.bw/DS
bw/DNSKEY (alg 8, id 18880)
bw/DNSKEY (alg 8, id 38424)
bw/DNSKEY (alg 8, id 46158)
bw/DNSKEY (alg 8, id 50194)
bw/DS (alg 8, id 50194)
bw/DS (alg 8, id 50194)

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:0:6::3, 2c0f:ff00:0:6::5, 2c0f:ff00:1:3::226)
gov.bw/DS has errors; select the "Denial of existence" DNSSEC option to see them.

. to bw: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the . zone): master.btc.net.bw See RFC 1034, Sec. 4.2.2.
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 50194): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
bw/DS (alg 8, id 50194): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
bw/DS (alg 8, id 50194): 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 50194): 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.