gov.bw
Updated:
2020-08-21 21:53:20 UTC (1600 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (3)
- gov.bw/NS
- gov.bw/SOA
- gov.bw/TXT
Secure (2)
- bw/SOA
- bw/SOA
DNSKEY/DS/NSEC status
Secure (9)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 46594)
- 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 18880)
- bw/DS (alg 8, id 18880)
Delegation status
Insecure (1)
- bw to gov.bw
Secure (1)
- . to bw
Notices
Errors (19)
- 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:1:5::218)
- gov.bw zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (168.167.78.62)
- gov.bw zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (168.167.78.62)
- gov.bw zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (196.216.163.125, 196.216.163.126, 2a03:dd40:3::86, 2a03:dd40:3::93)
- gov.bw/DNSKEY: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (168.167.78.62, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
- 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, 196.216.163.126, 2a03:dd40:3::86, 2a03:dd40:3::93, UDP_-_NOEDNS_)
- gov.bw/NS: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (168.167.78.62, UDP_-_EDNS0_4096_D_K)
- gov.bw/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (168.167.78.62, TCP_-_EDNS0_4096_D)
- gov.bw/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (168.167.78.62, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K_0x20)
- gov.bw/TXT: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (168.167.78.62, UDP_-_EDNS0_4096_D_K)
- rjuv1k257b.gov.bw/A has errors; select the "Denial of existence" DNSSEC option to see them.
- gov.bw/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- gov.bw/DS has errors; select the "Denial of existence" DNSSEC option to see them.
- gov.bw/A has errors; select the "Denial of existence" DNSSEC option to see them.
- gov.bw/MX has errors; select the "Denial of existence" DNSSEC option to see them.
- gov.bw/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- gov.bw/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (8)
- 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 to gov.bw: The following NS name(s) were found in the delegation NS RRset (i.e., in the bw zone), but not in the authoritative NS RRset: ns5.gov.bw, dns3.nic.net.bw See RFC 1034, Sec. 4.2.2.
- bw/DS (alg 8, id 18880): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- bw/DS (alg 8, id 18880): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- bw/DS (alg 8, id 18880): 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 18880): 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.
JavaScript is required to make the graph below interactive.
