SPF check
marketstead.com
The SPF policy for marketstead.com ends in -all: mail servers not listed in the policy should be rejected outright.
SPF tells other mail servers which servers may send email as @marketstead.com. The table breaks the record into its rules; the shared policy check follows redirects and shows the result for unlisted senders.
- 1 OK
- SPF record
- v=spf1 include:spf.protection.outlook.com include:spf.postal.marketstead.shop -all
What the record says
| Rule | Value | Meaning |
|---|---|---|
| v=spf1 | Marks this TXT record as an SPF policy. | |
| include | spf.protection.outlook.com | Allow the servers listed in spf.protection.outlook.com's own SPF record. |
| include | spf.postal.marketstead.shop | Allow the servers listed in spf.postal.marketstead.shop's own SPF record. |
| -all | Reject everything not matched earlier. |
The lookups a receiver performs
| Step | Result |
|---|---|
| marketstead.com | v=spf1 include:spf.protection.outlook.com include:spf.postal.marketstead.shop -all |
| include:spf.protection.outlook.com | 0 lookups, 1 record |
| include:spf.postal.marketstead.shop | 0 lookups, 1 record |
| Lookup budget | 2/10 mechanisms, 0/2 void |
Tests
-
OK
Sender Policy Framework (SPF)
The SPF policy for marketstead.com ends in -all: mail servers not listed in the policy should be rejected outright. Lookup budget: 2/10 mechanisms, 0/2 void.
More info about “Sender Policy Framework (SPF)”
SPF is the public list of mail servers allowed to send email as your domain, published as a TXT record. Without it — or with a policy so broken that receivers discard it (a "PermError") — anyone can put your domain in the From: line, and spam filters treat the missing authorization as a strike against everything you legitimately send. The catch: SPF only protects you if every lookup inside it resolves cleanly, which is why this check walks the policy the way a receiving server would, counting the same DNS lookups. RFC 7208 §4.5 selects the record; §5.1 stops at all, §6.1 follows redirect, and §4.7 makes no match neutral, not permission to send. The slow reverse-name ptr rule is discouraged by RFC 7208 §5.5; advice about it does not change the policy grade. RFC 7208 §4.6.4 permits 10 DNS-causing terms; each mx address expansion has a separate limit of 10 address queries.
How we got this answer
Every question we asked, in order, with how long each server took to reply.
-
recursive resolver — asked marketstead.com SOA
· 14 ms
The zone holding marketstead.com is marketstead.com. -
todd.ns.cloudflare.com (108.162.193.146) — asked marketstead.com TXT
· 15 ms
3 TXT records returned (authoritative).
Check next
Check something else
Rather not deal with this yourself?
dns.rehab is made by Marketstead. We run DNS, email and the rest of the back office for small businesses — farms, shops, studios, restaurants — and we read reports like this one for a living.
Email me this result
We send it once, with the link. No newsletter, no follow-ups.