Domain verification failing
If you've added the verification line to your domain settings and Verify now keeps coming back as failed, work through the checks below. The fix is almost always one of these.
1. Wait a few minutes
Domain settings can take time to propagate. After saving the line at your domain provider, wait 2 to 5 minutes before clicking Verify now again. For some providers, propagation can take longer (up to an hour in rare cases).
2. Check the line was copied exactly
Open the verification dialog in One Privacy and copy the line again with the copy icon.
Compare it to what's in your domain settings. Common mistakes:
A space at the start or end of the value.
The line was wrapped onto two lines and only the first line was saved.
Quotation marks were added by your domain provider's interface.
3. Check the record type
The record must be a TXT record. Some interfaces default to A or CNAME; switch to TXT.
4. Check the host or name
The host should be @ (or blank, depending on your provider). Setting it to www or any other subdomain won't work.
If your provider uses a different convention (some use the bare domain instead of @), use the convention they document for "root" records.
5. Confirm you saved at the right domain
If you have several domains in the same provider account, double-check you're editing the right one.
If your domain uses external nameservers (Cloudflare in front of your registrar, for example), make sure you're editing the records at the provider that's actually authoritative.
6. Test the record yourself
If you have a developer or IT colleague handy, ask them to run a quick TXT lookup:
dig TXT yourdomain.com +short
The line you added should appear in the output. If it doesn't, the record hasn't been saved correctly or hasn't propagated yet.
7. Cloudflare proxy
If you use Cloudflare, the proxy doesn't affect TXT records, so this usually isn't the cause. But check that the record isn't being filtered by a Cloudflare page rule.