If your domain isn't verifying in SendX, this article covers the most common errors and how to fix them. SendX shows specific error messages that tell you exactly what went wrong, so you can usually resolve the issue in minutes.
When you'll need this
Read this article if you see red error banners on your domain authentication page, one or more of your DNS records shows as failed, you've waited more than 24 hours and verification still isn't working, or you recently made DNS changes and something broke.
How verification works
When you click "Recheck Status," SendX checks each of your four DNS records independently:
Record | What SendX checks |
sp-dkim._domainkey (TXT) | DKIM signature key exists and matches |
sp-bounce (CNAME) | Bounce handling record points to correct destination |
sp-track (CNAME) | Tracking record points to correct destination |
_dmarc (TXT) | DMARC record exists and has valid syntax |
If any record fails, SendX displays a red error banner at the top of your domain page explaining the specific problem.
Important: You need at least three records verified to send emails: DKIM, bounce (ReturnPath), and DMARC. If any of these three fail, sending from that domain is blocked. The tracking record (sp-track) is required for click and open tracking in your campaigns.
Error 1: Double domain (record name appended twice)
What the error looks like:
DKIM Verification Failed DNS record found at 'sp-dkim._domainkey.yourdomain.com.yourdomain.com' instead of 'sp-dkim._domainkey.yourdomain.com'. Your DNS manager likely auto-appends the domain. Please delete the record and create it using just the prefix part.
What happened:
This is the most common authentication error. When you added the DNS record, you entered the full domain name (like sp-bounce.yourdomain.com) in the host field. But your DNS provider automatically appends your domain to whatever you enter, which created a doubled-up record like sp-bounce.yourdomain.com.yourdomain.com.
How to fix it:
Go to your DNS provider
Delete the incorrectly named record
Add the record again, entering only the prefix part
For example:
Instead of entering | Enter just |
sp-dkim._domainkey.yourdomain.com | sp-dkim._domainkey |
sp-bounce.yourdomain.com | sp-bounce |
sp-track.yourdomain.com | sp-track |
_dmarc.yourdomain.com | _dmarc |
Most DNS providers (GoDaddy, Namecheap, Cloudflare, Google Domains) auto-append your domain. Some providers like AWS Route53 let you enter the full domain. Check your provider's documentation if you're unsure.
After fixing the record, return to SendX and click Recheck Status.
Error 2: No DMARC record found
What the error looks like:
DMARC Verification Failed No DMARC record found. Please add a TXT record with host '_dmarc' and value 'v=DMARC1; p=none;'
What happened:
Your domain doesn't have a DMARC record in DNS. This is common if you're setting up email authentication for the first time. DMARC is required by Gmail, Yahoo, and other major inbox providers for bulk email senders.
How to fix it:
Go to your DNS provider
Add a new TXT record
Set the host to
_dmarcSet the value to
v=DMARC1; p=none;Save the record
Wait for DNS propagation (a few minutes to 24 hours) and click Recheck Status in SendX.
If you're not sure how to add the record in your specific DNS provider, see our provider-specific guides:
Google Domains step-by-step domain authentication
Cloudflare step-by-step domain authentication
GoDaddy step-by-step domain authentication
Namecheap step-by-step domain authentication
AWS Route53 step-by-step domain authentication
Error 3: Invalid DMARC record
What the error looks like:
DMARC Verification Failed DMARC verification failed. Please ensure you have a valid DMARC record configured for your domain.
What happened:
Your domain has a DMARC record, but the syntax isn't valid. Common causes include typos, missing required tags, or formatting issues.
How to fix it:
First, check your current DMARC record. You can use MXToolbox DMARC Lookup to see exactly what's published.
Then check for these common syntax problems:
Problem | What's wrong | Correct format |
Missing version tag |
|
|
Wrong version |
|
|
Version not first |
|
|
Invalid policy value |
|
|
Extra spaces or characters |
|
|
Multiple DMARC records | Two TXT records for _dmarc | Only one DMARC record allowed per domain |
If you have an existing DMARC record from another service, don't add a second one. Fix the existing record's syntax instead. You can only have one DMARC record per domain.
If you're not sure what's wrong, the simplest fix is to replace your current DMARC record with: v=DMARC1; p=none;
This is a valid, safe starting point. Just be aware that if you're replacing a more restrictive policy (like p=reject), switching to p=none will reduce your protection until you update it.
Error 4: Duplicate DKIM selectors
What the error looks like:
DKIM verification may fail if another service already has a DKIM record using the same selector.
What happened:
Your domain may have a DKIM record from another email provider that conflicts with the SendX DKIM record. This isn't about having too many DKIM records (you can have multiple), but specifically about two records sharing the same selector name.
How to fix it:
Check your DNS for any existing TXT records at
sp-dkim._domainkeyIf another service is using the exact same selector (
sp-dkim), one of them will need to changeSendX uses the
sp-dkimselector. Other services typically use their own selectors (likegoogle,mailchimp,sendgrid), so conflicts are rare
If you do find a conflict, contact SendX support with your domain name so they can help resolve it.
General troubleshooting checklist
If your records aren't verifying and you don't see a specific error banner, work through this list:
Check 1: Have you waited long enough?
DNS propagation can take up to 48 hours. Most changes appear within a few hours, but some providers and record types take longer. If you just added the records, wait and recheck later.
Check 2: Are all four records present?
Verify each record exists in your DNS:
sp-dkim._domainkey (TXT)
sp-bounce (CNAME)
sp-track (CNAME)
_dmarc (TXT)
Missing records are easy to miss, especially if you're adding them one at a time.
Check 3: Are the record types correct?
A common mistake is adding a CNAME record as a TXT record or vice versa.
Record | Must be type |
sp-dkim._domainkey | TXT |
sp-bounce | CNAME |
sp-track | CNAME |
_dmarc | TXT |
Check 4: Were the values copied correctly?
Use the copy button in SendX rather than manually selecting the text. DKIM values especially are long and easy to truncate accidentally.
Check 5: Is the record on the right domain?
If you have multiple domains or subdomains, confirm you added the records to the correct one.
Check 6: Is proxy disabled? (Cloudflare users)
If your domain uses Cloudflare, make sure proxy status is set to DNS only (gray cloud) for both CNAME records. Proxied CNAME records will fail email verification.
Verify records externally
If you're stuck, use these free tools to check whether your records are publicly visible. Sometimes a record looks correct in your DNS provider but isn't propagating correctly.
MXToolbox
DKIM: https://mxtoolbox.com/dkim.aspx (use selector
sp-dkim)DNS Lookup: https://mxtoolbox.com/DNSLookup.aspx
DNSChecker
Check propagation across multiple global servers.
Google Admin Toolbox
Comprehensive DNS check including DKIM and DMARC.
If an external tool shows your record but SendX doesn't verify it, the record format may be slightly off. Compare exactly what the tool shows with what SendX expects.
Records that were working but stopped
If your domain was previously verified and suddenly shows as failed:
DNS records deleted accidentally. Check your DNS provider to make sure the records still exist. Some providers remove records during migrations or account changes.
Domain expired or transferred. If your domain registration lapsed or you transferred to a new registrar, DNS records may have been lost. Re-add them at your new provider.
DNS provider changed. If you switched nameservers (for example, moving to or from Cloudflare), your old DNS records don't transfer automatically. You need to re-add them at your new DNS provider.
Someone else modified your DNS. If multiple people have access to your DNS, someone may have accidentally edited or removed a record.
When to contact support
Contact SendX support if:
You've verified all records are correct using external tools but SendX still shows failures
You see an error message not covered in this article
You suspect a conflict with another email service
You need help reading or interpreting DNS records
When contacting support, include your domain name and screenshots of both the SendX error and your DNS records. This helps the team resolve the issue faster.
Common questions
Can I send emails while some records are failing?
You need DKIM, bounce (sp-bounce), and DMARC verified to send emails. If any of these three fail, sending is blocked for that domain. The tracking record (sp-track) is separate, if it's not verified, your emails will send but click and open tracking won't work.
How often can I click Recheck Status?
As often as you want. There's no cooldown or limit.
I fixed the error but the status didn't change.
Click "Recheck Status" again. SendX doesn't poll your DNS automatically, it only checks when you ask it to.
Why does my error mention a different domain than what I entered?
This usually means the double-domain issue. Your DNS provider auto-appended your domain, creating a record like sp-bounce.yourdomain.com.yourdomain.com. See Error 1 above.
I have a DMARC record from another service. Do I need to change it?
No, as long as it's valid. SendX works with any valid DMARC policy. You only need to fix it if the syntax is invalid or if you don't have one at all.