View on GitHub

DNSViz: A DNS visualization tool

_acme-challenge.adopteunmanchot.com

Updated: 2024-01-15 15:08:23 UTC (about a year ago) Go to most recent »
DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
  10. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Secure (3)
  • adopteunmanchot.com/SOA
  • adopteunmanchot.com/SOA
  • adopteunmanchot.com/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (13)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 30903)
  • NSEC3 proving non-existence of _acme-challenge.adopteunmanchot.com/DS
  • NSEC3 proving non-existence of _acme-challenge.adopteunmanchot.com/DS
  • NSEC3 proving non-existence of _acme-challenge.adopteunmanchot.com/DS
  • adopteunmanchot.com/DNSKEY (alg 13, id 16872)
  • adopteunmanchot.com/DNSKEY (alg 13, id 19574)
  • adopteunmanchot.com/DS (alg 13, id 16872)
  • adopteunmanchot.com/DS (alg 13, id 19574)
  • com/DNSKEY (alg 13, id 19718)
  • com/DNSKEY (alg 13, id 4534)
  • com/DNSKEY (alg 13, id 46171)
  • com/DS (alg 13, id 19718)

Delegation statusDelegation status

Lame (1)
  • adopteunmanchot.com to _acme-challenge.adopteunmanchot.com
Secure (2)
  • . to com
  • com to adopteunmanchot.com

NoticesNotices

Errors (4)
  • NSEC3 proving non-existence of _acme-challenge.adopteunmanchot.com/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 _acme-challenge.adopteunmanchot.com/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • _acme-challenge.adopteunmanchot.com zone: The server(s) did not respond authoritatively for the namespace. See RFC 1035, Sec. 4.1.1. (78.46.82.168, 94.130.180.148, 109.237.252.179, 2001:67c:1298::1, 2a01:4f8:120:1104::2, 2a01:4f8:1c0c:4090::2, 2a01:729:16e::2)
  • _acme-challenge.adopteunmanchot.com/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (7)
  • NSEC3 proving non-existence of _acme-challenge.adopteunmanchot.com/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of _acme-challenge.adopteunmanchot.com/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of _acme-challenge.adopteunmanchot.com/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of _acme-challenge.adopteunmanchot.com/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of _acme-challenge.adopteunmanchot.com/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of _acme-challenge.adopteunmanchot.com/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • _acme-challenge.adopteunmanchot.com/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