dren.net
Updated:
2023-11-07 14:03:44 UTC (410 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (4)
- dren.net/MX
- dren.net/NS
- dren.net/SOA
- dren.net/TXT
DNSKEY/DS/NSEC status
Secure (12)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 46780)
- dren.net/DNSKEY (alg 10, id 17708)
- dren.net/DNSKEY (alg 10, id 25698)
- dren.net/DNSKEY (alg 13, id 18414)
- dren.net/DNSKEY (alg 13, id 36368)
- dren.net/DS (alg 13, id 36368)
- net/DNSKEY (alg 13, id 37331)
- net/DNSKEY (alg 13, id 44222)
- net/DNSKEY (alg 8, id 35886)
- net/DNSKEY (alg 8, id 51464)
- net/DS (alg 8, id 35886)
Delegation status
Secure (2)
- . to net
- net to dren.net
Notices
Errors (3)
- dren.net zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (140.32.131.142, 2001:480:31:ffff::53)
- dren.net/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (140.32.131.142, 2001:480:31:ffff::53, UDP_-_NOEDNS_)
- dren.net/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (25)
- RRSIG dren.net/DNSKEY alg 10, id 17708: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG dren.net/DNSKEY alg 10, id 17708: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG dren.net/DNSKEY alg 10, id 17708: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG dren.net/DNSKEY alg 10, id 17708: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG dren.net/DNSKEY alg 10, id 25698: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG dren.net/DNSKEY alg 10, id 25698: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG dren.net/DNSKEY alg 10, id 25698: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG dren.net/DNSKEY alg 10, id 25698: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG dren.net/MX alg 10, id 17708: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG dren.net/NS alg 10, id 17708: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG dren.net/SOA alg 10, id 17708: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG dren.net/TXT alg 10, id 17708: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- dren.net/DNSKEY (alg 10, id 17708): 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. (140.32.59.226, 140.32.61.226, UDP_-_EDNS0_4096_D_KN)
- dren.net/DNSKEY (alg 10, id 25698): 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. (140.32.59.226, 140.32.61.226, UDP_-_EDNS0_4096_D_KN)
- dren.net/DNSKEY (alg 13, id 18414): 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. (140.32.59.226, 140.32.61.226, UDP_-_EDNS0_4096_D_KN)
- dren.net/DNSKEY (alg 13, id 36368): 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. (140.32.59.226, 140.32.61.226, UDP_-_EDNS0_4096_D_KN)
- dren.net/MX: 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. (140.32.59.226, UDP_-_EDNS0_4096_D_KN)
- dren.net/SOA: 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. (140.32.59.226, 2001:480:a0:f003::226, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
- dren.net/TXT: 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. (140.32.59.226, UDP_-_EDNS0_4096_D_KN)
- dren.net/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
- dren.net/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
- dren.net/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
- dren.net/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- dren.net/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- np3iv9uthg.dren.net/A has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
