Connect Your Sender Domain

Before you can send a single email, you need to authenticate the domain you want to send from (e.g., acme-store.com). This proves to recipient servers that emails claiming to be from your domain are actually authorized by you.

We give you 3 DNS records to publish; once they resolve, your domain is verified and email-sender signs every outbound mail with your domain’s DKIM signature so recipients see dkim=pass header.d=acme-store.com instead of our shared zone.

When to do this

Once. Per domain. Setup takes ~5 minutes; DNS propagation takes 5 to 60 minutes.

You can authenticate up to 5 domains. Common pattern is to verify your apex (acme-store.com) plus a marketing subdomain (mail.acme-store.com) — keeps marketing send reputation isolated from your transactional / corporate mail.

Step 1 — Add the domain

Open Settings → Email Domain
Click Add domain
Type your domain (e.g., acme-store.com) — without https://, without @
Click Add

The page now shows your domain in Pending status with the 3 DNS records you need to publish.

Step 2 — Publish 3 DNS records

Open your domain’s DNS provider in another tab — Cloudflare, Route 53, Namecheap, GoDaddy, DigitalOcean, whatever you use.

Copy each record from the Email Domain page and add it to your DNS:

SPF — TXT record


Type:     TXT
Hostname: _spf.acme-store.com
Value:    v=spf1 include:_spf.splashifypro.com ~all

Already have an SPF record? Most DNS providers allow only one TXT record at the same name. If _spf.acme-store.com already has an SPF (e.g., for Google Workspace), append our include: to the existing value:

v=spf1 include:_spf.google.com include:_spf.splashifypro.com ~all

DKIM — CNAME record


Type:     CNAME
Hostname: splashify._domainkey.acme-store.com
Value:    splashify._domainkey.mail.splashifypro.com

This is a CNAME chain — your record points to ours, recipient servers follow the chain to fetch our public key. Your private key never leaves our infrastructure.

Cloudflare proxy “flattening”? If Cloudflare flattens this CNAME to an IP, switch the proxy off (orange cloud → grey cloud) for this record. Email DNS records should never be proxied.

DMARC — TXT record


Type:     TXT
Hostname: _dmarc.acme-store.com
Value:    v=DMARC1; p=quarantine; rua=mailto:dmarc@splashifypro.com; pct=100; adkim=r; aspf=r

p=quarantine is our recommended starting policy — emails that fail SPF/DKIM checks land in spam rather than being rejected outright. Once you’re confident your sends authenticate cleanly (give it 30 days), upgrade to p=reject for stronger protection against spoofing.

Step 3 — Verify

Back on the Email Domain page, click Verify now on your pending domain.

We query your DNS provider directly via Cloudflare 1.1.1.1 / Google 8.8.8.8 (bypassing any system caches) and report each record’s status:

Status	Meaning
✓ Pass	Record found and matches expected pattern
✗ NXDOMAIN	Record not yet published. DNS propagation can take up to 1 hour
✗ Wrong value	Record exists but doesn’t include our `include:` / point at the right CNAME / start with `v=DMARC1`. Compare “Found” vs “Expected” in the UI
✗ DNS timeout	Your DNS provider is slow. Click Verify again in a moment

When all 3 are green, status flips to Verified and the green badge appears.

Auto-recheck: even if you don’t click Verify, we re-check every 15 minutes for pending domains. So if you publish DNS at 10:00 and forget about it, the domain auto-flips to Verified by 10:15.

What happens after verification

Email-sender signs every outbound message from <anything>@acme-store.com with your domain’s DKIM:


DKIM-Signature: v=1; a=rsa-sha256; d=acme-store.com; s=splashify; ...

Recipients (Gmail “Show original”, etc.) see:


SPF:    PASS  with IP 203.174.23.244
DKIM:   PASS  with domain acme-store.com
DMARC:  PASS

Your brand. Your domain. Our infrastructure.

What you can’t do until verified

You can build templates and create campaigns in draft. But:

You can’t actually send from a non-verified from_email — campaign Send button errors with “domain not verified”
Public API /email/send returns 400 with from_email domain '<x>' is not verified. until verification is complete

This is intentional. Sending from an unverified domain hits recipient spam folders 60–90% of the time and damages our shared sending IP’s reputation.

Removing a domain

Click Remove on the domain card. Confirm. The domain is removed from your account and future sends from that from_email will be blocked.

Old DNS records: removing a domain in our UI doesn’t unpublish the DNS records on your side — those are yours to manage. If you want to fully clean up, delete the SPF / DKIM / DMARC records from your DNS provider too.

Reseller-specific note

If you’re an end customer of a reseller (your platform domain is app.<reseller-domain> rather than app.splashifypro.com):

The verification flow is identical
Your DKIM CNAME still points to splashify._domainkey.mail.splashifypro.com — that’s our shared signing infrastructure regardless of which reseller you’re under
Your reseller’s branding doesn’t change the technical setup

Troubleshooting

Symptom	Fix
All 3 records published but still pending after an hour	Click “Verify now” once. If still stuck: confirm records resolve via `dig +short TXT _spf.your-domain.com` and `dig +short CNAME splashify._domainkey.your-domain.com` from any computer. If those return empty, your DNS provider hasn’t propagated yet — wait.
SPF shows “wrong_value”	The recommended SPF didn’t get into the TXT record at `_spf.your-domain.com`. Check the actual published value (the UI shows “Found”). Make sure `include:_spf.splashifypro.com` is part of the SPF string.
DKIM shows “wrong_value”	The CNAME isn’t pointing at the right target. Make sure it’s `splashify._domainkey.mail.splashifypro.com.` (note the trailing dot in some DNS providers).
DMARC shows “wrong_value”	The TXT exists but doesn’t start with `v=DMARC1`. Re-paste the recommended value.
Verified yesterday, today shows pending	We re-check every 24h on verified domains. If a record was rotated by your DNS provider or accidentally deleted, you’ll get an in-app notification + status flip. Re-publish and click Verify.