How to Warm Up Hostinger Email for Cold Outreach

Warm up Hostinger Email for at least 14 days on an existing domain, using imap.hostinger.com:993 SSL and smtp.hostinger.com:465 SSL. If you send cold outreach before the mailbox has history, you increase spam placement and throttling risk. This guide gives the connection settings, DNS checks, 14-day ramp, error fixes and readiness checks.

Hostinger Email connects to BobWork Email Warm-up through standard IMAP and SMTP, not OAuth. In BobWork, use the 'Other IMAP + SMTP' route, enter the Hostinger servers, and let the mailbox build from 3 to 30 warm-up emails per day. For related planning, use the email warm-up schedule and the new-domain warm-up plan.

What affects Hostinger deliverability?

Hostinger is the mailbox provider in this setup. Gmail, Yahoo, Microsoft and other receiving providers decide whether your messages land in the inbox, spam folder or get blocked.

Those receivers look for authentication, stable volume and low negative feedback. A new mailbox that sends hundreds of emails on day one looks riskier than a mailbox that builds a small, consistent pattern.

Google asks senders to authenticate mail and keep spam complaints low. For Gmail, keep the complaint rate under 0.1% and never let it reach 0.3%. Google publishes those requirements in its email sender guidelines.

Yahoo requires SPF and DKIM, DMARC at least at p=none, aligned authentication, one-click unsubscribe for bulk senders and a spam rate under 0.3%. Yahoo lists those rules in its sender best practices.

Microsoft applies specific requirements to domains sending more than 5,000 emails per day to Outlook.com and Hotmail consumer mailboxes. Those include SPF, DKIM and DMARC with alignment. Microsoft explains the rule in its high-volume sender requirements.

Even if your volume is far below those bulk thresholds, follow the same basics. A small sender with broken DNS still looks risky.

How do you warm up Hostinger email?

Use Hostinger Email with BobWork through the generic IMAP and SMTP option. IMAP lets the warm-up engine see warm-up replies and spam placement. SMTP lets it send warm-up messages from your mailbox.

Use these settings first. If Hostinger changes its current settings, follow Hostinger’s current mailbox help before changing ports or encryption.

Before connecting any tool, sign in to Hostinger webmail. Send one normal test email to another inbox, then reply to it. This proves the mailbox can send and receive before warm-up starts.

Add the mailbox

Open BobWork Email Warm-up and add a mailbox. Choose 'Other IMAP + SMTP' as the provider type.

Use the full email address as the username. For most IMAP and SMTP providers, the username is the whole address, not only the part before the @ sign.

Enter the mailbox password. Do not use your Hostinger account password if it is different from the mailbox password.

Enter IMAP

Set the IMAP host to imap.hostinger.com.

Set the IMAP port to 993.

Set security to SSL.

Save and test the receiving connection. If it fails, check the password first. Then confirm the mailbox exists and can receive mail in Hostinger webmail.

Enter SMTP

Set the SMTP host to smtp.hostinger.com.

Set the SMTP port to 465.

Set security to SSL.

If port 465 fails, try port 587 with STARTTLS. Do not mix the encryption types. Port 465 uses SSL. Port 587 uses STARTTLS.

Start the ramp

After the mailbox connects, leave the default ramp on. BobWork starts at 3 warm-up emails per day, adds 2 per day, and caps at 30 per day. The cap is editable per mailbox, up to 100, but cold outreach mailboxes rarely need that much warm-up.

Sends are spread between 09:00 and 18:00 in the mailbox’s own time zone. Weekends run at 30% of weekday volume. About 40% of received warm-up mail gets a reply, and threads end after three messages.

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. Private pool mode needs at least two mailboxes.

Which DNS records must pass?

Do DNS before judging warm-up results. A mailbox with missing SPF, missing DKIM or weak DMARC can connect and send, but receiving providers have less reason to trust it.

For Hostinger Email, copy the exact DNS values from Hostinger’s domain or email setup screen. Do not copy values from another domain, another provider or an old workspace.

SPF should have one TXT record only. Multiple SPF records can cause SPF to fail. If you send through another service too, merge the includes into one SPF record instead of publishing a second SPF record.

DKIM proves the message was authorised by the sending service. Hostinger should show the selector and value to publish. If the selector is wrong, the record will look missing even when a DKIM record exists elsewhere.

DMARC tells receivers what to do when SPF and DKIM alignment fail. Start with p=none while you verify mail flow. Move to a stricter policy only after your regular senders pass authentication.

If you later send through a cold-email platform, CRM or SMTP relay, repeat the DNS check for that sender. Warm-up helps mailbox history. It does not fix authentication for a separate sending route.

What 14-day ramp should you use?

For an existing domain with correct DNS, use the 14-day ramp below. It follows BobWork’s default engine: 3 emails on day one, then +2 per day until the 30-per-day cap.

Use three to four weeks for a new Hostinger domain, a domain that recently changed email provider, or a mailbox with recent spam placement.

The engine reaches 30 per day on day 15. You do not need to push higher just because the cap allows it. During active campaigns, keep warm-up at 10–15 per day and keep real outreach modest.

For most cold outreach, stay around 30–50 real emails per day per mailbox. If you need more volume, add mailboxes and domains instead of forcing one Hostinger mailbox to carry everything. The cold-email volume guide explains the safer split.

If the warm-up spam rate goes above 5%, pause that mailbox for a few days. Fix authentication, reduce real sending and review your copy before restarting.

How should you fix Hostinger errors?

Most Hostinger warm-up failures are connection errors, DNS mistakes or too much outbound volume too soon. Fix them in that order.

A login error usually means the password is wrong, the username is incomplete, or the mailbox is not active. Use the full email address as the username. Then sign in to Hostinger webmail with the same password before testing again.

An IMAP timeout usually means the server, port or encryption is wrong. Use imap.hostinger.com, port 993 and SSL. Do not use port 143 unless Hostinger’s current help tells you to.

An SMTP error on port 465 often means SSL is not selected. Port 465 should use SSL. If you switch to port 587, change security to STARTTLS.

A certificate error can appear when the wrong mail host is used. For Hostinger Email, use imap.hostinger.com and smtp.hostinger.com from the verified settings. Do not replace them with mail.yourdomain.com unless Hostinger tells you that is correct for your mailbox.

A DKIM warning usually means the selector or TXT value is wrong. Copy the selector from Hostinger, then test it with the DKIM checker. DNS can also take time to publish, so recheck after propagation.

A DMARC warning usually means the record is missing, published at the wrong name, or malformed. The record name should be _dmarc on the sending domain. Use the DMARC checker to confirm receivers can see it.

Spam placement is different from a connection failure. If warm-up mail lands in spam, BobWork moves its own warm-up mail to the inbox, marks it read, labels it 'Warm-up' and archives it after 24 hours. It only touches mail carrying the engine’s hidden header. Real mail is never read, moved or answered.

If your real cold emails still land in spam, warm-up is only one part of the fix. Check list quality, targeting, copy, links, unsubscribe handling and sending volume. The guide to why emails go to spam covers those causes.

What should you verify now?

Use this checklist before sending cold outreach from Hostinger Email. Do not skip the verification column. A record that exists in your DNS editor is not always visible to receiving mail servers.

If you manage several Hostinger mailboxes, use the warm-up schedule generator to stagger launch dates. Staggering keeps each mailbox’s first outbound days small.

When is Hostinger ready?

A Hostinger mailbox is ready for cautious outbound when it has warmed for at least 14 days, has a 7-day warm-up spam rate at or below 3%, and has received at least 30 warm-up emails. Those are the BobWork ready criteria.

Start small after that. Send a handful of real cold emails first, then increase only if replies, bounces and spam placement stay healthy. Keep warm-up running at 10–15 per day during campaigns.

For a new domain, give the mailbox three to four weeks before normal outreach. A clean 14-day warm-up is a minimum for existing domains, not a shortcut for brand-new infrastructure.

BobWork Email Warm-up is free for up to 10 mailboxes, with no credit card and no time limit. Hostinger Email uses the standard IMAP/SMTP route, so you can connect it with the settings above, monitor SPF, DKIM and DMARC, and wait for the ready signal before scaling outreach.

Frequently asked questions