_acme-challenge.mihirr-home.duckdns.org
Updated:
2025-07-17 06:12:44 UTC (152 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (1)
- _acme-challenge.mihirr-home.duckdns.org/A
Secure (1)
- org/SOA
DNSKEY/DS/NSEC status
Secure (9)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 38696)
- ./DNSKEY (alg 8, id 46441)
- ./DNSKEY (alg 8, id 53148)
- NSEC3 proving non-existence of duckdns.org/DS
- org/DNSKEY (alg 8, id 26974)
- org/DNSKEY (alg 8, id 55098)
- org/DNSKEY (alg 8, id 8958)
- org/DS (alg 8, id 26974)
Delegation status
Insecure (1)
- org to duckdns.org
Secure (1)
- . to org
Notices
Errors (2)
- duckdns.org zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (3.97.51.116)
- duckdns.org/DNSKEY: No response was received from the server over TCP (tried 12 times). See RFC 1035, Sec. 4.2. (3.97.51.116, TCP_-_EDNS0_4096_D_KN)
Warnings (3)
- NSEC3 proving non-existence of duckdns.org/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of duckdns.org/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- _acme-challenge.mihirr-home.duckdns.org/A: 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. (15.222.19.97, UDP_-_EDNS0_4096_D_KN)
JavaScript is required to make the graph below interactive.
