All help articles

Email & sending domains

Why your sending domain won't verify

You added the DNS records and Check DNS still says no. The usual causes, in the order worth checking.

Updated 22 October 2026

You added the CNAME records, you've clicked Check DNS, and it still won't verify. Almost always one of these.

It hasn't propagated yet

DNS changes take time to reach us — usually minutes, sometimes up to 48 hours. If you added the records in the last few minutes, that's the likely answer.

Add them, then come back later and click Check DNS again. Clicking repeatedly doesn't make it faster.

Your provider added your domain to the end

This is the most common real fault, and the hardest to see.

Some providers — GoDaddy and Namecheap among them — append your domain to whatever you type in the Host field. Paste abc123.yourcompany.com and you get abc123.yourcompany.com.yourcompany.com, which resolves to nothing.

Look at the record as your provider now lists it, not at what you typed. If the domain appears twice, delete the domain part from the Host field and save it again.

Cloudflare is proxying the record

If your DNS is on Cloudflare, each CNAME must be DNS only — the grey cloud, not the orange one. A proxied record returns Cloudflare's address instead of the one we're checking for, so verification fails while the record looks perfectly correct.

The value was altered

Copy the Host and Value with the copy buttons rather than retyping them. Things that break it:

  • A trailing dot added or removed by your provider
  • A capital letter changed — some providers lowercase automatically, which is fine, but a manual change isn't
  • A truncated value, if you copied from a narrow column
  • Any character added

The values are long and meaningless, so a mistake in one is invisible to read past.

Only some of the records were added

All the records have to be there. Adding only some won't verify the domain. Choose View records to see which ones are ready and which still need attention.

Compare the list on the page against what your provider shows, one at a time.

You already have a conflicting record

If a record with the same Host already exists — often from a previous email provider — some DNS providers silently keep the old one instead of adding yours. Delete the old record first.

Your domain provider isn't where your DNS actually lives

If you bought the domain in one place and pointed its nameservers somewhere else, the records must go where the nameservers point, not where you bought it. Adding them at the registrar does nothing in that case.

When it verifies and mail still doesn't arrive

Verification means we may send as your domain; it doesn't mean every message lands in an inbox. Check the campaign's own results first — a message recorded as delivered and one that was never sent are different problems.

  • Authenticate your sending domain
  • Verify a sender email
  • Connect your website domain
  • Why a campaign didn't send

Was this article helpful?

Why your sending domain won't verify — Qcom Help