View on GitHub

DNSViz: A DNS visualization tool

nzb.su

Updated: 2021-11-03 03:40:28 UTC (1145 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 (5)
  • nzb.su/A
  • nzb.su/MX
  • nzb.su/NS
  • nzb.su/SOA
  • nzb.su/TXT
Secure (1)
  • su/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (6)
  • ./DNSKEY (alg 8, id 14748)
  • ./DNSKEY (alg 8, id 20326)
  • NSEC3 proving non-existence of nzb.su/DS
  • su/DNSKEY (alg 8, id 28900)
  • su/DNSKEY (alg 8, id 34821)
  • su/DS (alg 8, id 28900)

Delegation statusDelegation status

Insecure (1)
  • su to nzb.su
Secure (1)
  • . to su

NoticesNotices

Errors (4)
  • NSEC3 proving non-existence of nzb.su/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 nzb.su/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • su zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:678:14:0:193:232:156:17)
  • nzb.su/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (3)
  • NSEC3 proving non-existence of nzb.su/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of nzb.su/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • nzb.su/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