View on GitHub

DNSViz: A DNS visualization tool

2.node.pautje52.me

« 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 (2)
  • 2.node.pautje52.me/A (NXDOMAIN)
  • pautje52.me/A (NXDOMAIN)
Secure (1)
  • me/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (8)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 951)
  • NSEC3 proving non-existence of 2.node.pautje52.me/A
  • NSEC3 proving non-existence of pautje52.me/A
  • me/DNSKEY (alg 8, id 16080)
  • me/DNSKEY (alg 8, id 29439)
  • me/DNSKEY (alg 8, id 45352)
  • me/DS (alg 8, id 45352)

Delegation statusDelegation status

Secure (1)
  • . to me

NoticesNotices

Errors (6)
  • NSEC3 proving non-existence of 2.node.pautje52.me/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 2.node.pautje52.me/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 pautje52.me/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 pautje52.me/A: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • me zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:500:54::1)
  • me/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (5)
  • NSEC3 proving non-existence of 2.node.pautje52.me/A: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of 2.node.pautje52.me/A: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of pautje52.me/A: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of pautje52.me/A: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • me/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