How to add AISend's DNS records in Squarespace Domains
Squarespace Domains is where Google Domains customers now manage DNS, and its custom-record form uses different field names for CNAME and TXT records: Data for a CNAME, Text for a TXT. This guide fills it for mail.acme.com from Squarespace's own help articles, including the points that cause failed saves: the automatic domain suffix, trailing periods, and quotation marks in SPF.
Provider statements checked on November 19, 2026 against the provider's own pages, linked as Sources.
What you will add
AISend is our product: a Resend-compatible email API that sends through Amazon SES. This page is written by the team that builds it, so the records below are the ones AISend really issues. Add a domain on the AISend Domains page first; it shows your three tokens.
Examples use mail.acme.com, a subdomain of acme.com. We recommend verifying a subdomain like this over the root domain; the setup overview and our count of 23 real domains explain why.
| Record | Type | Full host | Value | Needed? |
|---|---|---|---|---|
| DKIM 1 | CNAME | <token1>._domainkey.mail.acme.com | <token1>.dkim.amazonses.com | Yes, gates verification |
| DKIM 2 | CNAME | <token2>._domainkey.mail.acme.com | <token2>.dkim.amazonses.com | Yes, gates verification |
| DKIM 3 | CNAME | <token3>._domainkey.mail.acme.com | <token3>.dkim.amazonses.com | Yes, gates verification |
| SPF (optional) | TXT | mail.acme.com | v=spf1 include:amazonses.com ~all | No |
| DMARC (optional) | TXT | _dmarc.mail.acme.com | v=DMARC1; p=none; rua=mailto:dmarc@mail.acme.com | No |
Only the three DKIM CNAMEs gate verification. Replace each <tokenN> with the token the Domains page shows; never use a token from this page.
Squarespace Domains, formerly Google Domains
Squarespace says it has migrated all Google Domains domains and that Google Domains no longer exists. Domains that were Google Domains are now in a Squarespace Domains account, and you can use it solely for domain hosting. Source: Squarespace Domains: Google Domains FAQ, checked November 19, 2026.
Where you edit depends on the domain. A Squarespace domain, or a third-party domain connected with Nameserver Connect, is edited in the Squarespace domains dashboard. A third-party domain connected with DNS Connect is edited at that domain provider. A Squarespace domain bought through Google Workspace is edited in the Google Admin console. Source: Squarespace Help: Add DNS records for email, checked November 19, 2026.
If the domain uses custom nameservers instead of the Squarespace defaults, records added in Squarespace's DNS panel do not apply to your domain. Source: Squarespace Help: Troubleshooting issues with DNS records, checked November 19, 2026.
Add the records in Squarespace Domains
- Open your Squarespace domains dashboard and click the domain.
- Click DNS, then DNS Settings.
- Scroll to Custom Records and click Add record.
- If asked, enter your password or re-authenticate with two-factor authentication, then click Continue.
- Choose CNAME in the Type menu, fill Name and Data (next table) and click Save. Repeat for the other two DKIM records.
| Field | What to enter for the DKIM record | Why |
|---|---|---|
| Type | CNAME | TXT for SPF and DMARC. |
| Name | <token1>._domainkey.mail | Squarespace adds your domain after any Name for you, so a name like mail.yourdomain.com is entered as mail. |
| Data (CNAME) | <token1>.dkim.amazonses.com | For a CNAME, Squarespace says to enter the value in Data, not Text. Remove any period at the end. |
| Text (TXT) | v=spf1 include:amazonses.com ~all | No quotation marks; they can stop an SPF record from working, depending on your nameservers. |
| Name (DMARC) | _dmarc.mail | Squarespace's own DMARC steps say to enter _dmarc and leave your domain off the end. |
| TTL | Default (4 hours) | Squarespace's default for custom records. Keep one TTL across records on a subdomain, which Squarespace recommends. |
Type the host the way Squarespace Domains wants it
Squarespace Domains calls the host box Name, the CNAME target Data and the TXT text Text. Worked example for mail.acme.com, in Squarespace Domains's own words:
| Record | Type | Name to type | Value to type |
|---|---|---|---|
| DKIM 1 | CNAME | <token1>._domainkey.mail | <token1>.dkim.amazonses.com |
| DKIM 2 | CNAME | <token2>._domainkey.mail | <token2>.dkim.amazonses.com |
| DKIM 3 | CNAME | <token3>._domainkey.mail | <token3>.dkim.amazonses.com |
| SPF (optional) | TXT | v=spf1 include:amazonses.com ~all | |
| DMARC (optional) | TXT | _dmarc.mail | v=DMARC1; p=none; rua=mailto:dmarc@mail.acme.com |
On a record that sits on the registered domain itself (acme.com, not mail.acme.com), Squarespace Domains wants: @. The calculator below does the same for your own domain.
Type the domain you added in AISend, for example mail.acme.com. Nothing leaves your browser.
What Squarespace Domains's own documentation says
- Squarespace adds your domain to the Name field itself: to add the host mail.yourdomain.com enter mail, and to use the bare domain enter @. Source: Squarespace Help: Adding TXT records, checked November 19, 2026.
- It is not possible to add a CNAME with @ in the Name field. Source: Squarespace Help: Troubleshooting issues with DNS records, checked November 19, 2026.
- "This name record is already in use" means the Name is taken by another record, for example www on both a CNAME and a TXT. Source: Squarespace Help: Troubleshooting issues with DNS records, checked November 19, 2026.
- Remove periods at the end of the Data value; the system cannot save records formatted that way. Source: Squarespace Help: Troubleshooting issues with DNS records, checked November 19, 2026.
- TXT and DMARC records have a 255-character limit; longer ones must be split into several strings. Source: Squarespace Help: Troubleshooting issues with DNS records, checked November 19, 2026.
- SPF and DKIM records can be added up to 2,048 bits without splitting, other TXT records have the 255-character limit. Source: Squarespace Help: Add DNS records for email, checked November 19, 2026.
- Add each SPF record as its own custom record and they merge into one. Squarespace says to refresh to see the merged record. Source: Squarespace Help: Add DNS records for email, checked November 19, 2026.
- All custom records have a 4-hour TTL by default, and it can take 24 to 48 hours for a change to update. Source: Squarespace Help: Edit your domain's DNS records, checked November 19, 2026.
SPF and the quote trap
If an SPF record does not resolve, Squarespace says to remove quotation marks from the Data or Text field, since they can cause propagation issues depending on your nameservers. The same article says that if you see the error "Custom records not saved" while adding an SPF record, you delete your current SPF records in DNS settings and add the new ones. Source: Squarespace Help: Add DNS records for email, checked November 19, 2026.
That pairs with AISend's rule of one SPF record per name: with Squarespace you can add v=spf1 include:amazonses.com ~all as its own custom record on mail and let Squarespace merge it with any other SPF record on the same name.
Verify in AISend
- Open the AISend Domains page, find your domain and click Verify DNS Records.
- Each record gets its own live status: "Found", "Not found yet", "Wrong value", "Proxied", "Wrong host", "Duplicate" and so on, with a plain hint on what to change.
- When the three DKIM rows are found the domain is verified. SPF and DMARC stay optional.
Squarespace says that after you save a record it can take up to 48 hours to work, and to troubleshoot if it is not working after that. Source: Squarespace Help: Add DNS records for email, checked November 19, 2026.
Check from your terminal
These commands show what the public DNS answers, which is what verification reads.
# paste your first token from the AISend Domains page
TOKEN1=your-first-token
# should print <token>.dkim.amazonses.com.
dig +short CNAME "$TOKEN1._domainkey.mail.acme.com"
# optional records
dig +short TXT mail.acme.com
dig +short TXT _dmarc.mail.acme.com
# where does the domain's DNS really live?
dig NS acme.com +shortPrefer a page? The free SPF & DMARC checker looks up the same records for any domain, no sign-up.
Common failures at Squarespace Domains
| What you see | Likely cause | Fix |
|---|---|---|
| "Custom record not saved" or "This name record is already in use" | The Name is already used by another record, or the record conflicts with an existing one. | Find the record on that name in Custom Records and delete or change it, then save again. Our DKIM names are unique per token. |
| Invalid IP address or Name error on a CNAME | The Data value ends in a period, or has a typo. | Paste <token1>.dkim.amazonses.com with no trailing period. |
SPF TXT is saved but dig TXT mail.acme.com shows nothing | Quotation marks in Text can stop SPF resolving. | Remove the quotes and save again. |
Name typed as <token1>._domainkey.mail.acme.com | Squarespace adds your domain itself, producing ...acme.com.acme.com. | Type <token1>._domainkey.mail. |
dig NS acme.com returns NXDOMAIN | The domain name is misspelled, was never registered, or has expired. In our count of pending domains on 2026-11-17, 11 of 19 did not exist in DNS. | Fix the name in AISend or register the domain; no DNS record can verify a name that does not exist. |
| The nameservers are not the ones you edited | Records were added at a DNS host the domain does not use. Run dig NS acme.com +short and compare with the nameservers shown for the domain in Squarespace. If they are custom nameservers, records in the Squarespace panel do not apply. | Add the records at the provider the nameservers point to, or switch the nameservers to the one you edited. |
| Verified, but old mail now fails SPF | A second SPF record on the same name; a name may carry only one. | Merge into one v=spf1 record with a single all, or skip SPF; AISend does not require it. |
The shared causes (zone typed twice, proxies, a second SPF record, a name that does not exist, records added at the wrong DNS host) come from our count of pending domains; the Squarespace Domains-specific rows come from its documentation, linked above.
Frequently asked questions
Is Squarespace Domains the same as Google Domains?
It is where Google Domains customers moved. Squarespace says all Google domains have been migrated and Google Domains no longer exists. DNS records are now edited in the Squarespace domains dashboard.
Where does the CNAME value go in Squarespace?
In the Data field. For TXT records, Squarespace uses the Text field. For the DKIM CNAMEs, paste <token1>.dkim.amazonses.com into Data with no trailing period.
How long do Squarespace DNS changes take?
Squarespace says up to 48 hours after you save. AISend's Verify button checks live DNS, so try it after a few minutes and again later.
Which of the records does AISend need before the domain verifies?
Only the three DKIM CNAME records. The SPF and DMARC TXT records are optional and do not block verification. A subdomain such as mail.acme.com is the safer first choice because it rarely already has an SPF record.
Why do the guide's tokens look like placeholders?
The three tokens are generated per domain and shown only in your AISend dashboard. We never invent them; copy each token from the Domains page into the host and into the value.
Sources
Other DNS providers
Ready to send from your own domain?
Creating an account is free, and a free account can send 10 test emails to its own verified address from onboarding@send.aisend.app. Sending to other people needs Pro, $14/month for 50,000 emails, and a verified domain.