View on GitHub

DNSViz: A DNS visualization tool

_acme-challenge.customer2.fangfree.com

Updated: 2023-04-26 19:08:31 UTC (454 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)
  • _acme-challenge.customer2.fangfree.com/A (NXDOMAIN)
  • customer2.fangfree.com/SOA
  • fangfree.com/SOA
Secure (2)
  • com/SOA
  • com/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (6)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 60955)
  • NSEC3 proving non-existence of fangfree.com/DS
  • com/DNSKEY (alg 8, id 30909)
  • com/DNSKEY (alg 8, id 46551)
  • com/DS (alg 8, id 30909)

Delegation statusDelegation status

Incomplete (1)
  • fangfree.com to customer2.fangfree.com
Insecure (1)
  • com to fangfree.com
Secure (1)
  • . to com

NoticesNotices

Errors (3)
  • customer2.fangfree.com zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (164.92.112.207)
  • customer2.fangfree.com zone: There was an error resolving the following NS name(s) to address(es): ns2.customer2.fangfree.com
  • fangfree.com to customer2.fangfree.com: No delegation NS records were detected in the parent zone (fangfree.com). This results in an NXDOMAIN response to a DS query (for DNSSEC), even if the parent servers are authoritative for the child. See RFC 1034, Sec. 4.2.2. (5.161.57.22, UDP_-_EDNS0_4096_D_KN)

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