View on GitHub

DNSViz: A DNS visualization tool

small._testentry.breakpoint.cc

Updated: 2020-06-19 09:35:22 UTC (1647 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

Secure (3)
  • breakpoint.cc/SOA
  • small._testentry.breakpoint.cc/A (NODATA)
  • small._testentry.breakpoint.cc/AAAA (NODATA)

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (11)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 48903)
  • NSEC3 proving non-existence of small._testentry.breakpoint.cc/A
  • NSEC3 proving non-existence of small._testentry.breakpoint.cc/AAAA
  • breakpoint.cc/DNSKEY (alg 8, id 17836)
  • breakpoint.cc/DNSKEY (alg 8, id 9361)
  • breakpoint.cc/DS (alg 8, id 9361)
  • cc/DNSKEY (alg 8, id 3849)
  • cc/DNSKEY (alg 8, id 519)
  • cc/DS (alg 8, id 519)
  • cc/DS (alg 8, id 519)

Delegation statusDelegation status

Secure (2)
  • . to cc
  • cc to breakpoint.cc

NoticesNotices

Errors (5)
  • NSEC3 proving non-existence of small._testentry.breakpoint.cc/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 small._testentry.breakpoint.cc/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 small._testentry.breakpoint.cc/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 small._testentry.breakpoint.cc/AAAA: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • breakpoint.cc/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (9)
  • NSEC3 proving non-existence of small._testentry.breakpoint.cc/A: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of small._testentry.breakpoint.cc/A: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of small._testentry.breakpoint.cc/AAAA: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of small._testentry.breakpoint.cc/AAAA: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • cc/DS (alg 8, id 519): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • cc/DS (alg 8, id 519): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • cc/DS (alg 8, id 519): 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.
  • cc/DS (alg 8, id 519): 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.
  • breakpoint.cc/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