How to set up SPF on Hostinger

Add an SPF record in your Hostinger DNS so the world knows which servers may send email using your domain.

Why this matters to your business

SPF (Sender Policy Framework) is a short note in your domain’s DNS that lists which mail servers are allowed to send email “from” your domain. Without it, scammers can forge your address to send invoices, payment requests or fake quotes to your customers and suppliers — and your own legitimate email is more likely to land in spam. Setting SPF up is free, takes a few minutes, and is one of the strongest, cheapest things you can do to protect your name and keep your email getting delivered.

Before you start: is Hostinger actually running your DNS?

This is the single most common reason these changes “do nothing.” A DNS record only takes effect if Hostinger is where your domain’s nameservers point.

If you registered the domain with Hostinger and use its DNS, you’re in the right place.
If your domain points at someone else’s nameservers (for example Cloudflare, another web host, or your email provider), then the SPF record must be added there, not at Hostinger. Adding it at Hostinger will have no effect.

In hPanel, open Domains and check the DNS / Nameservers area for your domain. If it shows Hostinger’s own nameservers, continue below. If it shows another company’s nameservers, go add SPF in that company’s DNS instead.

What you’ll add

A single TXT record that lists your senders. The exact value depends on who sends your email. A common example for a domain that sends only through Microsoft 365 is:

v=spf1 include:spf.protection.outlook.com -all

For Google Workspace it’s usually:

v=spf1 include:_spf.google.com ~all

Use the SPF value your email provider tells you to use. You should have only one SPF (TXT starting with v=spf1) record per domain — if you already have one, edit that one rather than adding a second.

Steps in Hostinger

Sign in to Hostinger and open hPanel.
Go to Domains, select your domain, and open DNS / Nameservers (the DNS Zone editor).
Look at the Manage DNS records section. Hostinger may already include a default SPF record — if one exists, edit it instead of adding a new one.
To add a record, set Type to TXT.
In the Name (sometimes called Host) field, enter @. The @ means “the domain itself.” Do not put your full domain name here.
In the TXT value (sometimes called Content or Value) field, paste your SPF string, e.g. v=spf1 include:spf.protection.outlook.com -all.
Leave TTL at the default.
Click Add Record (or Save).

Hostinger quirks people get wrong

Check for a default SPF first. Hostinger often pre-populates a basic SPF record on its own zones. Ending up with two v=spf1 records breaks SPF entirely — edit the existing one rather than adding a second.
No quotes. Type the SPF value plain. Do not wrap it in double quotes — Hostinger handles the quoting itself, and pasting a quoted value can result in a broken record.
@ for the name, not your domain. Putting the full domain in the Name field creates the record at the wrong place.
Only one SPF record. If you add a second sender (say you start using a newsletter tool as well), combine them into one record using extra include: entries — don’t create a second TXT.
Changes aren’t instant. DNS can take from a few minutes up to a couple of hours to update everywhere.

Verify it worked

Once saved, confirm the record is live and correct with the free check on Defaults.Exposed. Enter your domain and it’ll tell you in plain language whether your SPF is set up properly. Your data is processed in the EU.

Done? Check your domain free to confirm it worked — and see your full grade across all 34 checks.