Column 1

SPF Record For G-Suite

If you're using G-Suite (now known as Google Workspace) for your business emails, it's important to set up a Sender Policy Framework (SPF) record to help ensure that your emails are delivered to your recipients' inboxes. An SPF record is a type of DNS record that verifies that emails sent from your domain are authorized to be sent from G-Suite's servers.

Here's a step-by-step guide to help you set up an SPF record for G-Suite:

Step 1: Log in to your G-Suite account

Step 2: Access DNS settings

Go to the "Domains" section and select the domain you want to set up the SPF record for. Then, click on the "DNS" tab and scroll down to the "Custom resource records" section.

Step 3: Create a new TXT record

Click on the "Add" button to create a new TXT record.

Step 4: Enter your SPF record

In the "Name" field, enter the name of the subdomain you want to use for your SPF record. For example, if you want to set up an SPF record for your main domain, enter "@" (without quotes). If you want to set up an SPF record for a subdomain, enter the name of the subdomain (e.g. "subdomain.example.com").

In the "Type" field, select "TXT". In the "TTL" field, enter "3600" (without quotes).

In the "Data" field, enter the following SPF record:

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

This SPF record allows emails to be sent from your domain through G-Suite's servers.

Step 5: Save your changes

Click on the "Add" button to save your new SPF record.

Step 6: Check your SPF record

Once you have saved your new SPF record, you can check if it's working properly by using an SPF checker tool. Simply enter your domain name and the tool will show you the SPF record that it found.

In conclusion, setting up an SPF record for G-Suite is a quick and easy process that can help ensure that your emails are delivered to your recipients' inboxes. By following the steps above, you can create a more secure and reliable email environment for your business.

Google Workspace SPF checklist

For Google Workspace mail, keep one SPF TXT record at the sending domain and include Google's SPF source. Avoid publishing multiple separate SPF records because receivers can treat that as a permanent SPF error. If other mail services also send for the domain, combine them into the same SPF record instead of adding a second one.

After DNS changes

Wait for DNS propagation based on the record TTL.
Send a test message to a mailbox that shows authentication results.
Review SPF, DKIM, and DMARC together so one change does not break normal mail flow.

Email authentication maintenance note

Email DNS changes should be handled like a launch task, not a quick copy-and-paste job. Before changing SPF, DKIM, DMARC, MX, or SMTP settings, record the current DNS values, confirm who sends mail for the domain, and keep a rollback note in case forms, invoices, password resets, or customer replies stop flowing.

Safe verification checklist

Confirm there is only one SPF TXT record for the domain.
Check that every active sender is included before tightening SPF or DMARC policy.
Verify DKIM signing from the actual mail provider, not only that a DNS selector exists.
Start DMARC in monitoring mode when you are not sure all senders are aligned.
Send test messages to multiple mailbox providers and review headers before declaring the change finished.