Domain Verification Troubleshooting

This article covers the most common errors when verifying a sending domain in Yespo and how to fix them.

For the full setup steps, see Setting Up Email Domain Authentication. To learn how SPF, DKIM, DMARC, and domain alignment work, see FAQ: Email Authentication and Domain Reputation.

Most verification issues occur because DNS records are missing, incorrect, duplicated, added to the wrong DNS zone, or DNS changes have not fully propagated.

Before You Troubleshoot

Start with these checks, which resolve most cases:

• Match the values exactly. Each record's Name and Data must match what Yespo shows, character for character, with the correct record type: TXT, CNAME, or MX.
• Check where the record was added. Add the record to the DNS zone of the domain or subdomain you are verifying.
• Wait for propagation. DNS changes are not instant. DNS changes can take up to 48 hours to propagate.
• Refresh in Yespo. After updating DNS records, return to Settings → Domain verification and click Refresh or Verify domain.
• Confirm that the records are public. Use DNS Record Query or MxToolbox to check whether your records are visible to external mail servers.

If the records look correct and DNS changes have propagated but verification still fails, work through the specific cases below.

The Domain Won't Verify

Issue: The domain remains unverified even after you added the DNS records.

Possible causes:

• One or more records use the wrong record type.
• The Name or Data value does not match Yespo.
• The DNS provider appended your domain twice in the Name or Host field.
• DNS changes have not fully propagated yet.
• The records were added to the wrong DNS zone.

Solution:

1. Open the verification details in Settings → Domain verification.
2. Compare every record type, Name, and Data value with the values in Yespo.
3. Check the published records with a DNS lookup tool.
4. Fix any records whose values do not match Yespo.
5. Wait for propagation and click Refresh in Yespo.

How to check: Use a DNS lookup tool to confirm that each full record name resolves publicly and contains the expected value.

Missing MX Record for the Mailbox Domain

Issue: Yespo shows an error about a missing MX record for the primary or mailbox domain.

Possible cause: The domain used for regular email does not have a valid MX record, or the MX record points to the wrong destination.

Solution:

• On your mailbox domain, the MX record must point to your mailbox provider's mail server, for example Google Workspace, Microsoft 365, Amazon WorkMail, or another provider.
• The MX record must point to a domain name, not an IP address.
• Do not point your primary mailbox domain's MX record to a Yespo mail server.

The Yespo MX value is expected in a different place: with the Full + and Subdomain methods, you add an MX record on the technical or sending subdomain pointing to trap.yespo.io with priority 10. This is correct. Do not apply this Yespo MX record to your primary mailbox domain.

If the domain has no mail hosting, set up your mailbox provider first, add its MX record, and then return to verification.

How to check: Look up the MX records for the mailbox domain and confirm that they point to your mailbox provider.

SPF Record Is Invalid or Has Too Many Lookups

Issue: Yespo shows that SPF is invalid, or an SPF testing tool reports an SPF error.

Possible causes:

• The domain has more than one SPF TXT record.
• Yespo's include: value was added as a separate SPF record instead of being merged into the existing one.
• The SPF record exceeds the DNS lookup limit.
• The SPF TXT record contains a typo or unsupported mechanism.

Solution:

Keep a single SPF TXT record that starts with v=spf1.

If you already have an SPF record, edit the existing record and merge Yespo's include: value into it. Do not add a second SPF record.

SPF allows a maximum of 10 DNS lookups during a check. Each include: can count toward this limit. If your SPF record already includes multiple services, adding another include: may break SPF.

How to check: Use SPF Policy Tester to check whether your SPF record is valid and stays within SPF limitations.

Duplicate SPF or DMARC Records

Issue: Authentication fails because there are duplicate records.

Possible causes:

• The domain has more than one SPF TXT record starting with v=spf1.
• The domain has more than one DMARC TXT record at _dmarc.yourdomain.com.
• A new record was added instead of editing the existing one.

Solution:

• SPF: Keep one SPF TXT record only. Merge all authorized services into the same record.
• DMARC: Keep one TXT record at _dmarc.yourdomain.com.
• Other TXT records: A domain can have multiple TXT records, but SPF and DMARC records must not be duplicated.

If you see an existing SPF or DMARC record, edit it instead of adding a new one.

How to check: Look up TXT records for the domain and for _dmarc.yourdomain.com, then remove or merge duplicates.

DKIM Record Not Found

Issue: Yespo cannot find the DKIM record for your domain.

Possible causes:

• The DKIM record was not published.
• The record was added with the wrong type.
• The Name or Data value was copied incorrectly.
• The DNS provider appended your domain twice in the Name or Host field.
• DNS propagation has not finished yet.

Solution:

1. Confirm that the record was published with the exact Name Yespo provided.
2. Confirm that the record type is correct, usually CNAME or TXT.
3. Check whether your DNS provider expects only the prefix in the Name or Host field.
4. Wait for propagation.
5. Click Refresh in Yespo.

How to check: Use a DNS lookup tool to confirm that the full DKIM record name resolves publicly.

Incorrect Name or Host Value

Issue: DNS records are added, but Yespo cannot verify them.

Possible cause: The DNS provider automatically appended your domain to the Name, Host, or Record name field. If you pasted the full record name, the provider may have added your domain again and created an invalid record, for example selector._domainkey.yourdomain.com.yourdomain.com.

Solution: Check the full record name after saving. Use these examples as a guide, but always confirm the exact behavior in your DNS provider's documentation.

How to check: Look up the full record name. If it contains the domain twice, edit the record and enter only the prefix.

Verified Domain Is Required to Send

Issue: Yespo shows an error that a verified domain is required to send.

Possible cause: The domain or subdomain in the sender address is not verified.

Solution:

• Verify the exact domain or subdomain used in the sender address.
• Make sure the sender address configured in Yespo uses the verified domain or subdomain.
• Verifying yourdomain.com does not automatically verify promo.yourdomain.com. Domains and subdomains are verified separately.

For sender setup and related issues, see Adding a Sender.

How to check: Compare the domain in the sender address with the domain shown as Domain verified in Settings → Domain verification.

Forwarding for bounce+* Does Not Work

Issue: The Full method fails because Yespo cannot verify forwarding for bounce+* addresses.

Possible cause: Forwarding is missing, configured for the wrong mailbox, or unsupported by the mail provider.

Solution:

The Full method requires forwarding all mail sent to bounce+* addresses on your domain to [email protected].

If your mail provider supports plus addressing, create a bounce mailbox and forward all incoming mail to [email protected].

If your mail provider does not support plus addressing, create a catch-all mailbox for non-existent addresses. Then add a filter:

• If the address starts with bounce+, forward the message to [email protected].
• If the message is sent to any other non-existent mailbox, delete it.

If you use the Full + or Subdomain method, bounce forwarding is not required.

How to check: Send a test message to a bounce+... address on your domain and confirm that it is forwarded to [email protected].

Replies to Emails from the Subdomain Do Not Arrive

Issue: The domain is verified, but replies to emails sent from the subdomain do not arrive at the expected address.

Possible cause: The Reply address configured for the subdomain is invalid, the corresponding mailbox is not monitored, or it cannot receive forwarded messages.

Solution:

With the Subdomain method, all mail for the selected subdomain arrives at Yespo mail servers and is forwarded to the address specified in the Reply field.

Make sure the reply address is valid and the corresponding mailbox is monitored. Recipients can reply to your emails or send unsubscribe requests, and those requests need to be handled promptly.

How to check: Send a test reply to an email sent from the subdomain and confirm that it reaches the monitored reply mailbox.

The Domain Verified, Then Failed Again

Issue: After successful verification, the domain status shows an error again.

Possible cause: DNS changes have not fully propagated, so Yespo may see different values during different checks.

Solution:

• Wait until DNS changes have fully propagated across all nameservers.
• Avoid repeated re-checking during propagation.
• Confirm records with multiple DNS lookup tools if needed.

Yespo also re-checks domain settings on an ongoing basis. If the settings later become invalid, Yespo sends you an email and suspends DKIM signing with your domain key until the issue is resolved. Read automated emails from Yespo carefully and contact support if you need help.

How to check: Check the same DNS record from different lookup tools or locations. If results differ, wait for propagation to finish.

A TTL Warning Appears

Issue: Yespo shows a TTL warning, for example on a record with TTL=60.

Possible cause: The DNS record has a low TTL value.

Solution:

A TTL warning does not block verification. What matters is that the record type, name, and value are correct. A low TTL means that DNS caches retain the record for a shorter period.

You can keep the current value or use your DNS provider's default TTL.

How to check: Confirm that the record type, name, and value are correct. If they are correct, the TTL warning alone should not block verification.

When to Wait vs When to Fix

Wait if:

• You added or edited records recently.
• DNS lookup tools do not show the new values yet.
• Different lookup tools return different results.

Fix the records if:

• DNS lookup tools show a value that differs from Yespo.
• The record type is wrong.
• The full record name contains your domain twice.
• There are duplicate SPF or DMARC records.
• The sender address uses a domain that is not verified.

Still Stuck?

If your records are correct and propagated but verification keeps failing, contact Yespo support with:

• The domain or subdomain you are trying to verify.
• A screenshot of the warning shown in Settings → Domain verification.
• Screenshots or values of the DNS records in your DNS provider's control panel.
• The sender address you are trying to use.