gov.bw
Updated:
2022-07-28 21:55:15 UTC (891 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (6)
- bw/SOA
- gov.bw/A
- gov.bw/MX
- gov.bw/NS
- gov.bw/SOA
- gov.bw/TXT
Secure (2)
- ./SOA
- ./SOA
DNSKEY/DS/NSEC status
Insecure (5)
- 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)
Secure (3)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 20826)
- NSEC proving non-existence of bw/DS
Delegation status
Insecure (2)
- . to bw
- bw to gov.bw
Notices
Errors (6)
- 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.
- gov.bw zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (196.216.163.125)
- 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, 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, UDP_-_NOEDNS_)
- gov.bw/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (3)
- 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.
- gov.bw/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
