# No SPF record

Your domain publishes no SPF record, so receivers can't tell which servers may send mail as it. Mail you send is more likely to land in spam, and Gmail refuses some of it outright.

SPF is one TXT record at your domain itself, such as `example.com`, starting `v=spf1`. The check asked your domain's own nameservers for TXT records there and found none starting `v=spf1`. Other TXT records at the same name, such as a site verification code, don't count.

On the result:

```
No SPF record
Receivers can't tell which services may send as you, so your mail is more likely to land in spam.
```

## Look it up

**Details →** on your result shows what the check found. To look it up yourself, put your domain in place of `example.com`:

```
dig +short TXT example.com
```

On Windows, run `nslookup -type=TXT example.com`. No line containing `v=spf1` means no record.

## Publish one

1. List every service that sends mail as your domain: your mailbox provider, newsletter tool, invoicing, support desk, website forms.
2. For each one, read its setup page. SPF checks the return address (also called MAIL FROM or Return-Path), not the From address you see. Some services use a return address on your domain itself and give you an SPF entry to add, usually an `include:`. Others use their own domain or a subdomain of yours, such as `bounce.example.com`; their entry then goes in the SPF record at that name, or needs nothing from you.
3. At your DNS provider, add a TXT record at the exact name you checked. For `example.com` itself, many providers call that name `@` or leave it blank. For a subdomain such as `mail.example.com`, the name is `mail` in the `example.com` zone; `@` there would change the SPF record of `example.com` instead.
4. Give it the value `v=spf1`, then each service's entry, then `~all`, for example `v=spf1 include:_spf.google.com ~all`. Keep it to one record: a second `v=spf1` record makes receivers return an error for both, as [More than one SPF record](/docs/findings/spf-multiple/) explains.
5. Run the check again.

If the checked name is an alias (CNAME), you can't add a TXT record beside it. The record goes at the name the alias points to: find it with `dig +short CNAME mail.example.com`, or `nslookup -type=CNAME mail.example.com` on Windows. That name may belong to another provider or serve other domains too, so ask whoever runs it.

## Before you switch to -all

Before you change `~all` to `-all`, check that each service passes SPF itself, not only DMARC: DMARC can pass through DKIM alone. Send a test message from each service and open its headers: under `Authentication-Results`, look for `spf=pass` with `smtp.mailfrom=` naming the domain whose record you're changing. A pass for the service's own domain doesn't test your record.

A domain that sends no mail at all gets `v=spf1 -all`: no server may send as it.

[SPF](/docs/spf/) explains how SPF works with DMARC, and how MailGlo can keep the record for you.

## Bounces you may see

Gmail, refusing bulk mail that fails SPF ([Gmail SMTP errors](https://knowledge.workspace.google.com/admin/support/troubleshooting/gmail-smtp-errors-and-codes), updated 10 Nov 2026):

```
550 5.7.27 This message was blocked because it didn't pass SPF authentication. Gmail requires bulk email senders to authenticate their email with SPF.
```

Gmail, when neither SPF nor DKIM passes:

```
550 5.7.26 This email has been blocked because the sender is unauthenticated. Gmail requires all senders to authenticate with either SPF or DKIM.
```
