View on GitHub

DNSViz: A DNS visualization tool

soylentnews.org

DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
  10. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Insecure (6)
  • soylentnews.org/A
  • soylentnews.org/AAAA
  • soylentnews.org/MX
  • soylentnews.org/NS
  • soylentnews.org/SOA
  • soylentnews.org/TXT
Secure (2)
  • org/SOA
  • org/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Insecure (2)
  • soylentnews.org/DNSKEY (alg 8, id 60615)
  • soylentnews.org/DNSKEY (alg 8, id 64450)
Secure (7)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 61050)
  • NSEC3 proving non-existence of soylentnews.org/DS
  • org/DNSKEY (alg 8, id 15678)
  • org/DNSKEY (alg 8, id 26974)
  • org/DNSKEY (alg 8, id 42393)
  • org/DS (alg 8, id 26974)

Delegation statusDelegation status

Insecure (1)
  • org to soylentnews.org
Secure (1)
  • . to org

NoticesNotices

Errors (19)
  • soylentnews.org zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (92.123.94.2, 92.123.94.3, 92.123.95.2, 92.123.95.3, 92.123.95.4, 2600:14c0:6::2, 2600:14c0:6::3, 2600:14c0:7::2, 2600:14c0:7::3, 2600:14c0:7::4)
  • soylentnews.org zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (92.123.94.2, 92.123.94.3, 92.123.95.2, 92.123.95.3, 92.123.95.4, 2600:14c0:6::2, 2600:14c0:6::3, 2600:14c0:7::2, 2600:14c0:7::3, 2600:14c0:7::4)
  • soylentnews.org zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2602:fd63:12::2)
  • soylentnews.org/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2602:fd63:12::2, UDP_-_NOEDNS_)
  • soylentnews.org/A: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (92.123.94.2, 92.123.94.3, 92.123.95.2, 92.123.95.3, 92.123.95.4, 2600:14c0:6::2, 2600:14c0:6::3, 2600:14c0:7::2, 2600:14c0:7::3, 2600:14c0:7::4, UDP_-_EDNS0_4096_D_KN)
  • soylentnews.org/AAAA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (92.123.94.2, 92.123.94.3, 92.123.95.2, 92.123.95.3, 92.123.95.4, 2600:14c0:6::2, 2600:14c0:6::3, 2600:14c0:7::2, 2600:14c0:7::3, 2600:14c0:7::4, UDP_-_EDNS0_4096_D_KN)
  • soylentnews.org/DNSKEY: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (92.123.94.2, 92.123.94.3, 92.123.95.2, 92.123.95.3, 92.123.95.4, 2600:14c0:6::2, 2600:14c0:6::3, 2600:14c0:7::2, 2600:14c0:7::3, 2600:14c0:7::4, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • soylentnews.org/MX: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (92.123.94.2, 92.123.94.3, 92.123.95.2, 92.123.95.3, 92.123.95.4, 2600:14c0:6::2, 2600:14c0:6::3, 2600:14c0:7::2, 2600:14c0:7::3, 2600:14c0:7::4, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • soylentnews.org/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2602:fd63:12::2, UDP_-_NOEDNS_)
  • soylentnews.org/NS: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (92.123.94.2, 92.123.94.3, 92.123.95.2, 92.123.95.3, 92.123.95.4, 2600:14c0:6::2, 2600:14c0:6::3, 2600:14c0:7::2, 2600:14c0:7::3, 2600:14c0:7::4, UDP_-_EDNS0_4096_D_KN)
  • soylentnews.org/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (92.123.94.2, 92.123.94.3, 92.123.95.2, 92.123.95.3, 92.123.95.4, 2600:14c0:6::2, 2600:14c0:6::3, 2600:14c0:7::2, 2600:14c0:7::3, 2600:14c0:7::4, TCP_-_EDNS0_4096_D_N)
  • soylentnews.org/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (92.123.94.2, 92.123.94.3, 92.123.95.2, 92.123.95.3, 92.123.95.4, 2600:14c0:6::2, 2600:14c0:6::3, 2600:14c0:7::2, 2600:14c0:7::3, 2600:14c0:7::4, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • soylentnews.org/TXT: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (92.123.94.2, 92.123.94.3, 92.123.95.2, 92.123.95.3, 92.123.95.4, 2600:14c0:6::2, 2600:14c0:6::3, 2600:14c0:7::2, 2600:14c0:7::3, 2600:14c0:7::4, UDP_-_EDNS0_4096_D_KN)
  • soylentnews.org/CDS has errors; select the "Denial of existence" DNSSEC option to see them.
  • soylentnews.org/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
  • soylentnews.org/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • soylentnews.org/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • soylentnews.org/CDNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • g95cn.9lx0g.soylentnews.org/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (5)
  • NSEC3 proving non-existence of soylentnews.org/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of soylentnews.org/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • org to soylentnews.org: Authoritative AAAA records exist for ns1.soylentnews.org, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • org to soylentnews.org: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the org zone): ns0.soylentnews.org See RFC 1034, Sec. 4.2.2.
  • soylentnews.org/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