Email

Sending Domains

This guide takes a domain from unverified to sending. You'll publish three DNS records that cryptographically sign your mail; once inbox providers can check the signature, your mail arrives with your domain's reputation behind it. Nothing sends until this is done.

Before you begin

  • Access to your domain's DNS (Cloudflare, GoDaddy, Namecheap, Route 53, Vercel, DigitalOcean, or Google Domains — all have shortcuts here)
  • A decision on what to verify: your apex (yourbrand.com) or a subdomain (mail.yourbrand.com). For a first domain at founder scale, the apex is fine; subdomains partition reputation and are worth it later.

Verify your domain

1

Add the domain

Open Email → Setup → Domains and add your domain. You'll get three DKIM CNAME records to publish.

2

Publish the DNS records

  • On Cloudflare: click Add to Cloudflare. An authorization opens and all three records are published for you. This is the fastest path by far.
  • Anywhere else: use the shortcut link to open your provider's DNS console and copy the three records in.

Warning

Cloudflare users: the DKIM CNAMEs must be DNS-only (grey cloud). Proxied records (orange cloud) break verification — the UI warns you if it detects this.

3

Refresh and confirm

Press Refresh to re-check. Statuses run not started → pending → verified. A failed or temporary-failure state is usually a typo'd record or slow propagation; DNS can take minutes to hours.

Once verified, sending unlocks everywhere — every feature and the API.

4

Send a test

Send a test from Tracking or via the API and watch it appear in History. Then ramp volume gradually — the daily quota enforces the pace deliverability actually requires.

Keep 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.

Tip

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

Next steps