View on GitHub

DNSViz: A DNS visualization tool

org.bw

Updated: 2022-07-27 23:26:24 UTC (892 days ago) Update now
« 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 (3)
  • bw/SOA
  • org.bw/A (NODATA)
  • org.bw/AAAA (NODATA)
Secure (1)
  • ./SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Insecure (6)
  • NSEC3 proving non-existence of org.bw/A
  • NSEC3 proving non-existence of org.bw/AAAA
  • bw/DNSKEY (alg 8, id 18880)
  • bw/DNSKEY (alg 8, id 38424)
  • bw/DNSKEY (alg 8, id 46158)
  • bw/DNSKEY (alg 8, id 50194)
Secure (3)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 20826)
  • NSEC proving non-existence of bw/DS

Delegation statusDelegation status

Insecure (1)
  • . to bw

NoticesNotices

Errors (7)
  • NSEC3 proving non-existence of org.bw/A: 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 org.bw/A: 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 org.bw/AAAA: 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 org.bw/AAAA: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • org.bw/A: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (168.167.168.37, 2c0f:ff00:0:6::3, 2c0f:ff00:0:6::5, UDP_-_NOEDNS_)
  • org.bw/AAAA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (168.167.168.37, 2c0f:ff00:0:6::3, 2c0f:ff00:0:6::5, UDP_-_NOEDNS_)
  • bw/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (5)
  • NSEC3 proving non-existence of org.bw/A: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of org.bw/A: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of org.bw/AAAA: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of org.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.

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