tn
Updated:
2022-02-12 21:02:36 UTC (1063 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (4)
- tn/NS
- tn/SOA
- tn/SOA
- tn/SOA
DNSKEY/DS/NSEC status
Secure (5)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 9799)
- tn/DNSKEY (alg 8, id 36171)
- tn/DNSKEY (alg 8, id 8629)
- tn/DS (alg 8, id 8629)
Delegation status
Secure (1)
- . to tn
Notices
Errors (9)
- . to tn: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (2c0f:fab0:ffff:5:41:228:63:62, TCP_-_NOEDNS_)
- . to tn: The DS RRset for the zone included algorithm 8 (RSASHA256), but no DS RR matched a DNSKEY with algorithm 8 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (2c0f:fab0:ffff:5:41:228:63:62, TCP_-_NOEDNS_)
- tn/DNSKEY (alg 8, id 36171): DNSSEC was effectively downgraded because no response was received from the server over UDP (tried 11 times) with EDNS enabled. See RFC 6891, Sec. 7, RFC 2671, Sec. 5.3. (2c0f:fab0:ffff:5:41:228:63:62, TCP_-_NOEDNS_)
- tn/DNSKEY (alg 8, id 36171): No response was received from the server over UDP (tried 11 times) until EDNS was disabled (however, this server appeared to respond legitimately to other queries with EDNS enabled). See RFC 6891, Sec. 6.2.6. (2c0f:fab0:ffff:5:41:228:63:62, UDP_-_EDNS0_4096_D_KN)
- tn/DNSKEY (alg 8, id 36171): The DNSSEC records necessary to validate the response could not be retrieved from the server. See RFC 4035, Sec. 3.1.1, RFC 4035, Sec. 3.1.3. (2c0f:fab0:ffff:5:41:228:63:62, UDP_-_EDNS0_4096_D_KN)
- tn/DNSKEY (alg 8, id 8629): DNSSEC was effectively downgraded because no response was received from the server over UDP (tried 11 times) with EDNS enabled. See RFC 6891, Sec. 7, RFC 2671, Sec. 5.3. (2c0f:fab0:ffff:5:41:228:63:62, TCP_-_NOEDNS_)
- tn/DNSKEY (alg 8, id 8629): No response was received from the server over UDP (tried 11 times) until EDNS was disabled (however, this server appeared to respond legitimately to other queries with EDNS enabled). See RFC 6891, Sec. 6.2.6. (2c0f:fab0:ffff:5:41:228:63:62, UDP_-_EDNS0_4096_D_KN)
- tn/DNSKEY (alg 8, id 8629): The DNSSEC records necessary to validate the response could not be retrieved from the server. See RFC 4035, Sec. 3.1.1, RFC 4035, Sec. 3.1.3. (2c0f:fab0:ffff:5:41:228:63:62, UDP_-_EDNS0_4096_D_KN)
- tn/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (2)
- tn/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- tn/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
