IONOS SPF setup
In brief
Set up IONOS SPF with the documented DNS preset or U.S. external-DNS record, preserve other senders, and check the published record and message results.

IONOS SPF setup uses the IONOS SPF TXT preset when IONOS hosts your DNS, or the documented IONOS SPF value at your external DNS provider. Before saving a change, check the existing SPF record and every service that sends for the domain; adding IONOS must preserve those other senders in one policy.
At a glance
Quick takeaways
- Configure SPF where the relevant domain's authoritative DNS is managed.
- Use the IONOS mail service's instructions; registration or website hosting alone does not identify the email sender.
- Keep one SPF policy per domain and preserve other legitimate senders when editing it.
- Check the published record and a new message from the actual sending application separately.
- SPF authentication contributes to DMARC only when the authenticated domain aligns with the visible From domain.
What should I check before configuring IONOS?
Start with the sending account and the domain you intend to authorize. A business can have IONOS mailboxes alongside a CRM or an invoicing service. Record those systems before changing a policy that they share. The SPF reference explains how the mechanisms authorize sending infrastructure.
SPF normally checks the SMTP envelope-sender domain, which can differ from the address a person sees in From. RFC 7208 defines that identity. Use message evidence to establish the domain being checked instead of assuming that the visible address selects the DNS zone.
Do not copy account-specific domains, selectors or verification tokens from another customer's setup. The shared IONOS include below is a published provider value, scoped to the U.S. documentation cited beside it.
Save the current TXT answer and identify who can restore it. Write down the actual domain, existing policy, intended sender addition and a test plan. Keep that note with the DNS administrator; it does not belong in a public screenshot or support post.
Which setup method should I use?
Choose the DNS location first. With IONOS-managed DNS, use its preset workflow below. With external DNS, publish the corresponding policy at that provider. Check whether IONOS SPF is already present before making a change: IONOS describes SPF as enabled by default for its hosted domains.
For the U.S. IONOS email service, the same official guide supplies this external-DNS value:
v=spf1 include:_spf-us.ionos.com ~allUse that complete value only when it matches your service and sending inventory. If other senders are authorized already, retain their mechanisms in the existing policy rather than replacing it with an IONOS-only record. Check the regional documentation for a different IONOS service; do not assume this U.S. include applies to every product.
Two separate SPF records at one name are invalid. RFC 7208 section 3.2 requires a single selected policy. Its lookup limit also applies across included records, so counting only the includes visible in your own line is insufficient.
How do I configure SPF for IONOS?
1. Open the domain's DNS records
In IONOS, open Domains & SSL, find the intended domain and use its Actions menu to select DNS. This is the path in IONOS's TXT-management instructions. Compare the existing SPF value with your change note before proceeding.

2. Select the IONOS mail preset
Click Add Record, then choose IONOS SPF (TXT). The official SPF procedure distinguishes this preset from a manually defined policy.

3. Save and inspect the resulting policy
Click Save. IONOS documents that this option supplements an existing SPF record with its mail-server authorization. Inspect the resulting value rather than assuming that other senders survived the change. The IONOS guide allows up to 48 hours for global propagation; compare authoritative and cached answers before editing again.

4. Use your external DNS provider when it owns the zone
For external DNS, enter the appropriate policy as TXT at the actual SPF domain. At the zone root, a provider commonly represents the name as @; confirm its name-entry rules before saving. Do not treat @ as a wildcard covering every subdomain.
Preserve any existing policy and its final qualifier when planning a merge. Do not paste a second v=spf1 into the value or append an include after all: under RFC 7208 section 5.1, mechanisms after a matching all are not evaluated. Keep changes to other authentication records outside this SPF update.
How does this setup affect DMARC?
IONOS SPF authorization is one part of DMARC validation. DMARC needs an SPF or DKIM pass that aligns with the visible From domain, as defined in RFC 9989. A passing SPF result for an unrelated return-path domain does not supply that alignment.
Keep DMARC record configuration with the separate IONOS DMARC setup guide. Do not change DMARC policy merely because an SPF TXT lookup succeeds, and do not interpret authentication as a guarantee of inbox delivery.
How do I validate the setup?
DNS: compare the intended and published record
Query TXT records at the exact domain being checked. For an illustrative domain:
dig +short TXT example.comReplace example.com with your domain. Compare the complete answer with the policy you intended to publish, including other approved senders. Check the authoritative answer when a public resolver still returns an older value. A retrieved TXT record proves publication at that observation, not sender behavior.
Vendor status: confirm the saved configuration
Reopen the DNS entry and compare it with your change note. For external DNS, check the provider that actually saved the record. A successful save confirms a configuration action; it does not prove that your application sent through IONOS or that a receiver accepted the message.
Message headers: test the actual sending path
Send a new test through the configured mailbox or application to a mailbox you control. Inspect the receiving system's SPF result and the domain it evaluated. Repeat the check for other important sending systems after a shared policy changes. Use the same production path you are trying to validate, rather than a different application that happens to use the same From address.
DMARC reporting: check alignment over time
When aggregate reports arrive, compare the source's authentication and alignment results with the test message. Reports can help reveal another sender that the one-message test missed. Reports are receiver-generated and may be incomplete; their absence does not establish that no mail was sent. RFC 9989 describes reporting separately from message validation.
Troubleshooting
IONOS SPF is already present
Inspect the existing policy before adding anything. If it authorizes the intended sending path already, gather message evidence for the reported failure instead of creating another SPF record. Avoid resetting the whole DNS zone to investigate one authentication result.
Another service also sends mail
Keep the other service's authorization in the single SPF policy. Recheck both services after the edit. If you cannot identify an existing mechanism's owner, resolve that question with the mail administrator before removing it. A short record is not necessarily a complete sending inventory.
SPF passes but DMARC fails
Compare the authenticated domain with the visible From domain and inspect DKIM alignment. SPF pass alone does not diagnose a DMARC failure. The alignment rules are in RFC 9989; keep DNS authorization and message alignment as separate checks.
Public DNS still shows the old value
Confirm that you edited the authoritative zone and the intended record name. Preserve the authoritative and public-resolver observations with their timestamps. Another edit while cached answers differ makes the result harder to diagnose.
Check the IONOS SPF record you published
Check your SPF record and compare the public answer with the configuration you intended. Then use a newly delivered message to test the actual sending path.
A public lookup cannot prove how a delivered message authenticated or change your DNS. Keep the published-record result alongside the message and report evidence when deciding whether the setup is complete.
If more sending services appear after this repair, a one-time SPF lookup leaves an ongoing sender-review task. Palisade's Domain Overview describes how Palisade's DMARC Agent analyzes DMARC aggregate-report data, identifies sending sources and authentication or alignment issues, and creates prioritized remediation tickets for human review. Proposed DNS and policy changes require approval; monitoring does not guarantee delivery.
Evidence
Sources and further reading
Questions readers ask
Frequently asked questions
Does every IONOS domain need a manual SPF change?
No. Check the existing IONOS SPF configuration first, then determine whether the domain uses the IONOS mail service and whether another approved sender needs authorization. An existing correct policy does not need another record simply because a setup guide is available.
Can I use IONOS email with DNS hosted elsewhere?
Yes. Publish the SPF policy at the provider responsible for the domain's authoritative DNS. Use the documented value for the IONOS mail service you actually use, and preserve any other legitimate senders in that policy.
Should I create a second SPF record for IONOS?
No. Keep one SPF policy for that domain and incorporate the required sender authorization there. Multiple separate SPF policies at the same name are invalid under RFC 7208.
Does the U.S. IONOS include cover every IONOS product?
No. This guide scopes the published include to the U.S. mail documentation it cites. Check the official instructions for your actual regional product before applying a value to another service or sending path.
Does an SPF pass mean DMARC passes too?
No. DMARC also requires alignment with the visible From domain through SPF or DKIM. Check the delivered message's domains and results, as defined in RFC 9989, before changing a DMARC policy.


Written by
Samuel ChenardCEO & Co-Founder, Palisade
Samuel Chenard is the CEO and co-founder of Palisade, agentic DMARC software for IT teams and MSPs, from one domain to thousands.
More from Samuel →


