# Domain not Verifying
Verifying a domain involves a few steps:
1. Add your domain to Humanic
2. Copy the required DNS records from Humanic
3. Add these records to your DNS provider
4. Wait for verification to complete
When this process is completed correctly, your domain will often verify within 15 minutes of adding the DNS records. What should you do if your domain isn’t verifying?
Click here to understand the different [domain statuses](/humanic/getting-started-with-humanic/domain-setup/understanding-domain-status.md)
### [](https://resend.com/docs/knowledge-base/what-if-my-domain-is-not-verifying#common-verification-issues)Common verification issues
When your domain doesn’t verify as expected, it’s typically due to DNS configuration issues. This guide will help you troubleshoot and resolve common verification problems.
#### [](https://resend.com/docs/knowledge-base/what-if-my-domain-is-not-verifying#incorrect-dns-records)Incorrect DNS records
Usually when a domain doesn’t verify, it’s because the DNS records were not added correctly. Here’s how to check:
1. Confirm that you’ve added all required records (DKIM, SPF, and MX)
2. Verify that the records are added at the correct location (the `send` subdomain, not the root domain)
3. Check that record values match exactly what Resend generated for you
4. Use a DNS lookup tool like [dns.email](https://dns.email/) to verify your records are publicly visible
#### [](https://resend.com/docs/knowledge-base/what-if-my-domain-is-not-verifying#dns-provider-auto-appending-domain-names)DNS provider auto-appending domain names
Some DNS providers automatically append your domain name to record MX values, causing verification failures.
**Problem:**Your MX record appears as:`feedback-smtp.eu-west-1.amazonses.com.yourdomain.com`Instead of:`feedback-smtp.eu-west-1.amazonses.com`
**Solution:**In your DNS provider, add a trailing period (dot) at the end of the record value:`feedback-smtp.eu-west-1.amazonses.com.`The trailing period tells your DNS provider that this is a fully qualified domain name that should not be modified.Note: The region your domain is added to is in this MX record. It may be `us-east-1`, `eu-west-1`, `ap-northeast-1`, or `sa-east-1` depending on the region.
#### [](https://resend.com/docs/knowledge-base/what-if-my-domain-is-not-verifying#nameserver-conflicts)Nameserver conflicts
If your domain’s DNS is managed in multiple places (e.g., Vercel, Cloudflare, your domain registrar), you might be adding records in the wrong location.
**How to check:** Run a nameserver lookup for your domain using a tool like [dns.email](https://dns.email/) to see which provider actually controls your DNS. Add the Resend records at that provider, not elsewhere.
#### [](https://resend.com/docs/knowledge-base/what-if-my-domain-is-not-verifying#dkim-record-value-mismatches)DKIM record value mismatches
The DKIM record must match exactly what Resend generated. Common mistakes include:
1. Adding extra quotes or spaces
2. Truncating long values
3. Adding SPF information to the DKIM record
4. Not copying the entire value
Always copy and paste the exact value from Resend’s domain configuration page.
#### [](https://resend.com/docs/knowledge-base/what-if-my-domain-is-not-verifying#dns-propagation)DNS Propagation
After adding or correcting your DNS records:
1. DNS changes can take up to 72 hours to propagate globally (though often much faster)
2. Use the “Restart verification” button in the Resend dashboard to trigger a fresh verification check
3. If verification still fails after 24 hours, use [dns.email](https://dns.email/) to check if your records are visible publicly
### [](https://resend.com/docs/knowledge-base/what-if-my-domain-is-not-verifying#need-more-help)Need more help?
If you’ve followed all the steps above and your domain still isn’t verifying, contact with:
1. Your domain name
2. Screenshots of your DNS configuration
Our team will help identify any remaining issues preventing successful verification please reach out to or our WhatsApp support group [here](https://wa.me/14157403050).
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://humanic.gitbook.io/humanic/getting-started-with-humanic/domain-setup/domain-not-verifying.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.