Hostinger Email Going to Spam: Fix DNS, SMTP, Volume

Hostinger email going to spam is usually fixed by checking four things first: SPF, DKIM, DMARC, and sending volume. If you ignore them, Gmail, Yahoo, and Microsoft may distrust the domain, not just one mailbox. This guide gives you the exact Hostinger settings, DNS checks, warm-up rules, and proof steps.

Use this as a repair page, not a theory page. If you only need connection settings, keep the Hostinger Email warm-up guide open beside it. Before you send more mail, check the domain with the free SPF checker, DKIM checker, and DMARC checker.

How should you diagnose spam placement?

Do not change five things at once. Match the symptom to the most likely cause, run the quick check, then fix the highest-risk item first.

If the whole domain is affected, start with DNS. If only one mailbox is affected, inspect that mailbox’s recent sends, content, and recipient list.

Which fixes stop Hostinger email going to spam?

Most spam problems sit in three buckets: authentication, reputation, or behaviour. Fix them in that order.

Authentication proves Hostinger is allowed to send for your domain. Reputation is how receivers judge past mail from the domain and mailbox. Behaviour is what you send, how fast you send it, and who receives it.

Keep these numbers on one screen while you work.

Google’s sender guidance says to authenticate mail, use DMARC for direct mail, and keep spam complaints low. Google says to stay under 0.1% and avoid ever reaching 0.3%. Read the primary source in Google’s email sender guidelines.

Yahoo requires SPF and DKIM, DMARC at least at p=none, alignment with the From domain, and spam rates under 0.3%. Check the current requirements in Yahoo’s sender best practices.

Are SPF, DKIM, and DMARC correct?

DNS mistakes can send good mail to spam. They also affect every mailbox on the domain, including mailboxes you have not used yet.

Check SPF first

SPF is a TXT record on your root domain. It lists the services allowed to send mail for that domain.

For Hostinger Email, copy the current SPF value from Hostinger hPanel. Do not use a guessed include value from another article. Providers can change include hosts, and different Hostinger products can use different records.

Use this shape:

You must have one SPF TXT record, not two. If you send from Hostinger plus another platform, merge both senders into one SPF record.

A broken setup looks like this:

Merge them into one record using the current include values from each sender. Then test the domain with the free SPF checker. If it shows more than one SPF record, fix that before you send again.

Enable and verify DKIM

DKIM signs outgoing mail. It tells Gmail, Yahoo, Microsoft, and other receivers that the message was authorised and not changed after sending.

In Hostinger, enable DKIM for the domain and copy the exact DNS record shown in hPanel. DKIM selectors vary, so do not guess the selector. Publish the TXT record at the exact host name Hostinger gives you.

Use this format:

Wait for DNS propagation, then check it with the free DKIM checker. If the checker cannot find the selector, confirm the DNS host did not duplicate the domain name.

Some DNS panels append the domain automatically. If Hostinger gives you a full host name and your DNS host appends the domain again, the record is published in the wrong place.

Add DMARC at p=none

DMARC tells receivers what to do when SPF or DKIM does not align with the visible From domain. It also gives you a policy layer above SPF and DKIM.

Start with a monitoring policy while you fix delivery:

If you want reports, add a reporting address you control:

v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com

Do not move to p=quarantine or p=reject until every legitimate sender passes alignment. That includes Hostinger, cold email tools, newsletter tools, CRMs, and helpdesks.

Check the result with the free DMARC checker. If there is no visible DMARC record, keep the policy at p=none until DNS has propagated.

What should you fix next?

Once DNS is correct, work through SMTP, content, volume, lists, mail streams, and blacklist checks.

Confirm Hostinger SMTP

Wrong SMTP settings can cause connection failures, duplicate sending attempts, or mail sent through a route you did not intend.

Use these Hostinger Email settings:

If you connect Hostinger Email to BobWork Email Warm-up, use the Other IMAP + SMTP route. The mailbox still sends from Hostinger. The tool uses IMAP and SMTP to warm the mailbox and measure placement.

Remove risky content

Receivers do not judge authentication alone. They also inspect message content and user reaction.

For a clean test, send a plain text email to a real contact. Remove links, images, attachments, open tracking, link tracking, shortened URLs, and heavy formatting. Use a normal first-name greeting and a specific reason for sending.

If the plain text version reaches the inbox but the campaign version lands in spam, the issue is content or tracking. Add elements back one at a time.

For cold outreach, keep the first email short. Use a real business reason. Make opting out easy.

Lower mailbox volume

If DNS is correct and content is clean, sending volume is the next likely cause.

A new or quiet mailbox should not jump to high outbound volume. For cold outreach, a typical safe range is 30–50 real outbound emails per mailbox per day after warm-up. If you need more volume, add mailboxes and domains instead of pushing one inbox harder.

Use the guide on how many cold emails per day is safe if you are planning Hostinger campaigns. If the domain is new, use the new domain warm-up guide and ramp for 2–3 weeks.

Clean the recipient list

Bad lists create spam placement even when the sending setup is correct.

Remove old contacts, scraped addresses, purchased lists, rented lists, and contacts with no clear business fit. Remove role accounts when possible, such as info@, sales@, support@, and admin@. They can be useful in some contexts, but they often create weaker engagement in cold campaigns.

High bounces and complaints damage both the mailbox and the domain. If you send commercial or bulk mail, include a working unsubscribe option. Yahoo says bulk senders should support one-click unsubscribe and honour unsubscribes within 2 days.

Separate mail streams

Do not send newsletters, product announcements, cold outbound, receipts, and support replies from the same new mailbox.

Each stream creates a different reputation pattern. Newsletters may include old subscribers. Cold outreach may get lower engagement. Support replies usually get better engagement. Mixing them makes diagnosis harder.

If Hostinger is used for human business email, protect those mailboxes. Use separate mailboxes, and often separate domains, for cold outreach. This guide on newsletter versus cold email providers explains the split.

Check blacklists carefully

A blacklist result can matter, but it is not always the root cause. Some lists have little effect. Others affect specific receivers or corporate filters.

Use the email blacklist checker after you verify SPF, DKIM, and DMARC. If you see a listing, read that list’s own removal process. Do not pay random removal services.

If one test tool says blacklisted but real mail is improving, do not panic. Focus on authentication, complaints, bounces, and engagement first.

When should you use warm-up?

Warm-up helps when a mailbox needs steady, normal-looking email activity. It is not a repair tool for every spam problem.

BobWork Email Warm-up starts at 3 emails per day, adds 2 per day, and caps at 30 per day by default. The cap is editable per mailbox, up to 100. Weekends run at 30%. Sends are spread from 09:00 to 18:00 in the mailbox’s own time zone.

About 40% of warm-up mail gets a reply, and threads end after 3 messages. Warm-up mail found in Spam is moved to Inbox, marked read, labelled Warm-up, and archived after 24 hours. Only mail carrying the engine’s own hidden header is touched. Real mail is never read, moved, or answered.

The free pool does this step automatically through a shared warm-up network, or a private pool per account if you prefer. One mailbox is enough to start in the shared network. A private pool needs at least two mailboxes.

Keep warm-up running during campaigns, but do not use it as permission to send too much. We recommend keeping warm-up at 10–15 per day during active campaigns and pausing a mailbox for a few days if its warm-up spam rate rises above 5%.

A mailbox is ready for outbound in BobWork after 7 or more days warming, a 7-day spam rate of 10% or less, and at least 30 warm-up emails received. For the limits of the method, read what email warm-up can and cannot fix.

What should you do now?

Do the fastest, highest-impact checks first. This order avoids wasting warm-up on a broken domain.

If you manage several Hostinger mailboxes, do not fix one and forget the rest. Check the domain once, then check each mailbox’s behaviour separately.

For bulk onboarding in BobWork, go to Add mailbox → Many mailboxes: upload a CSV. Use rows of email,app_password,name. For Hostinger and other custom domains, include the IMAP host when needed. Failed rows are listed with the reason, and already-connected rows are skipped.

How do you prove the fix worked?

You need proof from receiving behaviour, not only a green DNS screen.

Start with a small test group. Include one Gmail address, one Yahoo address if relevant, and one business inbox you control. Send the same plain text message from the affected Hostinger mailbox. Ask recipients to check Inbox, Promotions, Updates, and Spam.

Then watch these signals for at least 7 days:

BobWork measures spam landings directly in receiving mailboxes. It does not use third-party seed lists. That makes the warm-up spam rate useful for trend checks after a DNS, content, or volume fix.

Do not declare victory after one inbox test. Spam filtering is recipient-specific. A mailbox can reach one corporate inbox and still struggle at Gmail or Yahoo.

Use a staged restart:

If spam placement returns, roll back the last change. Usually that means a new template, a larger list, a tracking domain, or a sudden volume increase.

For a practical setup, connect the Hostinger mailbox with IMAP and SMTP, verify DNS, and let warm-up run while real sending stays low. BobWork Email Warm-up is free for up to 10 mailboxes, with no credit card and no time limit. It supports Hostinger through Other IMAP + SMTP. Outlook and Microsoft 365 are not supported yet.

Frequently asked questions