Setting up SPF at All-Inkl — Step-by-Step Guide (2026)

Last updated: July 2026

In short: After this guide your domain publishes a correct SPF record. Receiving mail servers can then tell which servers are allowed to send in your name — and sort out forged senders.

Prerequisites

An All-Inkl package with at least one domain
Access to the KAS (technical administration)

What is SPF?

SPF (Sender Policy Framework) is a TXT record in your domain’s DNS. It lists which mail servers are allowed to send email with your domain as the sender. Receiving servers look up the record on every incoming message and check whether the delivering server is on the list. Without SPF, any server can send mail in your name — and your legitimate mail lands in spam faster, because large receivers like Gmail now simply expect SPF.

For context: SPF alone is not complete protection. Only together with DKIM and DMARC does it become a solid foundation. But SPF is the easiest entry point.

The starting point at All-Inkl

Unlike providers with ready-made SPF switches, at All-Inkl you enter the record yourself as a TXT entry in the KAS. The official All-Inkl recommendation is:

v=spf1 a mx include:spf.kasserver.com ~all

That’s a clever construction: a and mx authorize the servers your domain already points to via its A/AAAA and MX records — at All-Inkl, that’s your KAS server. The include adds a central All-Inkl sending address (currently exactly one IPv4 address). This way the record adapts automatically if your package moves to a different kasserver.

Step-by-step guide

1. Check whether SPF is already active

Fastest via the terminal:

dig TXT example.com +short | grep spf1

If a record with v=spf1 comes back, your domain already publishes SPF. Alternatively, drop your domain into the free MXAudit scanner — it checks the record for syntax and lookup limits at the same time.

2. Open the DNS settings in the KAS

Log into the KAS (technical administration) and click Tools → DNS settings. Edit the domain whose DNS you want to change.

3. Create (or edit) the TXT entry

Important: there may be only one SPF entry per domain — All-Inkl states this itself. If one already exists, edit it; don’t create a second one.

If the entry is missing, click create new DNS entry and fill in the form like this:

Field	Value
Name	(leave empty)
Type	`TXT (SPF)`
Prio	`0`
Data	`v=spf1 a mx include:spf.kasserver.com ~all`

Then save — the entry appears in the table afterwards.

4. Plan without DNS editing?

If the message “These DNS settings are unfortunately not possible in your plan” appears, there’s a way out: via Reset zone All-Inkl automatically creates the default SPF entry (v=spf1 a mx include:spf.kasserver.com ~all).

Careful: resetting the zone reverts the domain’s DNS settings completely to the default — any additional entries you had are removed. If you’ve set your own records (e.g. for external services), note them down first.

5. Add additional senders (if needed)

If you also send via other services — newsletter tool, CRM, shop system — their servers must be in the record too. You’ll find the required include value in that service’s docs (search for “SPF”). Edit the existing entry and add the include before the ~all:

v=spf1 a mx include:spf.kasserver.com include:spf.newsletter-dienst.de ~all

6. Wait until the change is live

DNS changes take time: depending on TTL and caching it can take a few hours until every server worldwide sees the new record.

The components in detail

Component	Meaning
`v=spf1`	version identifier, always at the start
`a`	allows the servers behind your domain’s A/AAAA record
`mx`	allows the servers behind your domain’s MX record
`include:spf.kasserver.com`	allows the central All-Inkl sending address
`~all`	softfail: all other servers are treated as suspicious, but mail is usually still accepted

a, mx, and include each cost one DNS lookup — so the default entry consumes three of the maximum ten allowed lookups.

Verify the result

Check your configuration with the free MXAudit scanner — it shows immediately whether your SPF record is syntactically correct and how many DNS lookups it consumes.

Or directly in the terminal:

dig TXT example.com +short | grep spf1

The output must contain exactly one record with v=spf1.

Common mistakes

Two SPF records. Two TXT entries with v=spf1 cause a permerror — receiving servers then ignore SPF entirely. All-Inkl’s own guide points this out explicitly: edit the existing entry instead of creating a new one.

Resetting the zone without a backup. The convenient route for small plans deletes all additional DNS entries. Note your records first, then reset.

Domain name in the Name field. For the main domain’s SPF record, the Name field stays empty — entering the domain there creates the record in the wrong place.

+all at the end. A +all allows any server to send and makes the whole record useless. Still shows up in some old forum posts — don’t copy it.

Forwarding fails. If a recipient auto-forwards your mail, SPF often fails at the final recipient — the forwarding server isn’t in your record. That’s a design weakness of SPF, not a configuration error; DKIM and DMARC catch this case.