A standing permission for one certificate authority account to get certificates for the domain, approved by the CA/Browser Forum in October 2025. Unlike _acme-challenge it is published once and left in place, so renewals need no new DNS change.
Name: _validation-persist Type: TXT Value: letsencrypt.org; accounturi=https://acme-v02.api.letsencrypt.org/acme/acct/1234567890
| Added by | Let’s Encrypt, DigiCert and other certificate authorities — persistent domain validation (DNS-PERSIST-01) |
| Can it be deleted? | Keep it — the service checks it again, and removing it undoes the verification |
| Value | The authority’s domain, then accounturi= the account allowed to request certificates |
| Options | policy=wildcard for wildcards; persistUntil= an end date |
Look for it on your domain
Enter a domain: we look up its TXT records, and _validation-persist under it, and say whether this one is there — naming every other record we recognise.
What it is for
The record names the certificate authority and the account it trusts. The authority re-reads it at each issuance, so certificates for the domain can be renewed without publishing anything new. DigiCert re-checks it about every five days.
Why it is on your domain
- Your server, hosting or certificate management set up persistent validation with Let’s Encrypt, DigiCert or another authority.
Can you delete it?
Keep it while that account gets certificates for the domain: Let’s Encrypt designed it to be reused for issuance and every renewal, and DigiCert says not to delete it after validation. Remove it only to withdraw the permission.
Sources
Checked on 26 September 2026 against these official sources:
- DNS-PERSIST-01: A New Model for DNS-based Challenge Validation — letsencrypt.org
- Add and validate a domain using DNS TXT record — docs.digicert.com
- CA/Browser Forum TLS Baseline Requirements — raw.githubusercontent.com