// GUIDE

SPF, DKIM and DMARC in IONOS

If your domain uses IONOS name servers, the SPF and DKIM for its mail come already set up. If the DNS is elsewhere (for example, on Cloudflare), you copy those records yourself. You add DMARC either way.

What to publish

SPF TXT @ (the domain)

v=spf1 include:_spf-eu.ionos.com ~all

For European accounts (IONOS Spain, Germany…); in the United States, include:_spf-us.ionos.com. With IONOS name servers it is added automatically (“IONOS SPF”).

DKIM CNAME s1-ionos._domainkey

s1.dkim.ionos.com

Only if your DNS is outside IONOS; with its name servers it is already there.

DKIM CNAME s2-ionos._domainkey

s2.dkim.ionos.com

Same. If IONOS help or the panel show you another DKIM record, copy it as it is too.

DMARC TXT _dmarc

v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com

Start at p=none with reports and move to quarantine and reject once all your legitimate mail passes (below).

Step by step

  1. In the IONOS panel, open the domain’s DNS settings.
  2. With IONOS name servers, check that the “IONOS SPF” (TXT) record is there and that there is no other SPF record: if you send from more services, their include: go in that same record.
  3. With DNS outside IONOS, create the SPF record and the DKIM CNAMEs from the table at your DNS provider (TTL of one hour).
  4. Add the DMARC record (type TXT, name _dmarc) and read the reports for a few weeks before raising the policy.

Usual mistakes

Towards p=reject

DMARC at p=none only watches. The reports (rua) show who sends on your behalf; once all your legitimate mail passes aligned SPF or DKIM, move to quarantine and then to reject. That way, nobody can use your domain to send forged mail.

Check your domain

Sources

Checked on 24 September 2026. Panels change: if something does not match, the provider’s documentation wins.