View on GitHub

DNSViz: A DNS visualization tool

coder.show

« 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 (4)
  • coder.show/CNAME
  • coder.show/NS
  • fm/SOA
  • hosted.fireside.fm/A
Secure (2)
  • ./SOA
  • show/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Insecure (4)
  • NSEC3 proving non-existence of fireside.fm/DS
  • fm/DNSKEY (alg 8, id 26186)
  • fm/DNSKEY (alg 8, id 32310)
  • fm/DNSKEY (alg 8, id 46926)
Secure (8)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 33853)
  • NSEC proving non-existence of fm/DS
  • NSEC3 proving non-existence of coder.show/DS
  • show/DNSKEY (alg 8, id 44874)
  • show/DNSKEY (alg 8, id 64339)
  • show/DS (alg 8, id 64339)
  • show/DS (alg 8, id 64339)

Delegation statusDelegation status

Insecure (3)
  • . to fm
  • fm to fireside.fm
  • show to coder.show
Secure (1)
  • . to show

NoticesNotices

Errors (5)
  • NSEC3 proving non-existence of coder.show/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 coder.show/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 fireside.fm/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 fireside.fm/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • coder.show/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (17)
  • NSEC3 proving non-existence of coder.show/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of coder.show/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • coder.show/CNAME: The server responded with no OPT record, rather than with RCODE FORMERR. See RFC 6891, Sec. 7. (64.98.148.13, 216.40.47.26, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • coder.show/CNAME: The server returned CNAME for coder.show, but records of other types exist at that name. See RFC 2181, Sec. 10.1.
  • coder.show/NS: The server responded with no OPT record, rather than with RCODE FORMERR. See RFC 6891, Sec. 7. (216.40.47.26, UDP_-_EDNS0_4096_D_K)
  • show/DS (alg 8, id 64339): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • show/DS (alg 8, id 64339): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • show/DS (alg 8, id 64339): 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.
  • show/DS (alg 8, id 64339): 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.
  • coder.show/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
  • rkyt6248ai.coder.show/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • coder.show/TXT has warnings; select the "Denial of existence" DNSSEC option to see them.
  • coder.show/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
  • coder.show/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • coder.show/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • coder.show/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • coder.show/SOA 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