tn
Updated:
2024-10-17 20:05:33 UTC (69 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (2)
- tn/NS
- tn/SOA
DNSKEY/DS/NSEC status
Secure (5)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 61050)
- 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 (14)
- tn zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2c0f:fab0:ffff:4:41:228:62:63)
- tn/DNSKEY: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (196.216.168.25, TCP_-_NOEDNS_)
- tn/DNSKEY: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (196.216.168.25, UDP_-_EDNS0_512_D_KN)
- tn/NS: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (196.216.168.25, UDP_-_NOEDNS_)
- tn/NS: There was an error communicating with the server over UDP (EACCES). See RFC 1035, Sec. 4.2. (2c0f:fab0:ffff:4:41:228:62:63, UDP_-_EDNS0_4096_D_KN)
- tn/SOA: DNSSEC was effectively downgraded because the response had an invalid RCODE (SERVFAIL) with EDNS enabled. See RFC 6891, Sec. 7, RFC 2671, Sec. 5.3. (196.216.168.25, TCP_-_NOEDNS_)
- tn/SOA: DNSSEC was effectively downgraded because the response had an invalid RCODE (SERVFAIL) with EDNS enabled. See RFC 6891, Sec. 7, RFC 2671, Sec. 5.3. (196.216.168.25, UDP_-_NOEDNS_)
- tn/SOA: 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. (196.216.168.25, UDP_-_EDNS0_4096_D_KN)
- tn/SOA: The response had an invalid RCODE (SERVFAIL) until EDNS was disabled (however, this server appeared to respond legitimately to other queries with EDNS enabled). See RFC 6891, Sec. 6.2.6. (196.216.168.25, UDP_-_EDNS0_4096_D_KN)
- tn/SOA: The response had an invalid RCODE (SERVFAIL) until EDNS was disabled. See RFC 6891, Sec. 6.2.6. (196.216.168.25, TCP_-_EDNS0_4096_D_N)
- dsbfw.e7syp.tn/A has errors; select the "Denial of existence" DNSSEC option to see them.
- tn/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- tn/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- tn/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (7)
- tn/DNSKEY (alg 8, id 36171): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (41.228.63.62, UDP_-_EDNS0_4096_D_KN)
- tn/DNSKEY (alg 8, id 8629): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (41.228.63.62, UDP_-_EDNS0_4096_D_KN)
- tn/NS: No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (147.28.0.39, UDP_-_EDNS0_4096_D_KN)
- tn/SOA: No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (147.28.0.39, UDP_-_EDNS0_4096_D_KN)
- dsbfw.e7syp.tn/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- tn/DNSKEY 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.
