GetResponse email authentication
Marketing automation and landing-page platform.
SPF record
Add GetResponse to your domain's SPF record with this include:
include:_spf.getresponse.com
A complete record for a domain sending only through GetResponse:
v=spf1 include:_spf.getresponse.com ~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.getresponse.com published when this page was generated:
v=spf1 ip4:104.160.64.0/23 ip4:104.160.67.128/25 ip4:104.160.68.224/27 ip4:104.160.69.0/27 -all
Domains using GetResponse
Found while resolving 293 well-known domains on 2026-08-04 — each authorises
_spf.getresponse.com in its published SPF record:
DKIM
Enable DKIM inside GetResponse 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 GetResponse is authenticating, publish a DMARC record — start at
p=none with a reporting address and
tighten from there.
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.