Back to Domain Verification
SPF
Domain Security

SPF Record

PostFrame gives you the exact SPF record to publish — v=spf1 include:amazonses.com ~all — checks it on demand, and if your domain already has an SPF record it shows the merged line to paste instead of a second one.

How SPF Works

Authorized sender list
SPF publishes a DNS TXT record listing the IP addresses and services allowed to send for your domain
Spoofing prevention
Receiving servers check the SPF record to verify the sending server is authorized — blocking forged senders
Generated for you
PostFrame lists the exact include directive to publish and resolves the record live when you press Check
One record per domain
A domain may have only one SPF record; if one exists, the check reports a mismatch and shows the merged record ready to paste
SPF Record Example
Record type
TXT
Host
@ (root domain)
Value
v=spf1 include:amazonses.com ~all
Bounce domain too
bounce.yourdomain.com gets its own MX and SPF so the envelope sender aligns
Questions

Common questions, straight answers.

What exactly do I add for SPF?

A TXT record at the root of your domain with the value v=spf1 include:amazonses.com ~all, plus a second TXT record with the same value on bounce.yourdomain.com for the custom bounce domain.

My domain already has an SPF record — do I add a second one?

No. A domain may have only one SPF record and a second one breaks both. PostFrame detects the existing record, reports a mismatch, and shows the merged record with the include added so you can paste it over the old one.

How does PostFrame check the record?

It resolves the TXT record with a live DNS lookup each time you press Check and reports found, missing or mismatch per record, along with the value it saw.

Run your business from one place.

Five plans, seventeen launch apps, one dashboard. Set up in under 5 minutes — change tiers any time.

From $0 · Basic $9.95/mo · Save 20% on annual billing · Upgrade or downgrade any time