InboxAudit

Postmark email authentication

Transactional-only provider known for keeping application mail out of marketing IP pools.

SPF record

Add Postmark to your domain's SPF record with this include:

include:spf.mtasv.net

A complete record for a domain sending only through Postmark:

v=spf1 include:spf.mtasv.net ~all

What it costs you

1 of your 10 DNS lookups. That is the cheapest an include can be — the record it points at contains only IP ranges, with no further includes to follow. Behind it are 4 IP ranges.

Live record

This is what spf.mtasv.net published when this page was generated:

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

Domains using Postmark

Found while resolving 293 well-known domains on 2026-08-04 — each authorises spf.mtasv.net in its published SPF record:

DKIM

Enable DKIM inside Postmark and publish the selector record it generates. DKIM matters more than SPF for deliverability, because a DKIM signature survives forwarding while SPF does not — see how selectors work.

DMARC

Neither SPF nor DKIM protects the address your recipients actually see until DMARC ties them to it. Once Postmark is authenticating, publish a DMARC record — start at p=none with a reporting address and tighten from there.

Generate a DMARC record →

Check it worked

DNS changes take minutes to hours to propagate. Once published, run the domain through the checker — it resolves the full include chain and reports the real lookup count.