Registrar guide

Adding an SPF Record in AWS Route 53 DNS

SPF belongs in a single TXT at your root. AWS Route 53 uses “Record name (blank = apex)” for the left-hand field — use (leave blank for apex) for the apex. Never publish two SPF TXT records.

Exact fields

Type: TXT Record name (blank = apex): (leave blank for apex) Value: "v=spf1 include:_spf.google.com ~all" TTL: Automatic / Auto

The gotcha

Only one TXT may start with v=spf1. If you already have SPF, edit that row — do not add a second.

No proxy — enterprise DNS only.

Verify SPF after you publish

Open DNS Preflight →

See also: SPF record guide · SPF glossary · Too many lookups

Step by step

Step 1 Navigate to AWS Console → Route 53 → Hosted zones → your domain → Create record.

Step 2 Click Create record and choose type TXT.

Step 3 Set Record name (blank = apex) to (leave blank for apex) for the root domain.

Step 4 Paste your full SPF record starting with v=spf1 — merge with any existing SPF first.

Step 5 Save the record. Wait a few minutes for the zone to update.

Step 6 Run DNS Preflight to confirm SPF and lookup count.

FAQ

How do I add a TXT record in AWS Route 53?

AWS Console → Route 53 → Hosted zones → your domain → Create record. Then Create record → TXT → set Record name (blank = apex) to (leave blank for apex) → paste value → save.

Should I create a second SPF TXT if I use two senders?

No — merge includes into one v=spf1 string. Two SPF TXTs cause PermError.

How long until AWS Route 53 SPF changes propagate?

Often minutes to a few hours. Confirm in DNS Preflight or the Propagation checker.

What if AWS Route 53 splits my TXT into chunks?

Many panels split long strings — SPF usually fits. If something looks wrong, re-copy from your provider.

Where does SPF go?

At the root of your domain — blank apex name in Route 53.

← AWS Route 53 guides

Open DomainPreflight →