A certificate client — Certbot, a hosting panel, Caddy, a CDN — proved to Let’s Encrypt or another ACME certificate authority that it controls the domain, by publishing a one-time value here. It is how wildcard certificates are issued. Once the certificate is issued, the value is spent.
Name: _acme-challenge Type: TXT Value: ufWSbwSht2uaTwQc3p5unfZc3lHs9Sv_wS4ihh-UmG4
| Added by | Let’s Encrypt and other ACME certificate authorities — certificate issuance (DNS-01) |
| Can it be deleted? | It can go once verification is complete, the service says |
| Value | 43 characters: a hash of the challenge and the ACME account key |
| Required for | Wildcard certificates (Let’s Encrypt) |
Look for it on your domain
Enter a domain: we look up its TXT records, and _acme-challenge under it, and say whether this one is there — naming every other record we recognise.
What it is for
ACME is the protocol behind Let’s Encrypt and a growing number of certificate authorities. In the DNS-01 check, the client publishes a value at _acme-challenge under the name it wants a certificate for; the authority looks it up, and issues the certificate if it matches. Let’s Encrypt issues wildcard certificates only this way.
Why it is on your domain
- Your server, hosting panel or CDN obtained or renewed a certificate using a DNS check.
- A leftover value from an earlier issuance that was never cleaned up.
Can you delete it?
The value itself, yes: RFC 8555 says the client should remove it once the check is complete, and Let’s Encrypt asks you to clean up old values, because it starts rejecting responses that grow too large. Several values at once are allowed while renewals overlap.
Not a CNAME: if _acme-challenge is a CNAME pointing to another zone or a DNS provider, it delegates the check so renewals can run automatically — removing it stops them.
Questions
What is _validation-persist?
A newer, permanent kind of certificate check, approved in October 2025, designed to stay in place for every renewal — unlike _acme-challenge. It has its own page.
Sources
Checked on 26 September 2026 against these official sources:
- RFC 8555 — rfc-editor.org
- Challenge Types — letsencrypt.org
- FAQ — letsencrypt.org