Use the records returned by your own Emailer API account. Verify ownership and SPF, then publish the DKIM and DMARC records returned after signing provisioning. Keep existing email services in mind before changing DNS.
What each check is for
| Record | What to check in this setup |
|---|---|
| Ownership TXT | The exact name and value issued to your domain. It proves control of that domain for this account. |
| SPF TXT | The required sending authorization is present in the domain’s single SPF policy. Do not add a second independent SPF policy. |
| DKIM TXT | The selector and public signing key returned after provisioning. Never invent or reuse another account’s value. |
| DMARC TXT | The required policy at the returned name, reconciled with existing settings and other senders. |
This table describes Emailer API’s verification workflow. The application’s account-specific instructions are the source of truth for record values; no universal DNS value belongs in a copy-and-paste tutorial.
Why DKIM may not appear in the first step
Emailer API stages domain setup. Add the domain, publish ownership and SPF records, then run verification. Signing provisioning can then produce the DKIM value. Publish that value and the returned DMARC record, and check again. A domain added to an account is not yet a fully verified sending identity.
Using the built-in assistant
Select your domain and ask the assistant to check its DNS. It reads current setup state and can explain which records are still missing. If your domain is managed in Cloudflare, use the secure provider connection field to authorize access for that customer’s domain. Do not paste credentials into chat.
The helper can prepare supported TXT additions. You review the exact plan and apply it through the customer interface. Plans expire after 10 minutes, and records are rechecked before any write. If the existing policy conflicts with the requested record, resolve it manually. The helper does not silently delete records or apply plans itself.
Verification still pending?
- Check the selected domain. A root domain and a sending subdomain are different DNS names. Confirm the name shown in the account.
- Check the authoritative provider. Publish records where the domain’s active nameservers are managed, not in an unused dashboard.
- Check the record name. DNS dashboards may append the zone name. Avoid creating a doubled domain name.
- Check exact values. Copy the current account-generated value, including the complete public DKIM key. Do not copy example records from this page.
- Check existing policies. Duplicate SPF or DMARC policies need reconciliation. Preserve legitimate existing senders.
- Recheck after publication. DNS caches can delay visibility. Follow the service’s actual result rather than treating elapsed time as proof.
Domain verification is one part of launch.
Account access, owner verification, signing readiness, the approved template, a fresh event and available capacity still apply. DNS verification alone cannot establish inbox placement or authorize arbitrary mail. Continue with the transactional email setup checklist.
Implementation references
See the Emailer API domain workflow, assistant capabilities and current sending limits. These instructions describe the implemented product as reviewed on the date above.