In short. SPF (the list of servers allowed to send email with your domain) tells receiving mailboxes which senders are genuine. If it is missing or wrong, your messages can land in spam or be refused. You can do it yourself, or ask whoever manages your domain if that is a provider or agency. It takes a few minutes of setup, then Hostinger says to allow a few hours, up to 24, for it to take effect.
To set up SPF on Hostinger, open Domains in hPanel, choose your domain, go to DNS / Nameservers and, under DNS records, add a TXT record with name @ and the value from your mail provider. For Hostinger Email, the value is v=spf1 include:_spf.mail.hostinger.com ~all. If an SPF record already exists, edit it instead of creating another.
SPF tells mailbox providers which servers may send email with your domain. Without it, or with a wrong one, your messages land in spam more often and DMARC cannot work properly.
Last verified: November 18, 2026, against Hostinger's official English help.
Before you start: list your senders
A domain must have only one SPF record, covering everything that sends mail with your address:
- your mailboxes (Hostinger Email, Google Workspace, Microsoft 365);
- your website, if it sends email (forms, online shop);
- your newsletter, invoicing or booking tools.
Each provider gives the include: to add in its help. Google Workspace, for example, uses include:_spf.google.com (see our SPF guide for Google Workspace).
These steps only work if your domain uses Hostinger's name servers. If it points to another provider, the DNS zone is managed there.
The fast route with Hostinger Email
If your domain points to Hostinger and you only use Hostinger Email, Hostinger adds the MX, SPF and DKIM records automatically. To do it or check it:
- In hPanel, open Emails, click Mailboxes next to your domain.
- Select Domain settings in the left sidebar.
- If records are missing, click Connect automatically.
Step 1: check whether an SPF record already exists
- In hPanel, choose Domains in the left sidebar, then DNS, and select your domain. (Or click Manage next to the domain, then DNS / Nameservers.)
- Stay on the DNS records tab.
- Look for a
TXTrecord whose value starts withv=spf1.
If you find one, go to Step 3. If there are two, keep one and merge their include: entries.
Step 2: add the SPF record
In the Manage DNS records card, fill in the form:
- Type:
TXT; - Name:
@(the main domain; for a subdomain such asshop, enter the subdomain name); - Value:
v=spf1 include:_spf.mail.hostinger.com ~all; - TTL: keep the default (Hostinger's SPF page says 300 or default).
- Type:
- Click Add Record.
With Hostinger Email and Google Workspace together, the value would be:
v=spf1 include:_spf.mail.hostinger.com include:_spf.google.com ~allStep 3: edit an existing SPF record
- In the records list, click the pencil icon next to the
TXTrecord that starts withv=spf1. - Add the missing
include:before~allor-all. - Click Update.
If your DNS is at another provider
If you use Hostinger Email but your DNS zone is at Cloudflare or another provider, add a TXT record on @ there with the Hostinger include:. Hostinger says to delete any existing SPF record first: in practice, merge your include: entries into a single record. For two providers, Hostinger's own example is:
v=spf1 include:_spf.mail.hostinger.com include:emailmktprovider.tld ~allStep 4: check it works
Hostinger says to allow a few hours, and up to 24 hours on its DNS help page, for changes to propagate. Then, in a terminal:
nslookup -type=TXT yourdomain.comExactly one line must start with v=spf1. Our free SPF checker also counts the DNS lookups.
From ~all to -all
~all(soft fail): an unlisted server is treated as suspicious, but the message is usually not rejected. It is the right setting until you are sure every sender is listed.-all(hard fail): an unlisted server should be rejected.
Move to -all when your DMARC reports have shown for several weeks that every legitimate sender passes SPF. To get those reports, follow our guide on setting up DMARC on Hostinger.
Known pitfalls
- Two SPF records: an old one from another provider plus the Hostinger one. Hostinger warns that several SPF records on one domain can cause delivery problems, and the standard allows only one: with two, SPF fails with an error.
- The 10-lookup limit: every
include:,a,mxorredirectcosts at least one DNS lookup, and includes often chain into others. Past 10, SPF fails. Remove services you no longer use. - The domain in the Name field: enter
@, notyourdomain.com. - An
include:afterall: everything after~allor-allis ignored. - Editing at Hostinger while the domain points elsewhere: the change has no effect.
Frequently asked questions
Is SPF enough to keep my email out of spam?
No. Also enable DKIM (Hostinger adds it automatically with its name servers) and publish DMARC. Gmail and Outlook.com require all three from senders of more than 5,000 messages a day.
How long does the change take?
Hostinger talks about a few hours, and up to 24 hours at most.
Verify it's fixed. AttackScout reads your SPF record from the internet, counts DNS lookups, spots duplicates and tells you whether your domain is ready for DMARC. Free, no account needed. Verify it's fixed
Technical details
Exact configuration. A single TXT record at the root of the domain, starting with v=spf1 and ending with an all mechanism:
v=spf1 include:<service-that-sends-your-email> ~allWhy. SPF (RFC 7208) lists the servers allowed to send email for your domain. The receiving server reads this TXT record and counts at most 10 DNS lookups (include, a, mx, exists, redirect): beyond that the result is permerror and SPF protects nothing. Two SPF records also give permerror. ~all flags without rejecting; -all makes receivers reject anything not listed.
To check it yourself. Exactly one line must start with v=spf1:
dig +short TXT your-domain.comReference: https://www.rfc-editor.org/rfc/rfc7208
Sources
Accessed November 18, 2026.
- Hostinger, How to add SPF records in hPanel: https://www.hostinger.com/support/1583673-how-to-enable-or-add-spf-records-on-hpanel/
- Hostinger, How to manage DNS records at Hostinger: https://www.hostinger.com/support/1583249-how-to-manage-dns-records-at-hostinger/
- Hostinger, Set up a domain for Hostinger email automatically: https://support.hostinger.com/en/articles/8671304-set-up-a-domain-for-hostinger-email-automatically
- IETF, RFC 7208 (SPF), section 4.6.4 on the 10-lookup limit: https://www.rfc-editor.org/rfc/rfc7208
- Google Workspace, Set up SPF: https://knowledge.workspace.google.com/admin/security/set-up-spf