If DKIM is verified but your sending records are still pending, check the remaining records separately. Resend's older TXT/MX setup needs both sending records to be correct before SPF verifies. Newer domains may use CNAME records instead. Start with the Records tab for your domain, not a record list copied from another setup. Resend's verification guide documents both configurations.
Find the DNS provider that actually controls the domain
Look up your domain's nameservers using dns.email, the DNS lookup tool linked by Resend. Compare the result with the provider where you entered your records. If the nameservers point elsewhere, edit the records at that provider. Adding them at your registrar does not help when another provider manages the DNS. Verification guide
Use a domain you own or administer. Keep the Resend Records tab open alongside the DNS editor so you can compare each name, type and value.
Match the records shown for this domain
Check the full hostname where each record should exist. The default sending location is a send subdomain, but your configured Return-Path can differ. Copy the generated values and, for MX records, the displayed priority. Keep DKIM content separate from SPF content. Verification guide, Return-Path documentation
| What the Records tab shows | What to inspect |
|---|---|
| Sending TXT and MX records | Check both at the exact sending hostname. DKIM passing does not establish that this pair is correct. |
| Sending CNAME records | Check every CNAME shown, using its own name and target. Do not add the old TXT/MX pair in place of them. |
| DKIM record | Match its generated name and complete value. Do not add SPF text to it. |
Resend says domains created after August 2026 may show CNAME records. When two are shown, each verifies independently: one can pass while the other fails, leaving the domain partially_verified. Resend documents sending in that state without a fallback sending server. Inspect the individual record errors rather than treating that status as the older TXT/MX failure. Verification guide
For a terminal lookup, use the record type and full name from your dashboard:
nslookup -type=TXT FULL_RECORD_NAME
nslookup -type=MX FULL_RECORD_NAME
nslookup -type=CNAME FULL_RECORD_NAMEReplace FULL_RECORD_NAME before running a command. Run only the types your dashboard requests, and compare the returned values with Resend. These are the lookup methods in Resend's guide.
Check for the domain being appended twice
Keep the Name field separate from the Value, Content or Target field.
In a zone for example.com, a provider may expect the relative name send, not send.example.com. For a Resend domain of updates.example.com managed in that same zone, its default sending name would be send.updates. Resend's Hetzner instructions show this relative-name format. Check how your own provider handles names before saving.
MX and CNAME targets can have a similar problem. If the target comes back with your domain appended to the vendor hostname, Resend recommends a trailing dot on that target to keep it fully qualified. Its Hetzner guide explicitly requires the trailing dot for the MX value. Copy your domain's generated target; do not copy a region from an example. Verification guide, Hetzner guide
Do not add a dot to the TXT payload as a general fix. The trailing-dot advice concerns domain names in MX/CNAME targets. The SPF and DKIM TXT content should match what Resend generated.
A synthetic example of the naming mistake
We tested a local model that appends example.test. to names without a trailing dot. It produced these results:
| Input in that model | Result |
|---|---|
send | send.example.test. |
send.example.test | send.example.test.example.test. |
send.example.test. | send.example.test. |
MX target mx.vendor.test | mx.vendor.test.example.test. |
MX target mx.vendor.test. | mx.vendor.test. |
In the incorrect fixture, the DKIM entry was found at its expected name while the sending TXT/MX entries were absent from theirs. Correcting the sending names and MX target made the entries discoverable at the intended names; the TXT payload stayed unchanged.
This illustrates one naming error. It is a synthetic name-expansion test, not a live DNS-provider test or a successful Resend verification. Providers differ in how their input fields handle full names.
Check record type and proxy settings
If Resend asks for CNAME records, confirm that the DNS editor saved CNAME records at those names. On Cloudflare, the dedicated sending CNAME records must be DNS only, shown by a gray cloud. Resend says proxied records do not resolve as CNAMEs for verification. Verification guide
Apply that setting only to the sending names Resend generated. Leave unrelated website proxy settings alone. If a proposed sending name already serves a website or another service, resolve that name conflict before changing it.
Resolve conflicts without breaking existing mail
A sending Return-Path and an inbox's receiving domain have different jobs. Resend's sending MX at send.example.com does not replace the mailbox MX at example.com. Keep your production mailbox records. Do not enable Resend Receiving or change root MX priorities just to fix sending verification. Resend's MX conflict guide
Check conflicts at the exact sending hostname:
CNAME setup: a CNAME cannot coexist with other record types at the same name. If an existing service needs those records, preserve them and plan a different Return-Path with your DNS administrator.
Legacy TXT/MX setup: check whether that sending name already belongs to another mail service. Do not remove its records without identifying their purpose. Resend's conflict guide describes using a separate subdomain when existing records must remain.
Existing SPF: leave unrelated SPF records intact. Do not create a second SPF policy at the same name. The SPF standard treats multiple selected SPF records as an error; have the mail administrator resolve the collision rather than overwrite a working policy.
Sources: verification guide, MX conflict guide, RFC 7208, sections 3.2 and 4.5.
A different Return-Path is not an in-place edit. Resend says it is set when the domain is created; changing it requires deleting and adding the domain again. For a domain already in use, stop and plan that change with the person responsible for app email or Resend support. Do not recreate a production domain casually. Return-Path documentation
Check the region only if your setup uses MX
For region-mismatch, compare the sending MX target with the value shown for your domain in Resend. For multiple-regions, inspect the MX records at that sending name and correct only the Resend entries that point to the wrong region.
Keep unrelated receiving MX records untouched. These region checks apply to the legacy sending MX setup. With CNAME sending records, Resend says the target handles the region, so there is no MX region to match. Verification guide
Recheck after correcting the records
Use Restart verification in Resend after correcting the records. Resend allows up to 72 hours for DNS changes to propagate and recommends checking public visibility with dns.email if verification still fails after 24 hours. Those are troubleshooting windows, not a promise that waiting will fix a wrong record. Verification guide
If the names and values match but verification still fails, contact Resend support with your domain name and screenshots of the DNS configuration, as its guide recommends.
If the website also has an HTTPS error
Treat that as a separate check. Enviera's custom-domain SSL checker checks web-domain DNS and certificates; it does not verify Resend email authentication. For a Lovable web domain that is stuck during setup, use the Lovable domain and SSL guide.
Still stuck on app email?
For unresolved app email failures, see the Production Readiness Audit.
Sources
All sources read on 1 November 2026. Resend pages did not display publication dates in the text consulted.
Resend, What if my domain is not verifying?.
Resend, Hetzner DNS setup.
Resend, Configure a custom Return Path.
IETF / RFC Editor, RFC 7208: Sender Policy Framework, April 2014.
Enviera, Custom-domain SSL checker, Lovable domain and SSL guide, and Production Readiness Audit.