auth.acme-dns.io
Updated:
2025-06-05 15:06:15 UTC (41 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (1)
- acme-dns.io/SOA
Secure (1)
- io/SOA
DNSKEY/DS/NSEC status
Secure (8)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 38696)
- ./DNSKEY (alg 8, id 53148)
- NSEC3 proving non-existence of acme-dns.io/DS
- io/DNSKEY (alg 8, id 17133)
- io/DNSKEY (alg 8, id 56505)
- io/DNSKEY (alg 8, id 57355)
- io/DS (alg 8, id 57355)
Delegation status
Lame (1)
- acme-dns.io to auth.acme-dns.io
Insecure (1)
- io to acme-dns.io
Secure (1)
- . to io
Notices
Errors (4)
- auth.acme-dns.io zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (49.12.60.200)
- auth.acme-dns.io zone: There was an error resolving the following NS name(s) to address(es): ns.auth.acme-dns.io
- auth.acme-dns.io/A: The UDP connection was refused (ECONNREFUSED). See RFC 1035, Sec. 4.2. (49.12.60.200, UDP_-_EDNS0_4096_D_KN)
- auth.acme-dns.io/NS: The UDP connection was refused (ECONNREFUSED). See RFC 1035, Sec. 4.2. (49.12.60.200, UDP_-_EDNS0_4096_D_KN)
Warnings (2)
- NSEC3 proving non-existence of acme-dns.io/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of acme-dns.io/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
JavaScript is required to make the graph below interactive.
