coder.show
Updated:
2021-11-05 00:06:59 UTC (1143 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (4)
- coder.show/CNAME
- coder.show/MX
- coder.show/NS
- hosted.fireside.fm/A
Secure (3)
- fm/SOA
- fm/SOA
- show/SOA
DNSKEY/DS/NSEC status
Secure (15)
- ./DNSKEY (alg 8, id 14748)
- ./DNSKEY (alg 8, id 20326)
- NSEC3 proving non-existence of coder.show/DS
- NSEC3 proving non-existence of fireside.fm/DS
- fm/DNSKEY (alg 8, id 26186)
- fm/DNSKEY (alg 8, id 31618)
- fm/DNSKEY (alg 8, id 38119)
- fm/DS (alg 8, id 26186)
- show/DNSKEY (alg 8, id 19413)
- show/DNSKEY (alg 8, id 37234)
- show/DNSKEY (alg 8, id 43876)
- show/DNSKEY (alg 8, id 59763)
- show/DS (alg 8, id 37234)
- show/DS (alg 8, id 37234)
- show/DS (alg 8, id 43876)
Delegation status
Insecure (2)
- fm to fireside.fm
- show to coder.show
Secure (2)
- . to fm
- . to show
Notices
Errors (7)
- 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.
- RRSIG NSEC3 proving non-existence of coder.show/DS alg 8, id 19413: The TTL of the RRset (86400) exceeds the value of the Original TTL field of the RRSIG RR covering it (3600). See RFC 4035, Sec. 2.2.
- show zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2a01:8840:1f::43)
- coder.show/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (14)
- 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 returned CNAME for coder.show, but records of other types exist at that name. See RFC 2181, Sec. 10.1.
- show/DS (alg 8, id 37234): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- show/DS (alg 8, id 37234): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- show/DS (alg 8, id 37234): 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 37234): 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/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/NSEC3PARAM 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.
JavaScript is required to make the graph below interactive.
