How To Setup SPF And DKIM Records Correctly On Hostinger?

Your emails keep landing in the spam folder. You send important messages, but your customers never see them. This problem frustrates many Hostinger users. The fix is simpler than you think. You need two DNS records called SPF and DKIM.

These records prove that your emails are real. They tell receiving servers that you are a trusted sender. Without them, your messages look suspicious. Spam filters block them fast. Email providers like Gmail and Yahoo now demand these records.

This guide shows you the exact steps. You will learn how to add SPF and DKIM on Hostinger correctly. You will also avoid common mistakes that break email delivery. Let us start and fix your inbox problem today.

Key Takeaways

• SPF and DKIM protect your domain. SPF tells servers which mail servers can send your email. DKIM adds a digital signature that proves your message is genuine and untouched.
• Hostinger offers two setup methods. You can use the Connect automatically button if your domain uses Hostinger nameservers. You can add records manually if your domain points elsewhere.
• The default Hostinger SPF value is simple. It reads v=spf1 include:_spf.mail.hostinger.com ~all. You add it as a TXT record in your DNS zone.
• DKIM uses CNAME records on Hostinger. You find the exact values inside the Increase email deliverability tab in your hPanel email settings.
• You must keep only one SPF record. Two SPF records break email delivery. Merge multiple senders into a single line instead.
• DNS propagation takes time. Wait up to 24 hours after changes. Always test your records with a verification tool before you trust them.

What SPF And DKIM Records Actually Do

SPF stands for Sender Policy Framework. It is a TXT type DNS record. This record lists the mail servers allowed to send email for your domain. When a server receives your email, it checks this list. If your sending server matches, the email passes.

DKIM stands for DomainKeys Identified Mail. It adds a digital signature to every outgoing message. The receiving server reads this signature and confirms the email is real. It also confirms nobody changed the message in transit.

Together these records build trust. They stop spammers from faking your domain. They also push your real emails into the inbox instead of the spam folder. Both records work behind the scenes. Your readers never see them, but they feel the result.

Why Your Hostinger Emails Land In Spam

Many people set up email and assume it just works. Then their messages vanish into spam folders. The reason is almost always missing authentication records. Modern email providers treat unauthenticated mail as risky.

Gmail and Yahoo updated their rules. They now require SPF and DKIM for bulk senders. Without these records, your domain looks like a potential spammer. The receiving server has no proof that you sent the message.

This hurts your business directly. Customers miss invoices. Clients ignore your proposals. Newsletters never get read. The good news is that this problem has a clear fix.

Once you add correct SPF and DKIM records on Hostinger, your delivery rate climbs. Your domain reputation improves over weeks. Trust grows with each authenticated message you send.

Things You Need Before You Start

Preparation saves time. Gather a few items before you open your hPanel. First, you need access to your Hostinger account. Log in and confirm you can reach the dashboard.

Second, you need an active email account on your domain. The setup connects to this email service. Third, you should know where your domain points. Check if it uses Hostinger nameservers or a third party like Cloudflare or GoDaddy.

This last point matters a lot. Your method changes based on your nameservers. Domains on Hostinger nameservers get the easy automatic setup.

Domains pointing elsewhere need manual record entry. Take five minutes now to check your nameserver settings. You can find them in the Domains section of hPanel. Knowing this upfront prevents confusion later in the process.

How To Find Your Hostinger SPF And DKIM Values

Hostinger shows you the exact records you need. You do not have to guess them. Log in to your hPanel and open the Emails section. Find your email account and click the Manage button next to it.

On the left sidebar, click Connect Domain. This page holds everything. Look for two tabs. The Protect your reputation tab shows your SPF record. The Increase email deliverability tab shows your DKIM records.

These tabs display the Expected records. Hostinger compares them against your current DNS setup. The default SPF value reads v=spf1 include:_spf.mail.hostinger.com ~all.

The DKIM records appear as CNAME entries. Copy these values carefully. A single typo breaks the whole setup. Keep this page open in one browser tab while you work. You will refer back to it often during the process.

Method 1 Setup SPF And DKIM Automatically

This is the fastest method. It works only if your domain uses Hostinger nameservers. Open the Connect Domain page inside your email management area. Look for the Connect automatically button.

Click that button. Hostinger does the rest. It adds the correct SPF, DKIM, and even DMARC records to your DNS zone. You do not type anything. The system handles the values, the formatting, and the placement for you.

This method removes human error. You will not mistype a value. You will not place a record in the wrong field. Within a few clicks, your authentication is live. Wait a few hours for DNS propagation. Then return to the page and confirm all records show a green checkmark or a verified status.

Pros And Cons Of The Automatic Method

The automatic method has clear strengths. It is fast and beginner friendly. You finish in under a minute. It also reduces mistakes because Hostinger fills every value for you. You get SPF, DKIM, and DMARC in one action.

There are limits too. The button only appears for domains on Hostinger nameservers. If your domain points to Cloudflare or another DNS host, you cannot use it.

The automatic setup also gives you less control. You cannot easily customize values during the process. For most small business owners, these tradeoffs are fine. The simplicity outweighs the limited control for everyday email use.

Method 2 Add SPF Record Manually In DNS Zone

Use this method if your domain does not use Hostinger nameservers. You add the record by hand in the DNS zone editor. Open your DNS Zone Editor in hPanel or in your third party DNS host.

Create a new record. Set the type to TXT. In the Name or Host field, enter @ for your main domain. For a subdomain like shop, enter shop instead. In the value field, paste v=spf1 include:_spf.mail.hostinger.com ~all.

Set the TTL to 14400 seconds if no other value is required. Save the record. Before you add the new SPF record, delete any old SPF record. Two SPF records will break your email delivery. This is one of the most common mistakes people make. Always check for existing entries first.

Method 2 Add DKIM Records Manually

DKIM on Hostinger uses CNAME type records. Go back to the Increase email deliverability tab to find your exact values. Hostinger usually gives you two CNAME records. Each one has a unique host name and a target value.

Open your DNS Zone Editor. Create a new record and set the type to CNAME. Copy the host name from Hostinger into the Name field. Copy the matching target into the value field. Repeat this for the second DKIM record.

Accuracy is everything here. CNAME values are long and full of random characters. One wrong letter makes DKIM fail. Before adding new DKIM records, delete any old DKIM entries on the domain. Save your changes. Like SPF, these records need time to spread across the internet before they start working.

Pros And Cons Of The Manual Method

The manual method gives you full control. You can edit, merge, or fine tune every value. It works on any DNS host, including Cloudflare, GoDaddy, and Namecheap. You decide exactly what goes into each field. This flexibility suits advanced users and agencies.

The downside is the risk of error. Manual entry invites typos and wrong record types. A small mistake in a CNAME value silently breaks DKIM.

The process also takes longer and feels confusing for beginners. You must understand TXT and CNAME differences. If you are not comfortable with DNS, this method can feel stressful. Go slow and double check each entry.

How To Merge Multiple SPF Records Correctly

You must have only one SPF record per domain. This rule trips up many users. Maybe you use Hostinger Email plus a marketing tool like Mailchimp. Each one gives you an SPF value. You cannot add both as separate records.

Instead, you merge them into a single line. Take the Hostinger value v=spf1 include:_spf.mail.hostinger.com ~all. Take your other provider value, for example v=spf1 include:emailmktprovider.tld ~all.

Combine the include parts and keep one ending. The merged record looks like this: v=spf1 include:_spf.mail.hostinger.com include:emailmktprovider.tld ~all.

Notice there is only one v=spf1 at the start and one ~all at the end. Use a plain text editor like Notepad to build this line. Then paste it as your single TXT value. This keeps every sender authorized without breaking the rule.

Understanding DNS Propagation And Wait Times

Patience matters after you save your records. DNS changes do not appear instantly. They spread across servers worldwide in a process called propagation. Hostinger advises waiting up to 24 hours for full propagation.

In most cases, records work within a few hours. Sometimes they appear in minutes. The exact time depends on the TTL value and your DNS provider. A lower TTL means faster updates. The default 14400 seconds equals four hours.

Do not panic if records fail right after saving. This is normal. The internet simply has not caught up yet. Avoid making repeated changes during this window.

Each new edit resets the clock. Save your records once, then step away. Come back after a few hours and test. Your patience prevents unnecessary confusion and second guessing.

How To Test Your SPF And DKIM Records

Never assume your setup works. Always verify it. The easiest check is inside hPanel itself. Return to the Connect Domain page. If your records match, Hostinger shows them as verified. A mismatch will be flagged clearly.

You can also use free online checker tools. These tools scan your domain and report your SPF and DKIM status. They show the exact record values they detect. They also warn you about errors like duplicate SPF records.

A practical test is sending a real email. Send a message to a Gmail account. Open the email, click the three dots, and choose Show original. Gmail displays a PASS or FAIL result for both SPF and DKIM. A PASS on both means your setup is correct. This live test gives you the most confidence that everything truly works.

Common Mistakes That Break Email Authentication

Small errors cause big problems. The most frequent mistake is two SPF records on one domain. This invalidates your SPF check entirely. Always merge multiple senders into one line as shown earlier.

Another common error is wrong record types. People add DKIM as a TXT record when Hostinger needs a CNAME. Mixing these up means DKIM never works. Always match the type Hostinger specifies for each record.

Typos in long DKIM values are sneaky. A single missing character breaks the signature with no obvious warning. Forgetting to delete old records also causes conflicts.

Finally, many users edit records repeatedly during propagation and confuse themselves. Save once, wait, then test. Avoiding these five mistakes solves most authentication failures that Hostinger users face. Slow and careful work beats fast and sloppy every time.

Should You Add DMARC Too For Full Protection

SPF and DKIM are a strong start. DMARC completes the picture. DMARC stands for Domain based Message Authentication, Reporting and Conformance. It tells receiving servers what to do when SPF or DKIM fails.

You add DMARC as a TXT record. A simple starter value is v=DMARC1; p=none; placed on the host _dmarc. The p=none part only monitors at first. It collects reports without blocking anything. Later you can move to p=quarantine or p=reject for stronger control.

DMARC needs SPF and DKIM to work first. It builds on top of them. The Hostinger automatic setup adds a basic DMARC record for you. Adding DMARC boosts your domain reputation further.

It also protects you from spoofing, where attackers fake your domain to scam your contacts. Together, all three records form complete email security.

Frequently Asked Questions

How long does it take for SPF and DKIM to work on Hostinger?

Most records start working within a few hours. Hostinger advises waiting up to 24 hours for full DNS propagation. The exact time depends on your TTL value and your DNS provider. Avoid making repeated edits during this window, as each change can reset the propagation clock.

Can I have two SPF records on my Hostinger domain?

No. You must have only one SPF record per domain. Two records break your email delivery completely. If you use multiple email services, merge them into a single line. Keep one v=spf1 at the start and one ~all at the end, with all include parts in between.

Why is my DKIM record not verifying on Hostinger?

The most common cause is a typo in the CNAME value. DKIM values are long and easy to mistype. Another cause is adding DKIM as a TXT record instead of CNAME. Check that you copied the exact host and target from the Increase email deliverability tab and used the CNAME type.

Do I need DKIM if I already have SPF?

Yes, you need both. SPF checks the sending server, while DKIM verifies the message content with a digital signature. Gmail and Yahoo now require both for reliable inbox delivery. Using only one leaves gaps in your authentication and increases the chance of landing in spam.

What is the default Hostinger SPF record value?

The default value is v=spf1 include:_spf.mail.hostinger.com ~all. You add it as a TXT record with @ as the host for your main domain. For subdomains, use the subdomain name as the host instead. You can always confirm the current value inside the Protect your reputation tab in hPanel.

Can I set up SPF and DKIM if my domain uses Cloudflare?

Yes. You cannot use the automatic button, but you can add records manually. Copy the SPF and DKIM values from your Hostinger email settings. Then log in to Cloudflare and add them in the DNS section. Add SPF as a TXT record and DKIM as CNAME records, then wait for propagation.