Email

How to add an SPF record on Namecheap

To add an SPF record on Namecheap, go to Domain List, click Manage next to your domain, open the Advanced DNS tab, click Add New Record, choose TXT Record, set Host to @, paste your SPF rule in Value, then click Save all changes. For Namecheap Private Email, the value is v=spf1 include:spf.privateemail.com ~all. If your domain already has an SPF record, edit it rather than adding another.

SPF lists the servers allowed to send email for your domain. A missing or broken record sends your mail to spam and weakens DMARC.

Last verified: November 13, 2026, against Namecheap's official knowledge base.

Before you start

  • Check where your DNS is hosted. These steps work when your domain uses Namecheap BasicDNS, PremiumDNS or FreeDNS. If it points to Namecheap Web Hosting DNS, Namecheap says to add records in cPanel instead. If it points to another provider, make the change there.
  • List every service that sends as you: your mailbox provider, your website, newsletter and invoicing tools. Each one documents the include: you need. Google Workspace, for example, uses include:_spf.google.com.

The fast route for Private Email

If you use Namecheap Private Email and nothing else:

  1. In your Namecheap account, click Manage next to the domain.
  2. Open Advanced DNS and find the Mail Settings section.
  3. Choose Private Email in the drop-down and click Save changes.

Namecheap then sets up the Private Email DNS records automatically. Check the result in Step 3. If you also send through other services, use Custom MX instead and manage the SPF record yourself, as below.

Step 1: check for an existing SPF record

  1. Go to Domain List and click Manage next to your domain.
  2. Open the Advanced DNS tab.
  3. Under Host Records, look for a TXT record on host @ whose value starts with v=spf1.

Namecheap is explicit: SPF allows only one TXT record per host, and several SPF records on the same host interfere with each other. If you find two, merge them.

Step 2: add or edit the record

  1. Click Add New Record (or the edit icon on the existing SPF record).
  2. Type: TXT Record.
  3. Host: @. Never put your domain name in this field.
  4. Value: your SPF rule. Private Email only:

    v=spf1 include:spf.privateemail.com ~all

    Private Email plus Google Workspace, for example:

    v=spf1 include:spf.privateemail.com include:_spf.google.com ~all
  5. Leave the TTL at its default.
  6. Click Save all changes.

Namecheap says new host records normally take effect within 30 minutes.

Step 3: check it works

nslookup -type=TXT yourdomain.com

You should see exactly one line starting with v=spf1. Our free SPF checker also counts the DNS lookups the record triggers.

~all or -all?

Namecheap explains the difference well: with ~all, receiving servers usually accept mail from unlisted senders but mark it as suspicious; with -all, they may reject it.

Start with ~all. Move to -all only when your DMARC reports have shown, for several weeks, that every legitimate sender passes SPF. To set up those reports, follow our guide on setting up DMARC on Namecheap.

Known pitfalls

  • Two SPF records: for example one added by a website builder and one for Private Email. Merge them into a single record.
  • The 10-lookup limit: every include:, a, mx or redirect costs at least one DNS lookup, and includes often chain further. Past 10, SPF fails with an error. Remove services you no longer use.
  • The domain in the Host field: yourdomain.com as host creates a record on yourdomain.com.yourdomain.com. Use @.
  • Hosting DNS vs BasicDNS: records added in Advanced DNS have no effect if your domain points to Namecheap hosting nameservers, and the reverse is true for cPanel.
  • SPF alone is not enough for DMARC: SPF checks the bounce (return-path) domain, not the From address. When a service uses its own bounce domain, SPF passes but doesn't count for DMARC. DKIM signed with your domain covers that case (see the DMARC guide).

Frequently asked questions

Do I need SPF if my domain doesn't send email?

Yes, it is good practice. Publish v=spf1 -all to say that nothing sends for this domain. This blocks spoofers from using it.

Is SPF enough to fix emails going to spam?

No. Add DKIM and DMARC as well. Gmail and Outlook.com require all three from senders above 5,000 messages a day, and they help at any volume.

Verify it's fixed. AttackScout reads your SPF record from the internet, counts DNS lookups, spots duplicates and tells you whether your domain is ready for DMARC. Free, no account needed. Verify it's fixed

Technical details

Exact configuration. A single TXT record at the root of the domain, starting with v=spf1 and ending with an all mechanism:

v=spf1 include:<service-that-sends-your-email> ~all

Why. SPF (RFC 7208) lists the servers allowed to send email for your domain. The receiving server reads this TXT record and counts at most 10 DNS lookups (include, a, mx, exists, redirect): beyond that the result is permerror and SPF protects nothing. Two SPF records also give permerror. ~all flags without rejecting; -all makes receivers reject anything not listed.

To check it yourself. Exactly one line must start with v=spf1:

dig +short TXT your-domain.com

Reference: https://www.rfc-editor.org/rfc/rfc7208

Sources

Accessed November 13, 2026.