include:spf.mtasv.net – Postmark
Short answer: include:spf.mtasv.net lets Postmark's mail servers pass SPF for your domain. It costs 1 of the 10 DNS lookups SPF allows (checked live).
| Service | Postmark |
|---|---|
| Lookups | 1 of the 10 DNS lookups SPF allows (checked live) |
| Record now | v=spf1 ip4:50.31.156.96/27 ip4:104.245.209.192/26 ip4:50.31.205.0/24 ip4:147.160.158.0/24 -all |
Do you need it?
Often not. From our Postmark setup guide: Not needed on your root domain: the custom Return-Path (a CNAME to pm.mtasv.net) makes Postmark's SPF pass and align with your domain.
If you added include:spf.mtasv.net only because an old article said so, it may just cost lookups. Send a test email through Postmark and see which domain SPF is checked for.
Who uses it
In our scan of top websites on 23 Oct 2026:
- 21 of the 2,214 world's top-3,000 sites that publish SPF (0.9%)
- 2 of the 1,961 India's top-3,000 sites that publish SPF (0.1%)
- 0 of the 428 Indian government sites that publish SPF (0.0%)
Add it the right way
- Keep one SPF record per domain:
v=spf1 include:spf.mtasv.net ~all, plus your other senders in the same record – SPF generator. - Stay under 10 lookups in total; every include counts, nested ones too.
- SPF alone isn't enough for Gmail, Yahoo and Outlook: turn on DKIM and publish DMARC.
Check your domain
After the fix, send a test email to see SPF, DKIM and DMARC pass on a real message, then keep an eye on it: free DMARC monitoring shows every service that sends mail as your domain and which ones fail, in plain English.
Get it fixed on Fiverr
Prefer to do it yourself? Get the step-by-step Fix Kit ($15) – 28-page guide, checklist, 20+ providers.