MailKite DNS on Squarespace Domains
Squarespace Domains supports all four DNS records MailKite requires — one MX and three TXT records (SPF, DKIM, DMARC) — added under Domains dashboard → your domain → DNS → Custom Records. This guide also covers domains migrated from Google Domains, which now live in the same Squarespace DNS panel.
Before you start
- Add your domain in MailKite to get the exact record values — the DKIM key is unique per domain.
- Squarespace must be your DNS host (the default for domains bought there or migrated from Google Domains). If you've pointed nameservers elsewhere, add the records at that provider instead.
The records, Squarespace-style
The Host field takes only the host part — @ for
the root domain. Values below are for myapp.ai:
| Host | Type | Priority | Data |
|---|---|---|---|
@ | MX | 10 | mx.mailkite.dev |
@ | TXT | — | v=spf1 include:mailkite.dev ~all |
mailkite._domainkey | TXT | — | v=DKIM1; k=rsa; p=… (from your dashboard) |
_dmarc | TXT | — | v=DMARC1; p=none; |
For a subdomain likemail.myapp.ai, the Hosts becomemailkite._domainkey.mail, and_dmarc.mail.
Step by step
- Sign in and open account.squarespace.com/domains (or, from a site: Settings → Domains).
- Select your domain, then open DNS (Edit DNS / DNS Settings).
- Under Custom Records, click Add Record.
- Add each of the four records above — for the MX record a Priority field appears next to Data; set it to
10. - Save. Squarespace applies the records immediately.
Verify
npx @mailkite/cli domains verify <domainId> --json
Squarespace changes usually propagate within an hour. The
domain flips to verified once MX resolves; re-run until SPF,
DKIM, and DMARC are green too.
Squarespace gotchas
- Google Domains migrations land here. If your domain was on Google Domains, it's now managed at Squarespace — same records, new panel. Old Google Domains instructions map 1:1 to Custom Records.
- Email presets can conflict. If you've used a Google
Workspace or Squarespace Email preset, the root
@may already carry MX and SPF records. A domain resolves mail to one inbound provider — put MailKite on a subdomain, or remove the preset MX records. - One SPF record per name. Merge
include:mailkite.devinto an existingv=spf1TXT rather than adding a second one. - No DNS API. Squarespace has no public DNS API, so records are added in the dashboard — it's four rows.
FAQ
Does Squarespace allow the DNS records MailKite requires?
Yes. MX and TXT custom records are supported on every Squarespace-managed domain, including former Google Domains. Nothing MailKite needs is restricted.
My domain came from Google Domains — where do I add records?
At account.squarespace.com/domains → your domain → DNS. Google migrated all Google Domains registrations to Squarespace; the Custom Records panel replaces Google's resource records page.
Will this break my Squarespace website?
No. Website traffic uses A/CNAME records; MailKite only adds MX and TXT records, which don't affect how your site loads.
Next: receive your first message, or see the full Domains & DNS reference.