btc.bw
Updated:
2026-01-19 15:13:08 UTC (15 minutes ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (5)
- btc.bw/A
- btc.bw/MX
- btc.bw/NS
- btc.bw/SOA
- btc.bw/TXT
Secure (1)
- bw/SOA
DNSKEY/DS/NSEC status
Secure (7)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 21831)
- ./DNSKEY (alg 8, id 38696)
- NSEC3 proving non-existence of btc.bw/DS
- bw/DNSKEY (alg 13, id 34799)
- bw/DNSKEY (alg 13, id 62453)
- bw/DS (alg 13, id 62453)
Delegation status
Insecure (1)
- bw to btc.bw
Secure (1)
- . to bw
Notices
Errors (6)
- btc.bw zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2c0f:ff00:0:4::4, 2c0f:ff00:0:4::5, 2c0f:ff00:0:4::11, 2c0f:ff00:0:4::13, 2c0f:ff00:0:6::2, 2c0f:ff00:0:6::4)
- btc.bw/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2c0f:ff00:0:4::4, 2c0f:ff00:0:4::5, 2c0f:ff00:0:4::11, 2c0f:ff00:0:4::13, 2c0f:ff00:0:6::2, 2c0f:ff00:0:6::4, UDP_-_NOEDNS_)
- btc.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)
- btc.bw/MX: 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)
- btc.bw/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2c0f:ff00:0:4::4, 2c0f:ff00:0:4::5, 2c0f:ff00:0:4::11, 2c0f:ff00:0:4::13, 2c0f:ff00:0:6::2, 2c0f:ff00:0:6::4, UDP_-_NOEDNS_)
- btc.bw/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (12)
- NSEC3 proving non-existence of btc.bw/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of btc.bw/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- btc.bw/NS: No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (168.167.168.37, UDP_-_EDNS0_4096_D_KN)
- btc.bw/SOA: No response was received from the server over UDP (tried 7 times) until the NSID EDNS option was removed (however, this server appeared to respond legitimately to other queries with the NSID EDNS option present). See RFC 6891, Sec. 6.1.2. (168.167.168.37, UDP_-_EDNS0_4096_D_KN)
- btc.bw/SOA: No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (168.167.168.37, UDP_-_EDNS0_4096_D_KN)
- bw to btc.bw: Authoritative AAAA records exist for ns1.btc.bw, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- bw to btc.bw: Authoritative AAAA records exist for ns4.btc.bw, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- bw to btc.bw: Authoritative AAAA records exist for vpsm.btc.bw, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- btc.bw/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
- btc.bw/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- btc.bw/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
- btc.bw/CDS has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
