GetResponse will happily send from your address with its own DKIM key — showing “via GetResponse-mail.com” — until you authenticate your domain so the signature is yours.
GetResponse is unusual: you don't add an SPF include because, in its own words, “the sending domain is GetResponse and is already SPF signed”, and custom DKIM is optional. Leave it and your mail is signed with GetResponse's key, shown as “via GetResponse-mail.com”; add custom DKIM — a per-domain generated selector such as 4e4a47eb._domainkey — and it signs as your domain so DMARC can align. Source: getresponse.com/help · verified 2026-07-15
p=none and a rua address, watch reports for a week, confirm this sender shows 100% pass.No. Adding SPF includes and DKIM records only adds authentication — it never blocks existing mail. The only risky step is tightening your DMARC policy, and that comes later, after reports confirm everything passes.
Send yourself a test email and inspect the headers for spf=pass, dkim=pass and dmarc=pass — or just watch your DMARCKeeper dashboard: the sender's pass rate should hit 100% within a day or two.
Yes. SPF and DKIM authenticate mail; DMARC is what tells receivers to BLOCK mail that fails, and it's the piece Gmail, Yahoo and Outlook now check for explicitly.