View on GitHub

DNSViz: A DNS visualization tool

zedo.com

Updated: 2025-05-29 21:04:59 UTC (204 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 (1)
  • zedo.com/A
Secure (1)
  • com/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (7)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 38696)
  • ./DNSKEY (alg 8, id 53148)
  • NSEC3 proving non-existence of zedo.com/DS
  • com/DNSKEY (alg 13, id 19718)
  • com/DNSKEY (alg 13, id 40097)
  • com/DS (alg 13, id 19718)

Delegation statusDelegation status

Insecure (1)
  • com to zedo.com
Secure (1)
  • . to com

NoticesNotices

Errors (18)
  • zedo.com zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (162.159.24.117, 162.159.25.158)
  • zedo.com/A: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (162.159.25.158, UDP_-_NOEDNS_)
  • zedo.com/AAAA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (162.159.24.117, UDP_-_EDNS0_4096_D_KN)
  • zedo.com/AAAA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (162.159.25.158, UDP_-_NOEDNS_)
  • zedo.com/CDNSKEY: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (162.159.24.117, 162.159.25.158, UDP_-_NOEDNS_)
  • zedo.com/CDS: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (162.159.24.117, 162.159.25.158, UDP_-_NOEDNS_)
  • zedo.com/DNSKEY: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (162.159.24.117, 162.159.25.158, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • zedo.com/MX: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (162.159.24.117, UDP_-_NOEDNS_)
  • zedo.com/MX: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (162.159.24.117, 162.159.25.158, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
  • zedo.com/NS: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (162.159.24.117, 162.159.25.158, UDP_-_NOEDNS_)
  • zedo.com/NSEC3PARAM: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (162.159.24.117, 162.159.25.158, UDP_-_NOEDNS_)
  • zedo.com/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (162.159.24.117, 162.159.25.158, TCP_-_NOEDNS_)
  • zedo.com/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (162.159.24.117, 162.159.25.158, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
  • zedo.com/TXT: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (162.159.24.117, UDP_-_EDNS0_4096_D_KN)
  • zedo.com/TXT: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (162.159.25.158, UDP_-_NOEDNS_)
  • zedo.com/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • zedo.com/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • 871xq.py42n.zedo.com/A has errors; 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