SPF Setup for Hostinger Email and DNS

December 10, 2025 • InboxGreenEmail Team

🚨 DKIM issues can silently kill replies.

If opens dropped, replies disappeared, or bounces increased, treat it as an incident. Run the scan and get a fix path.

No signup required. Works on any domain.

search Run a Free Domain Check notifications_active Monitor my domain

SPF Setup for Hostinger Email and DNS

As a SaaS founder or marketer, you know that email deliverability is crucial. You can have the best product in the world, but if your emails land in the spam folder, you’re not going to reach your audience. One of the key players in ensuring your emails get delivered is the Sender Policy Framework, or SPF. If you’re using Hostinger for your email and DNS, setting up SPF correctly is essential. Let's dive into how to do this effectively.

Understanding the Problem

When you send an email, the receiving server checks if the sending server is authorized to send emails on behalf of your domain. This is where SPF comes in. Without a properly configured SPF record, your emails may be flagged as suspicious or even blocked entirely.

Imagine this scenario. You’ve just launched a new feature and sent out an email blast. You eagerly check your email metrics, only to find that your open rates are dismal. After some digging, you discover that your emails are being marked as spam due to a missing or incorrect SPF record. Frustrating, right?

Step-by-Step SPF Setup for Hostinger

Let’s get to the nitty-gritty of setting up SPF for your Hostinger email. Follow these steps carefully to ensure you configure it correctly.

Step 1: Access Your DNS Settings

First, log in to your Hostinger account. Navigate to the DNS Zone Editor. This is where you’ll manage your DNS records. If you’re not sure how to get there, here’s a quick path:

  1. Log in to your Hostinger account.
  2. Go to the "Domains" section.
  3. Select the domain you want to configure.
  4. Click on "DNS Zone Editor."

Step 2: Check for Existing SPF Records

Before adding a new SPF record, check if one already exists. Look for a TXT record that starts with v=spf1. If you find one, you’ll need to modify it instead of creating a new record. If there is no existing SPF record, you can proceed to the next step.

Step 3: Create or Modify Your SPF Record

To create a new SPF record, you need to add a TXT record. Here’s a simple example of what your SPF record might look like:

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

This record allows Outlook to send emails on behalf of your domain. If you’re using other services, like Mailchimp or SendGrid, you’ll need to include their SPF records as well. Here’s a more complex example:

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

Make sure to replace the included domains with the ones you actually use. The -all at the end indicates that any server not listed should be rejected. If you want to be less strict, you can use ~all instead, which allows soft fails.

Step 4: Save Your Changes

After entering your SPF record, save the changes. DNS changes can take some time to propagate, so be patient. It might take anywhere from a few minutes to a couple of hours.

Step 5: Verify Your SPF Record

Once you've set up your SPF record, it’s time to verify it. Use the InboxGreen checker to ensure your SPF record is correctly configured. This tool will help you identify any issues that might affect your email deliverability.

Common Gotchas

Here are a few common pitfalls to watch out for:

  • Multiple SPF Records: You can only have one SPF record per domain. If you create multiple records, it can lead to delivery issues.
  • Too Many Includes: Each include: statement counts towards the DNS lookup limit. You can have a maximum of 10 DNS lookups for SPF, so choose wisely.
  • Not Updating After Changes: If you change your email service provider, make sure to update your SPF record accordingly.

DKIM and DMARC: The Dynamic Duo

While SPF is vital, it’s not the only player in the game. You should also implement DKIM and DMARC for better deliverability and security.

Setting Up DKIM

DKIM adds a digital signature to your emails, allowing the receiving server to verify that the email has not been altered. Hostinger usually provides DKIM settings in the email configuration section. Look for options to enable DKIM and follow the instructions provided.

Implementing DMARC

DMARC builds on SPF and DKIM by providing instructions on how to handle emails that fail authentication checks. You can create a DMARC record in the same way you did for SPF. Here’s an example:

v=DMARC1; p=none; rua=mailto:[email protected]

This record tells receiving servers to send reports to you without rejecting emails. As you get comfortable, you can change the policy from none to quarantine or reject for stricter enforcement.

What to Do Next

Now that you’ve set up SPF, DKIM, and DMARC, it’s time to monitor your email deliverability. Use the InboxGreen checker to keep an eye on your records and ensure everything is functioning as expected. Regular checks can help you catch issues before they impact your campaigns.

For more advanced setups, consider using our SPF generator and DMARC generator to simplify the process. If you have questions or need assistance, check out our API documentation or visit our pricing page for more information on our services.

Remember, email deliverability is not a one-time task. It requires ongoing attention. Stay proactive, and your emails will land where they belong - in the inbox.

Free Deliverability Scan

Check SPF, DKIM, DMARC and List-Unsubscribe for your domain in seconds.