Skip to main content
🇵🇱
DNS & email

SPF, DKIM and DMARC on Polish hosting providers (home.pl, nazwa.pl, OVH, cyberfolks)

Ready-made SPF values and instructions on where to add SPF, DKIM and DMARC records in the home.pl, nazwa.pl, OVH and cyberfolks panels

📖 Detailed description

Theory is fine, but in practice the question is: where do you click in the home.pl, nazwa.pl, OVH or cyberfolks panel to stop your mail from falling into spam? The rule is the same everywhere: SPF and DMARC are plain TXT records added in the DNS zone editor of the domain, while DKIM is usually enabled with a single switch in the email settings. If you receive bounces with a message like 550 SPF check failed, it means your SPF record does not cover the server you actually send from.

home.pl: you add TXT records in the client panel: Domains → (next to the domain) Options → Manage DNS records. The home.pl help pages describe an SPF record based on the mail server, for example v=spf1 a mx ip4:SERVER_IP ~all; a variant with an include (such as include:_spf.home.pl) is also seen in the wild - always confirm the current value for your plan in the home.pl knowledge base. DKIM for home.pl mail is enabled in the email service settings in the panel.

nazwa.pl: in the Client Panel select the domain and go to the DNS zone record configuration, where you add a TXT record for the domain. A typical SPF points to the nazwa.pl servers via an include (for example v=spf1 include:_spf.nazwa.pl ~all) - confirm the exact include address in the nazwa.pl help pages, because providers do change them. DKIM at nazwa.pl is sometimes activated automatically for mail hosted with them - check this in the CloudMail/email service settings.

OVH: in the OVHcloud panel go to Web Cloud → Domains → your domain → the DNS Zone tab → Add record → TXT. The official SPF value for MX Plan/Exchange mail is v=spf1 include:mx.ovh.com ~all (OVH also has an SPF wizard in the Domains tab). DKIM for OVH email services is activated in the panel next to the email product.

cyberfolks.pl: you edit records in the panel in the domain DNS management section. According to the official help, the default SPF for mail on their servers is v=spf1 a mx include:_spf.cyberfolks.pl -all; if you keep your DNS elsewhere, add just include:_spf.cyberfolks.pl to your existing record. DKIM is enabled in the panel in the email settings (sender verification).

On top of that, with every host it is worth adding DMARC - a TXT record named _dmarc, starting for example with v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com. You can generate it at /dmarc-generator, build your SPF at /spf-generator, and verify that everything works after the changes at /test-poczty (an A-F grade) and in the record preview at /dns. Remember about propagation - DNS changes may only become visible after a few hours.

Most common problems

SPF does not cover the hosting server

A record copied from the internet lacks the include of your host - mail falls into spam or bounces with a 550 error

Two SPF records after a migration

The old entry from the previous host plus a new one - the standard allows only one, so verification stops working entirely

DKIM was never switched on

The host offers DKIM with a single click, but the option is often off by default - mail goes out unsigned

No DMARC despite valid SPF and DKIM

Gmail and Yahoo require DMARC from bulk senders - without a _dmarc record the inbox is harder to reach

How to fix it?

Find the DNS zone editor in your hosting panel (home.pl: Manage DNS records; OVH: the DNS Zone tab; cyberfolks: DNS record editing) and add entries as TXT

Use the SPF value of your host: OVH - include:mx.ovh.com, cyberfolks - include:_spf.cyberfolks.pl; for home.pl and nazwa.pl confirm the include in the official host documentation

After a hosting migration remove the old SPF record - exactly one v=spf1 entry must remain

Enable DKIM in the email settings of the hosting panel and check that the key appeared in DNS

Add a _dmarc record (start: p=none with a rua address) - generate it at /dmarc-generator

After every change wait for propagation and verify the whole setup at /test-poczty and /dns

Examples

Good example

cyberfolks: v=spf1 a mx include:_spf.cyberfolks.pl -all + DKIM enabled + _dmarc with p=quarantine

Bad example

v=spf1 include:_spf.google.com ~all on a domain that sends mail from a home.pl server - SPF fail and 550 bounces

Check this indicator for your website

Get a detailed analysis and personalized tips on how to improve this element on your website.

Start free analysis