Skip to main content
Sending email from a verified custom domain improves deliverability and trust.
thePurplebox verifies ownership of your domain via DNS records and configures the appropriate authentication so receiving mail servers treat your messages as legitimate.

​
Overview

To enable sending from a domain you control, add the DNS records shown in your domain details. Once the records propagate, thePurplebox will verify them and mark the domain as verified in the dashboard. After verification you can send mail using addresses on that domain (for example [email protected]) via the API or SMTP.

​
What you’ll add to DNS

thePurplebox will display the exact values for your domain in domains → domain details, but typically verification requires:
  • TXT records for SPF and DKIM (typically 2 TXT records)
    • SPF: authorizes thePurplebox IPs/hosts to send mail for your domain.
    • DKIM: a public key used to cryptographically sign messages.
  • CNAME records for bounce/return-path and tracking (typically 2–3 CNAMEs)
    • Return-Path / Bounce (CNAME) — routes bounces back to thePurplebox.
    • Tracking / Clicks (CNAME) — enables branded tracking links and open tracking.
The exact record names and values are unique per domain and are shown in the dashboard. Copy them exactly into your DNS provider.

​
Add the records

  1. Open your DNS provider’s control panel (Cloudflare, Route 53, GoDaddy, etc.).
  2. Create the required TXT and CNAME entries exactly as shown in thePurplebox dashboard.
  3. Save the changes and wait for DNS propagation (can be minutes to 48 hours).
  4. In thePurplebox dashboard, click Verify on the domain details page to start validating the records.
We recommend publishing a DMARC policy to protect your brand from spoofing. Start with p=quarantine for monitoring, then move to p=reject once you’re confident. Example DMARC TXT record:
TypeNameValue
TXT_dmarcv=DMARC1; p=quarantine; rua=mailto:[email protected]; ruf=mailto:[email protected]; pct=100;
When ready to enforce, set p=reject:
TypeNameValue
TXT_dmarcv=DMARC1; p=reject; rua=mailto:[email protected]; pct=100;

​
Verification notes & troubleshooting

  • DNS propagation can take up to 48 hours, but often completes much sooner.
  • Use the exact host/name and value strings provided in the dashboard. Small differences (extra dots, missing subdomain) will prevent verification.
  • If verification fails, check:
    • You added the record to the correct DNS zone (e.g., example.com vs sub.example.com).
    • There are no conflicting TXT or CNAME records.
    • Your DNS provider doesn’t rewrite records (some managed DNS services modify TXT formatting).
  • For bounce issues ensure the return-path/bounce CNAME is present and verified.
  • If you use a proxy/CDN (Cloudflare) make sure it does not proxy or alter CNAME/TXT resolution for the verification host.

​
After verification

  • The domain status in the dashboard will change to Verified.
  • You can immediately send from addresses at that domain using the API or SMTP credentials.
  • Monitor deliverability metrics (bounces, complaints) in the dashboard and adjust DNS/policies if necessary.