Why domain verification is required
Email providers use domain authentication to confirm that mail is genuinely coming from the domain it claims. Without verified DNS records, your emails will be rejected or land in spam. MailerPath uses your verified domain to authenticate every send: transactional, campaign, and workflow.What you need to verify
Verification requires adding DNS records to your domain:| Record type | Purpose |
|---|---|
| SPF | Authorizes MailerPath’s sending servers to send on behalf of your domain. |
| DKIM | Adds a cryptographic signature so receiving servers can verify message integrity. |
How to add and verify your domain
- Go to your MailerPath account settings and locate the Sender domain section.
- Enter the domain you want to send from (for example,
yourdomain.com). - MailerPath generates the required DNS records (SPF and DKIM values).
- Log in to your DNS provider and add those records exactly as shown.
- Return to MailerPath and trigger domain verification.
- Verification runs a DNS lookup to confirm the records are live.
After verification
Once your domain is verified:- MailerPath creates a client-scoped sending credential scoped to your domain.
- Your
from_addressand sender settings become active. - Campaigns, workflows, and transactional sends can all dispatch.
Common issues
Verification fails immediately- Confirm the DNS records were saved correctly (no extra spaces, correct subdomain prefix).
- Check that your DNS provider has propagated the changes using a tool like
digor an online DNS lookup.
- Verify both SPF and DKIM records are present and passing.
- Confirm the
from_addressmatches the verified domain. - Avoid sending from a subdomain that is not explicitly included in your SPF record.
- The domain was not added or verification was not completed.
- Re-run verification from settings.

