Skip to content
BlogDeliverability

How to Set up Google Workspace With a Squarespace Domain mx Spf Dkim Dmarc

Learn how to Set up Google Workspace With a Squarespace Domain mx Spf Dkim Dmarc with this clear guide to configure your DNS and protect deliverability.

Infrabox TeamEditorial
10 min read
On this page
  1. How do you point Squarespace MX records to Google Workspace?
  2. How to configure SPF records for Google Workspace on Squarespace?
  3. Why is DKIM authentication required for Google Workspace senders?
  4. How do you enforce DMARC policies for maximum inbox placement?
  5. Which setup method works best for outbound cold outreach teams?
  6. How can you protect deliverability after setting up your domain?
  7. Master Your Domain Setup for Maximum Reach
  8. Related articles
  9. Frequently asked questions

How to Set up Google Workspace With a Squarespace Domain mx Spf Dkim Dmarc is the step-by-step technical process of configuring MX records to route incoming emails to Google servers, alongside SPF, DKIM, and DMARC protocols to authenticate and secure your sending domain within Squarespace DNS settings. When you complete these updates, you establish legitimate domain ownership and satisfy strict authentication policies enforced by global email providers.

If you are managing outbound operations at scale, platforms like Infrabox provide specialized domain management and deliverability monitoring tools to ensure your email infrastructure remains properly aligned over time.

Failing to configure your DNS settings accurately causes receiving gateways at Google, Yahoo, and Microsoft to flag your outbound messages as suspicious. Without verified authentication signatures, major inbox providers will divert your communications directly to the spam folder or drop them through hard bounces. Completing this technical guide guarantees your domain meets modern sender guidelines, establishes cryptographic trust, and maximizes your campaign deliverability.

Understanding the four mandatory DNS components:

  • MX (Mail Exchanger): Directs incoming email messages to the specific mail servers hosting your inbox.
  • SPF (Sender Policy Framework): A TXT record listing all IP addresses and third-party services authorized to send emails from your domain.
  • DKIM (DomainKeys Identified Mail): Adds an encrypted digital signature to outbound headers, confirming the email contents were not altered in transit.
  • DMARC (Domain-based Message Authentication, Reporting, and Conformance): Sets explicit instructions for receiving servers on how to handle emails that fail SPF or DKIM checks.

How do you point Squarespace MX records to Google Workspace?

To point Squarespace MX records to Google Workspace, you must access your domain's Advanced DNS Settings panel in Squarespace, remove legacy mail records, and enter Google's official mail server addresses with their corresponding priority values. This mapping routes all inbound email traffic directly to your Google Workspace environment for reliable message delivery.

Host: @
Type: MX
Value: ASPMX.L.GOOGLE.COM.
Priority: 1

Step 1: Access your Squarespace DNS panel

Log into your Squarespace account and navigate to the Domains dashboard. Click on the domain name you wish to configure, select Settings, and then open the Advanced Settings (or DNS Settings) panel to manage your zone files.

Step 2: Add Google Workspace MX records

In the DNS Settings menu, scroll down to Custom Records. Click Add Record and select MX from the record type drop-down menu. Add Google's five standard mail server addresses, setting the host field to @ (or leave it blank depending on the prompt):

Host Name Record Type Priority Points To / Value
@ MX 1 ASPMX.L.GOOGLE.COM.
@ MX 5 ALT1.ASPMX.L.GOOGLE.COM.
@ MX 5 ALT2.ASPMX.L.GOOGLE.COM.
@ MX 10 ALT3.ASPMX.L.GOOGLE.COM.
@ MX 10 ALT4.ASPMX.L.GOOGLE.COM.

(Note: Google Workspace also supports a single MX record layout using SMTP.GOOGLE.COM. at priority 1 for modern setups).

Step 3: Delete legacy records and wait for propagation

Locate any default MX records previously generated by Squarespace or old hosting providers and click the trash icon to remove them. Conflicting MX records prevent mail delivery. Once saved, allow 24 to 48 hours for global DNS servers to update. You can verify your MX propagation using online lookup utilities or Google's Admin Toolbox.

Step 4: Verify inbound message routing

Send an external test email from an outside account (such as personal Gmail or Outlook) to your new Google Workspace custom domain address. Confirm that the message reaches your Google Workspace inbox without delay or delivery bounce errors.


How to configure SPF records for Google Workspace on Squarespace?

You configure SPF records for Google Workspace on Squarespace by creating a TXT record with the host value set to @ and the points-to value set to v=spf1 include:_spf.google.com ~all. This record explicitly authorizes Google Workspace servers to transmit legitimate emails on behalf of your custom domain.

Sender Policy Framework (SPF) serves as an identity validation mechanism that protects your domain against unauthorized spoofing. When an email server receives a message from your domain, it looks up your DNS zone file to check if the sending IP address matches an approved resource declared in your SPF string.

Host: @
Type: TXT
Value: v=spf1 include:_spf.google.com ~all

A common technical blunder when managing DNS records is publishing multiple SPF TXT records for a single root domain. Under RFC 7208 standards, a domain must never have more than one SPF record published; presenting multiple records causes receiver validation to break, resulting in a PermError and routing your mail to spam folders.

If your team uses external tools like marketing platforms or CRM applications alongside Google Workspace, you must combine those sending services into one unified SPF string using include mechanisms:

v=spf1 include:_spf.google.com include:sendgrid.net ~all

For scaling teams deploying cold outreach across multiple sending assets, maintaining manual SPF strings across dozens of domains easily leads to syntax failures. Teams can manage their sending infrastructure efficiently using Infrabox to monitor multi-domain DNS setups and maintain deliverability.


Why is DKIM authentication required for Google Workspace senders?

DKIM authentication is required for Google Workspace senders because it embeds an encrypted cryptographic signature into every outbound email header, verifying to receiver servers that the sender owns the domain and the message contents were not tampered with during transmission. Major providers automatically block unsigned high-volume outbound mail.

DomainKeys Identified Mail (DKIM) works via a public-private key cryptographic pair. Your private key stays hidden on Google's secure mail servers to sign outbound headers. Meanwhile, you publish the matching public key in your Squarespace DNS. Receiving hosts retrieve the public key to validate the digital signature on incoming messages.

Host: google._domainkey
Type: TXT
Value: v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQE...

Follow these technical steps to implement DKIM signing:

  1. Generate the key pair: Log into the Google Workspace Admin Console. Navigate to Apps > Google Workspace > Gmail > Authenticate email. Select your domain and click Generate New Record. Choose a 2048-bit key length and leave the default prefix selector as google.
  2. Add the TXT record in Squarespace: Copy the generated text values. Open your Squarespace DNS Settings dashboard and select Add Record. Change the record type to TXT. Enter google._domainkey inside the Host field. Paste the long public key string starting with v=DKIM1; k=rsa; p= directly into the Value field.
  3. Activate signing in Google Workspace: Return to your Google Workspace Admin Console panel after allowing up to 24 hours for DNS propagation. Click the Start Authentication button. Once active, Google will begin appending cryptographic headers to all outbound mail.

How do you enforce DMARC policies for maximum inbox placement?

You enforce DMARC policies for maximum inbox placement by adding a custom TXT record named _dmarc to your Squarespace DNS panel that evaluates SPF and DKIM authentication outcomes. Setting progressive DMARC policies instructs receiving servers on whether to monitor, quarantine, or reject unauthorized messages spoofing your domain.

DMARC (Domain-based Message Authentication, Reporting, and Conformance) unifies SPF and DKIM mechanisms. It provides reporting back to the domain administrator while establishing compliance mandates for mailbox providers like Google and Yahoo, who now enforce strict authentication rules for bulk senders.

Host: _dmarc
Type: TXT
Value: v=DMARC1; p=none; rua=mailto:[email protected]

To deploy DMARC securely without interrupting internal business workflow, follow a phased policy rollout:

  • Phase 1: Monitoring (p=none)
    Publish your initial record as v=DMARC1; p=none; rua=mailto:[email protected]. This monitors delivery data and sends diagnostic reports without impacting inbox delivery.
  • Phase 2: Quarantine (p=quarantine)
    After verifying that all legitimate sending sources pass SPF and DKIM alignment, upgrade your record policy to v=DMARC1; p=quarantine; pct=100; rua=mailto:[email protected]. Receiver networks will automatically route unauthenticated emails to the recipient's spam folder.
  • Phase 3: Strict Rejection (p=reject)
    To protect your primary brand domain from identity abuse, update your DMARC string to v=DMARC1; p=reject; rua=mailto:[email protected]. Incoming messages failing authentication checks will be dropped completely by receiving servers.

Before deploying outbound sales campaigns, confirm your setup against this mandatory technical checklist:

  • Google standard MX hostnames are published without conflicting legacy mail records.
  • Exactly one unified SPF TXT record exists containing include:_spf.google.com alongside a soft-fail (~all) tag.
  • 2048-bit DKIM selector key (google._domainkey) is added to Squarespace and activated inside Google Workspace Admin.
  • A valid DMARC TXT record under host _dmarc is active with an assigned aggregate reporting email address.

Which setup method works best for outbound cold outreach teams?

Dedicated infrastructure platforms work best for outbound cold outreach teams because they automate DNS deployment, manage secondary domains at scale, streamline mailbox provisioning, and prevent manual configuration drift across multiple domains. Manual setup options become slow, error-prone, and inefficient as outbound operations expand.

Outbound sales organizations, growth agencies, and enterprise sales dev teams frequently manage dozens of sending domains and hundreds of distinct mailboxes to distribute sending volume safely.

While manual DNS administration inside Squarespace works well for single-domain setups, managing expansion domains manually leads to broken authentication syntax, missing DKIM keys, and high administrative overhead.

Teams building cold outreach infrastructure often evaluate several market approaches:

  1. Manual Registrar Setup: Entering records manually inside registrars like Squarespace. This offers direct control over individual records, but introduces high operational friction when managing multiple accounts.
  2. Registrar Auto-Setup Wizard: Built-in domain setup utilities provided by website builders. While fast for basic single-mailbox connections, these wizards usually miss custom DKIM key generation and advanced DMARC monitoring configurations.
  3. Dedicated Infrastructure Platforms: Email platforms such as Infrabox, InboxKit, Zapmail, Mailforge, and Maildoso automate multi-domain authentication, mailbox warm-up routines, and deliverability monitoring. (Note: Teams should evaluate individual competitor websites directly to review their latest specs, workflow support, and active features).

The technical differences between these setups highlight why automated deployment tools suit scaling outbound teams:

Evaluation Criteria Manual Squarespace DNS Entry Registrar Auto-Wizards Dedicated Infrastructure Platforms (e.g., Infrabox)
Setup Speed Slow (15–30 mins per domain) Fast (2–5 mins per domain) Automated (Bulk domain deployment)
Deliverability Monitoring None (Requires manual testing) Basic (Connection status only) Real-time monitoring and analytics
Multi-Domain Scaling Hard (High risk of human error) Moderate (Limited bulk actions) Built for high-volume portfolio management
Configuration Drift Risk High Medium Low (Automated alignment checks)
Sequencer Export & Integrations Manual CSV transfers Manual exports Native platform integration

For agencies managing cold outreach programs, using automated tools like Infrabox email insights reduces administrative burden while verifying that every domain maintains optimal DKIM key alignment and deliverability health.


How can you protect deliverability after setting up your domain?

You protect deliverability after setting up your domain by running automated warm-up routines, maintaining controlled daily sending ramps, validating lead lists, and monitoring your sender reputation over time. Proper DNS configuration provides the foundation, but ongoing sender behavior dictates whether your emails land in the inbox.

Major internet service providers inspect sending behavior to separate legitimate outbound senders from spammers. If a newly configured domain suddenly sends hundreds of cold emails on day one, receiving servers will flag the domain—even if your SPF, DKIM, and DMARC settings pass validation.

To preserve inbox placement after completing your Squarespace DNS setup, adopt these deliverability habits:

  • Warm up new mailboxes gradually: Start new mailboxes at low daily volumes (5 to 10 emails per day) and scale sending gradually over 3 to 4 weeks. This pattern establishes positive engagement history across receiver networks.
  • Validate email addresses prior to sending: Clean your outreach lists using list validation tools to remove invalid or inactive addresses, keeping hard bounce rates strictly under 2%.
  • Monitor spam complaints: Keep your spam complaint rate below Google and Yahoo's absolute maximum threshold of 0.30% (ideally under 0.10%) to preserve your domain reputation.
  • Maintain SPF alignment: Regularly audit your outbound software toolstack to confirm third-party senders remain correctly referenced within your published SPF record.

Outbound sales teams using Infrabox deliverability tools can access features like InfraGuard deliverability protection, Email Validate, and Inbox Placement tracking to detect routing issues before launch. Infrabox also includes an integrated email warm-up network starting at $3 per mailbox, helping enterprise teams protect sender reputation across all outreach assets.


Master Your Domain Setup for Maximum Reach

Configuring your Google Workspace domain on Squarespace requires establishing four core DNS components: point your MX records to Google mail servers, define authorized senders in your SPF record, append a 2048-bit cryptographic signature using DKIM, and publish a progressive DMARC policy to protect your domain identity.

Completing this authentication setup prevents spoofing, fulfills strict sender requirements from major inbox providers, and lays the groundwork for high inbox delivery rates.

Pairing proper technical DNS records with systematic email warm-up and continuous deliverability monitoring ensures your messages consistently land in the primary inbox rather than the spam folder.

Ready to simplify your sending setup and protect your sender reputation at scale? Start free with Infrabox to streamline domain management, automate mailbox warm-ups, and elevate your outbound email performance.

Frequently asked questions

How do I add Google Workspace MX records in Squarespace?
To add Google Workspace MX records in Squarespace, log into your account, navigate to your domain settings, and select the DNS settings panel. Delete any existing default MX records and input the primary and secondary Google MX values provided during your Workspace setup. Ensure you save your changes, keeping in mind that DNS propagation can occasionally take up to 24 hours to complete globally before Google can receive your incoming mail.
What is the correct SPF record format for Google Workspace on Squarespace?
The correct Sender Policy Framework record format for Google Workspace is a TXT record with the host set to your root domain or '@' and the value 'v=spf1 include:_spf.google.com ~all'. This tells receiving mail servers that Google servers are authorized to send emails on behalf of your custom domain. Adding this to your Squarespace DNS manager prevents domain spoofing and helps legitimate messages bypass harsh initial spam filters.
Where do I find my DKIM keys for Google Workspace?
You can find your DomainKeys Identified Mail keys inside the Google Workspace Admin console under Apps, Google Workspace, Gmail, and then Authenticate email. Select your domain and click generate new record, which provides a TXT record name and a long cryptographic key value. You must then copy these exact values and paste them as a new TXT record inside your Squarespace DNS settings panel.
How should I set up my DMARC record in Squarespace?
To set up a DMARC record in Squarespace, create a new TXT record with the host set to '_dmarc' and the value configured with a policy, such as 'v=DMARC1; p=none; rua=mailto:[email protected]'. The policy tag dictates how receiving servers handle unauthenticated messages, starting with a monitoring policy of none before advancing to quarantine or rejection. This protocol uses your SPF and DKIM alignments to protect your brand identity.
How long does it take for Squarespace DNS changes to update?
Squarespace DNS changes typically take anywhere from a few minutes up to 24 hours to propagate across global servers. While MX records might resolve quickly, authentication protocols like SPF, DKIM, and DMARC often require time before Google Workspace and external mail servers fully recognize them. You can use online DNS lookup tools to verify whether your records have successfully updated worldwide before launching your campaigns.
How does Infrabox help manage domain infrastructure after setup?
Once your domain is authenticated, platforms like Infrabox assist agencies and outbound teams by offering robust [domain management](https://infrabox.software/) and deliverability add-ons like InfraGuard. You can seamlessly monitor inbox placement, run an automated email warm-up network, and track insights to ensure your sending reputation stays pristine across various mailbox providers.

Written by

Infrabox Team

Editorial

Writes about email infrastructure and deliverability for the Infrabox blog, drawing on hands-on experience running domains, mailboxes and warm-up.

Try Infrabox

Put this into practice on your own fleet

Infrabox manages your domains and mailboxes, warms them up on our warm-up network, and checks deliverability with InfraGuard, Email Validate and Inbox Placement.