View on GitHub

DNSViz: A DNS visualization tool

btc.bw

« Previous analysis | Next analysis »
DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
  10. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset 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 statusDNSKEY/DS/NSEC status

Secure (9)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 26838)
  • NSEC3 proving non-existence of btc.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 50194)
  • bw/DS (alg 8, id 50194)

Delegation statusDelegation status

Insecure (1)
  • bw to btc.bw
Secure (1)
  • . to bw

NoticesNotices

Errors (3)
  • NSEC3 proving non-existence of btc.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 btc.bw/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • btc.bw/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (10)
  • 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.
  • 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.
  • bw/DS (alg 8, id 50194): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • bw/DS (alg 8, id 50194): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • bw/DS (alg 8, id 50194): 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 50194): 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.
  • btc.bw/DS has warnings; select the "Denial of existence" DNSSEC option to see them.

DNSKEY legend

Full legend
SEP bit setSEP bit set
Revoke bit setRevoke bit set
Trust anchorTrust anchor
Download: png | svg
Warning JavaScript is required to make the graph below interactive.
DNSSEC authentication graph