My domain is still unverified
The usual cause is propagation: the records are correct but the old values are still cached. If the previous TTL was long, that can take hours. Nothing needs re-adding while you wait.
The second most common cause is a second SPF record. A domain may only have one, and if something else — a newsletter tool, a CRM, an old host — already added one, the two conflict and neither is trusted. The fix is to merge them into a single record rather than to delete ours.
Third is a record added at the wrong name: a host that appends the domain automatically will turn an entered value of `mail.example.com` into `mail.example.com.example.com`. If verification keeps failing with records that look right, check the fully-qualified name your provider actually stored.
Did this not answer it?
Mail reaches a person rather than a queue. Include the domain and the exact error if there is one — it saves a round trip.
sales@ruber.meMore in Domains and DNS
- Which DNS records we add, and whyMX, SPF, DKIM and DMARC — what each one is actually for.
- Connect Cloudflare, or add records by handAuthorize once, or take the records and add them yourself. Your DNS does not move.
- Run more than one domainSeveral domains under one account, verified separately, billed as one plan.