View on GitHub

DNSViz: A DNS visualization tool

amanite.site

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

RRset statusRRset status

Secure (1)
  • site/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (8)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 26116)
  • NSEC3 proving non-existence of amanite.site/DS
  • site/DNSKEY (alg 8, id 35826)
  • site/DNSKEY (alg 8, id 51144)
  • site/DNSKEY (alg 8, id 51676)
  • site/DS (alg 8, id 51676)
  • site/DS (alg 8, id 51676)

Delegation statusDelegation status

Lame (1)
  • site to amanite.site
Secure (1)
  • . to site

NoticesNotices

Errors (17)
  • NSEC3 proving non-existence of amanite.site/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 amanite.site/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • amanite.site zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (193.48.57.184)
  • amanite.site zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (193.48.57.184)
  • amanite.site zone: There was an error resolving the following NS name(s) to address(es): ns1.amanite.site
  • amanite.site/A: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (193.48.57.184, UDP_-_EDNS0_4096_D_K)
  • amanite.site/AAAA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (193.48.57.184, UDP_-_EDNS0_4096_D_K)
  • amanite.site/DNSKEY: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (193.48.57.184, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • amanite.site/MX: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (193.48.57.184, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • amanite.site/NS: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (193.48.57.184, UDP_-_EDNS0_4096_D_K)
  • amanite.site/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (193.48.57.184, TCP_-_EDNS0_4096_D)
  • amanite.site/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (193.48.57.184, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K_0x20)
  • amanite.site/TXT: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (193.48.57.184, UDP_-_EDNS0_4096_D_K)
  • amanite.site/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • amanite.site/DS has errors; select the "Denial of existence" DNSSEC option to see them.
  • d8j9nxc1tl.amanite.site/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • amanite.site/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (4)
  • site/DS (alg 8, id 51676): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • site/DS (alg 8, id 51676): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • site/DS (alg 8, id 51676): 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.
  • site/DS (alg 8, id 51676): 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.

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