Questions · Updated 2026-09-23

How do I verify a sending domain on Google Domains?

To verify a sending domain on Google Domains, add the rows from GET /domains/{id}/setup as custom records in Squarespace, which has hosted those registrations since the 2023 migration, then call POST /domains/{id}/verify. The clicks below are Squarespace's, as of September 2026.

To verify a sending domain on Google Domains, add the rows from GET /domains/{id}/setup as custom records in Squarespace, then call POST /domains/{id}/verify. Squarespace's migration article says Squarespace acquired the Google Domains registrations on September 7, 2023, and that you manage the domain in Squarespace. The clicks below are Squarespace's, as of September 2026.

The records to publish

POST /domains registers the name. GET /domains/{id}/setup returns one row per record, with record, host, type, value, priority, and required. A TXT row also has value_strings and value_bind. Paste those. The DKIM value is the one on the row. The same response includes commands.gcloud for Cloud DNS.

When the nameservers still match Google, provider.name on that response is "Google Domains / Cloud DNS" and provider.dnsConsoleUrl is https://console.cloud.google.com/net-services/dns/zones. A registration that moved to Squarespace is edited in Squarespace, not at that URL. If the domain uses some other nameserver host, edit DNS there. Squarespace's edit article says the same: records you add in Squarespace apply when the domain is registered through Squarespace or connected with Nameserver Connect.

A new domain sends once the required rows resolve. Domains and DNS names them: the DKIM TXT, and the return-path MX and TXT. Root SPF and DMARC are recommended. A tracking CNAME is on the sheet only when tracking is available, and it never blocks verification. If the apex already has an SPF TXT, merge the sheet's value into that one record. A second SPF TXT on the same name invalidates both.

curl -sS -X GET https://api.agentisend.com/domains/9c8f8f0e-3d1a-4d3f-9a1e-2b7c1a0f5e42/setup \
  -H "Authorization: Bearer $AGENTISEND_API_KEY"
200
{
  "commands": "string",
  "deep_link": "string",
  "detected": true,
  "domain": "string",
  "nameservers": [],
  "provider": "string",
  "provider_hints": "string",
  "records": []
}
Response

Squarespace, for a migrated Google Domains registration, as of September 2026

About the Google Domains migration to Squarespace (updated May 28, 2026) says to sign in at squarespace.com/login and choose Continue with Google.

Adding TXT records (updated April 27, 2026) says: open the domains dashboard, click the domain, click DNS, then DNS Settings, scroll to Custom records, click Add record, reauthenticate, choose TXT, and Save. Name is @ when the row's host is @. Otherwise Name is the host only (as1._domainkey, send, _dmarc), because the article says Squarespace appends the domain. Text is the row's value. Troubleshooting says a TXT longer than 255 characters has to be split into strings under that length. Use value_strings for that split, on the one TXT the sheet describes, then let POST /domains/{id}/verify say whether the published record matches.

DNS records for email says an MX is the same Add record path with Type MX. Name is @ or the subdomain. Priority is a number from 0 through 255. Mail server is the host you are directing to. Put the row's priority in Priority and the row's value in Mail server. The edit article says a change can take 24 to 48 hours: Edit your domain's DNS records (updated September 22, 2026).

Read it back

POST /domains/{id}/verify reports which required rows resolved. GET /domains/{id} is the sheet with each row's status.

Other registrars