mailampel

← All articles

Setting up SPF, DKIM and DMARC at Hetzner: konsoleH and Hetzner Console

Webhosting or managed server at Hetzner: DKIM with one click in the konsoleH mail security, the automatic default SPF, the DMARC record by hand — and where the DNS records live, depending on whether konsoleH or the Hetzner Console manages the zone.

6 min read · Updated 7 September 2026

With Hetzner webhosting and managed servers you handle DKIM and SPF in konsoleH under mail security ("Mailsicherheit"): "Enable DKIM" generates the key pair, and if the konsoleH nameservers manage the domain, Hetzner sets the DNS record and a default SPF automatically. Only DMARC you create yourself as a TXT record _dmarc — in the konsoleH DNS administration or, if the zone lives there, in the Hetzner Console under DNS.

Two interfaces, that is the pitfall: konsoleH belongs to webhosting (mailboxes, mail security, DNS administration of the hosting domains); the Hetzner Console manages cloud servers and DNS zones of domains that do not run on the konsoleH nameservers. First check which nameservers your domain has — then you know where the records belong.

Step 1: Enable DKIM in konsoleH

Step 2: SPF

When the konsoleH nameservers are used, Hetzner automatically sets a default SPF record for its own mail servers, according to the docs. Look at it in the DNS administration (TXT record starting with v=spf1) and use it as the basis. Hetzner explicitly warns: anyone sending via external services that are not in the record gets delivery problems — then add the services, in the same record:

DNS record of type TXT:
Name / host
your-domain.com
Value
v=spf1 <Hetzner default from the DNS administration> include:spf.protection.outlook.com -all
Do not retype the Hetzner part; take it from the existing record — Hetzner does not document the value publicly. Example addition for Microsoft 365. Never create a second SPF record.

With external nameservers there is no automatism: there you create the SPF record yourself, with the servers that send in your name (guide).

Step 3: DMARC

According to the Hetzner docs, DMARC is configured as a TXT record under _dmarc; Hetzner gives v=DMARC1; p=none as an example and does not create it automatically. Add a reporting address so you can see who sends in your name:

DNS record of type TXT:
Name / host
_dmarc.your-domain.com
Value
v=DMARC1; p=none; rua=mailto:dmarc@your-domain.com
Tighten after two to four weeks of reports — the [[dmarc-einfuehren|step-by-step plan]]; every parameter in [[dmarc-eintrag|The DMARC record explained]].

Step 4: Where the record belongs

Step 5: Check

After setting, check the domain from the outside — SPF syntax, DKIM selector, DMARC — and send a test email to a Gmail mailbox: "Show original" must show spf=pass, dkim=pass, dmarc=pass. That is also the way to confirm the generated selector.

Frequently asked questions

konsoleH or Hetzner Console — where do I enter the records?

Wherever your domain's nameservers are. If the domain runs on the konsoleH nameservers, in konsoleH under DNS administration → DNS records; if the zone is in the Hetzner Console, there under DNS. With third-party nameservers, at that provider.

Does Hetzner set SPF automatically?

Yes, with konsoleH nameservers a default SPF record is set according to the docs. It only covers Hetzner's mail servers — every further sending service has to be added to the same record, otherwise its mail lands in spam.

How do I enable DKIM at Hetzner?

In konsoleH under mail security with "DKIM aktivieren". Hetzner generates the key pair; with konsoleH nameservers the record lands in DNS automatically, with external nameservers you enter the displayed TXT record by hand.

Does Hetzner create DMARC?

No, you create the TXT record _dmarc yourself. Hetzner gives v=DMARC1; p=none as an example — start with that plus a reporting address and tighten after the observation phase.