co.bw
Updated:
2025-07-28 20:28:28 UTC (142 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Bogus (1)
- co.bw/A
Secure (2)
- bw/SOA
- co.bw/A (NODATA)
DNSKEY/DS/NSEC status
Secure (8)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 38696)
- ./DNSKEY (alg 8, id 46441)
- ./DNSKEY (alg 8, id 53148)
- NSEC3 proving non-existence of co.bw/A
- bw/DNSKEY (alg 13, id 16690)
- bw/DNSKEY (alg 13, id 62453)
- bw/DS (alg 13, id 62453)
Delegation status
Secure (1)
- . to bw
Notices
Errors (11)
- . to bw: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (204.209.56.8, 204.209.56.9, 204.209.56.10, 204.209.56.11, 204.209.56.12, 204.209.56.13, 204.209.56.14, 204.209.56.15, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- . to bw: The DS RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no DS RR matched a DNSKEY with algorithm 13 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (204.209.56.8, 204.209.56.9, 204.209.56.10, 204.209.56.11, 204.209.56.12, 204.209.56.13, 204.209.56.14, 204.209.56.15, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- NSEC3 proving non-existence of co.bw/A: The following queries resulted in an answer response, even though the bitmap in the NSEC3 RR indicates that the queried records don't exist: co.bw/A See RFC 5155, Sec. 8.5.
- NSEC3 proving non-existence of co.bw/A: The following queries resulted in an answer response, even though the bitmap in the NSEC3 RR indicates that the queried records don't exist: co.bw/A See RFC 5155, Sec. 8.5.
- bw/DNSKEY (alg 13, id 16690): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (204.209.56.8, 204.209.56.9, 204.209.56.10, 204.209.56.11, 204.209.56.12, 204.209.56.13, 204.209.56.14, 204.209.56.15, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- bw/DNSKEY (alg 13, id 62453): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (204.209.56.8, 204.209.56.9, 204.209.56.10, 204.209.56.11, 204.209.56.12, 204.209.56.13, 204.209.56.14, 204.209.56.15, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- co.bw/A: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (204.209.56.8, 204.209.56.9, 204.209.56.10, 204.209.56.11, 204.209.56.12, 204.209.56.13, 204.209.56.14, 204.209.56.15, UDP_-_EDNS0_4096_D_KN)
- co.bw/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (168.167.168.37, UDP_-_NOEDNS_)
- bw/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- co.bw/NS has errors; select the "Denial of existence" DNSSEC option to see them.
- co.bw/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (7)
- . to bw: The glue address(es) for master.btc.net.bw (168.167.168.37) differed from its authoritative address(es) (204.209.56.8, 204.209.56.9, 204.209.56.10, 204.209.56.11, 204.209.56.12, 204.209.56.13, 204.209.56.14, 204.209.56.15). See RFC 1034, Sec. 4.2.2.
- NSEC3 proving non-existence of co.bw/A: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of co.bw/A: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- co.bw/A: The server responded with no OPT record, rather than with RCODE FORMERR. See RFC 6891, Sec. 7. (204.209.56.8, 204.209.56.9, 204.209.56.10, 204.209.56.11, 204.209.56.12, 204.209.56.13, 204.209.56.14, 204.209.56.15, UDP_-_EDNS0_4096_D_KN)
- bw/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- co.bw/NS has warnings; select the "Denial of existence" DNSSEC option to see them.
- co.bw/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
