co.bw
Updated:
2025-10-15 17:09:22 UTC (54 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Secure (3)
- bw/SOA
- co.bw/A (NODATA)
- co.bw/AAAA (NODATA)
DNSKEY/DS/NSEC status
Secure (8)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 38696)
- ./DNSKEY (alg 8, id 61809)
- NSEC3 proving non-existence of co.bw/A
- NSEC3 proving non-existence of co.bw/AAAA
- bw/DNSKEY (alg 13, id 48016)
- bw/DNSKEY (alg 13, id 62453)
- bw/DS (alg 13, id 62453)
Delegation status
Secure (1)
- . to bw
Notices
Errors (3)
- bw/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (168.167.168.37, UDP_-_EDNS0_512_D_KN)
- co.bw/A: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (168.167.168.37, UDP_-_NOEDNS_)
- co.bw/AAAA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (168.167.168.37, UDP_-_NOEDNS_)
Warnings (5)
- 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.
- NSEC3 proving non-existence of co.bw/AAAA: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of co.bw/AAAA: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- bw/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
