ShipReady rates this medium. Fix soon. Meaningfully weakens a defence or degrades how the site works.

Paste the fix prompt on this page into Cursor, Claude Code or your AI editor. It is the same prompt ShipReady puts in your report.

Can I check my own site?

Yes — ShipReady scans up to ten pages of any public site for free and reports this alongside every other check.

mediummissing-spf

No SPF record found

`{org_domain}` publishes no SPF record, so there is no list of servers authorised to send mail on its behalf.

Why it matters

`{org_domain}` publishes no SPF record, so there is no list of servers authorised to send mail on its behalf. Receiving servers cannot tell your transactional email from a forgery, which both makes your domain easy to spoof and makes your genuine email more likely to land in spam. SPF is also a prerequisite for DMARC enforcement to do anything useful.

How ShipReady detects it

Email-authentication DNS records (DMARC / SPF). Almost every AI-built SaaS sends transactional email — password resets, magic links, receipts — through Resend, SendGrid or Postmark. Setting that up gets the mail delivered; it does not stop anyone else sending mail that claims to come from the same domain. Without a DMARC policy, a receiving server has no instruction to reject a forgery, so an attacker can send "reset your password" from the product's own domain and the message will land in the inbox looking authentic. This is the only check in the scanner that reads DNS rather than HTTP. It is also the most deterministic: a record either exists or it does not, so there is no heuristic and no false-positive surface. The one place judgement is required is deciding WHICH domain to ask about — see _organizational_domain.

Detection is deterministic. ShipReady reports this only when it observes the condition directly, and prefers to miss a real problem over inventing one. Rule version 1.1.0.

How to fix it

This is the prompt ShipReady puts in your report — written to be pasted straight into Cursor, Claude Code, or whichever assistant built the app.

The domain {domain} has no SPF record, so receiving servers have no list of hosts allowed to send mail as you. Add a single TXT record at {domain} of the form "v=spf1 include:<your-email-provider> ~all" — for example include:_spf.resend.com, include:sendgrid.net, or include:_spf.google.com, depending on who sends your mail. Publish exactly one SPF record (multiple records are invalid), include every service that sends on your behalf, and end with ~all or -all rather than +all.

Frequently asked questions

What does "No SPF record found" mean?: `{org_domain}` publishes no SPF record, so there is no list of servers authorised to send mail on its behalf.
How serious is it?: ShipReady rates this medium. Fix soon. Meaningfully weakens a defence or degrades how the site works.
How do I fix it?: Paste the fix prompt on this page into Cursor, Claude Code or your AI editor. It is the same prompt ShipReady puts in your report.
Can I check my own site?: Yes — ShipReady scans up to ten pages of any public site for free and reports this alongside every other check.

Related checks

Does your site have this?

ShipReady checks this and 73 other things across up to ten pages of your site. Free, no signup.

Scan my site