Sending Domains

Sending "from" your domain without proving you control it is what spam filters exist to catch. Verification is a one-time DNS exercise: you publish records that cryptographically sign your mail, inbox providers check the signature, and your mail arrives with your domain's reputation behind it.

Adding a domain

Email → Setup → Domains, add your domain. You'll get three DKIM CNAME records to publish in DNS. Then:

One-click for Cloudflare: if your DNS is on Cloudflare, Add to Cloudflare opens an authorization and publishes all three records for you. This is the fastest path by far.
Everyone else: shortcut links open the DNS console for GoDaddy, Namecheap, Route 53, Vercel, DigitalOcean, and Google Domains; copy the three records in.

Press Refresh to re-check. Statuses: not started → pending → verified (or failed / temporary failure — usually a typo'd record or slow propagation; DNS can take minutes to hours). Once verified, sending unlocks for every feature and the API.

Note for Cloudflare users: the DKIM CNAMEs must be DNS-only (grey cloud). Proxied records (orange cloud) break verification, and the UI will warn you if it detects this.

Keeping your current email provider

You almost certainly already send personal mail from this domain — Google Workspace, Fastmail, whatever. That keeps working. DKIM records are additive: each sender signs with its own keys, and GoShipFast's three CNAMEs don't touch your provider's records, your MX, or your mail flow.

Two records are singular per domain, though, and worth care:

SPF — a domain gets exactly one SPF TXT record. If you maintain one, don't create a second; merge includes into the existing record.
DMARC — likewise one policy record. If you run a strict policy, confirm it aligns with how you want GoShipFast's mail treated.

The How it works drawer covers these cases in detail. When in doubt: add only what the setup screen asks for, replace nothing.

Choosing what to verify

You can verify your apex (yourbrand.com) or a subdomain (mail.yourbrand.com, news.yourbrand.com). Subdomains partition reputation — a common pattern is keeping marketing volume on a subdomain so the apex's transactional reputation stays pristine. For a first domain at founder scale, the apex is fine; the plan's domain count (1 on Creator, more on higher tiers) leaves room to specialize later.

After verification

Send a test from Tracking or via the API and watch it appear in History.
Ramp volume gradually — the daily quota enforces the pace deliverability actually requires.
Optionally flip the domain to receive mail too: Receiving & Forwarding.