Hostinger includes email with its WordPress plans, but on plans bought since April 2025 the mailboxes are a free trial of up to a year rather than a permanent bundle: 2 per website on the 3-site plan and unlimited on the higher plans, each with 1 GB of storage, webmail, forwarding, and access from desktop and phone mail apps. Keeping them after the trial means paying for Hostinger’s Business Email. WordPress’s own outbound mail leaves through PHP’s mail() function on the local server, unsigned by default and capped at 10 messages a minute and 100 a day, which is the same starting position as most generic shared hosts and the same gap the SMTP plugins exist to fill. Hostinger documents the SMTP host (smtp.hostinger.com:465) for routing WordPress through a mailbox, and the standard submission ports are open for a third-party relay swap. Mailbox sending caps are 100 messages per mailbox per day on the trial and 1,000 or 3,000 per day on paid Business Email. The marketing trade-off is that intro prices ($2.49/month on the 3-site plan) require a 48-month commitment and renew at $10.99/month or more.
Plans renew at $10.99/month (3 sites), $16.99/month (unlimited sites, the plan Hostinger used to sell as Business), and $25.99/month (entry cloud plan), billed annually or longer. Hostinger sits in the budget shared-hosting tier, well below managed-WordPress hosts like Kinsta and WP Engine, and roughly aligned with Bluehost on renewal pricing.
Email on Hostinger
How wp_mail works by default
A fresh WordPress install on Hostinger sends mail through PHP’s mail() function, which hands off to the local server’s sendmail configuration. No SMTP plugin is required to get the default path running; password resets, WooCommerce order confirmations, and comment notifications all leave through this path on a brand-new install, up to the server-sending cap covered under Sending limits.
The gap on the default path is DKIM (the cryptographic signature receiving servers use to confirm a message came from your domain). Hostinger does not sign PHP mail() traffic out of the box. Its hPanel does support SPF and DKIM at the DNS layer (the
auto-configuration option publishes both when the domain uses Hostinger nameservers), but those records are for the bundled mailbox path, not for PHP mail() going out via the local server. Most operators close this gap by installing an SMTP plugin and pointing it at one of two routes: Hostinger’s own mailbox SMTP (smtp.hostinger.com:465), which signs with the DKIM Hostinger auto-publishes, or a third-party relay that brings its own DKIM. Hostinger’s
own WordPress SMTP tutorial walks through both.
Outbound SMTP port status
| Port | Status | Protocol |
|---|---|---|
| 25 | Open | SMTP (legacy); Hostinger |
| 465 | Open | SMTPS (implicit TLS); the port Hostinger’s own tutorial uses for the bundled smtp.hostinger.com mailbox |
| 587 | Open | SMTP with STARTTLS; the standard submission port for external relays |
| 2525 | Open | SMTP (alternate) |
| 993 | Open | IMAPS (incoming, bundled mailboxes) |
| 995 | Open | POP3S (incoming, bundled mailboxes) |
Hostinger does not publish a port-status table of its own. Port 465 is the one its WordPress SMTP tutorial uses, with SSL, for the bundled mailbox path. The remaining outbound rows are based on Hostinger’s VPS port-25 policy applied to the shared infrastructure and on the same plugins (WP Mail SMTP, FluentSMTP, Post SMTP) routinely connecting from Hostinger sites to Postmark and SMTP2GO without trouble.
Sending limits
| Tier | Daily limit (per mailbox) |
|---|---|
| Free trial included with hosting (1 GB) | 100 in / 100 out |
| Paid Business Email, 5 GB plan | 1,000 in / 1,000 out |
| Paid Business Email, 20 GB and 50 GB plans | 3,000 in / 3,000 out |
Hostinger’s
documented policy treats the daily limit as per-mailbox in each direction; a mailbox on the 5 GB plan sending 1,000 messages and receiving 1,000 in a day is at its ceiling. The trial’s 100-a-day-per-mailbox limit is generous enough for one operator’s personal account but tight for any per-mailbox transactional pattern (orders@, noreply@, contact-form senders).
WordPress’s wp_mail() does not consume mailbox quota when it leaves through PHP’s mail() function on the local server, because the local sendmail handoff bypasses the Business Email mail server entirely. That path has its own ceiling: Hostinger’s
hosting-plan limits cap server-based sending at 10 messages a minute and 100 a day on its web, cloud, and agency plans, counted over a rolling 24 hours. Past the cap, sending by that method is switched off until older messages age out of the window. A WooCommerce store or a busy contact form can hit 100 a day without trying, and Hostinger’s own advice on the same page is to move to SMTP. Sites that route wp_mail() through an SMTP plugin connected to smtp.hostinger.com:465 count against the mailbox quota instead.
Mailboxes, forwarding, DNS
Mailboxes that come with a hosting plan are a
Business Email free trial, and the count depends on when the plan was bought. Plans sold today include 2 mailboxes per website on the 3-site plan and unlimited mailboxes on the unlimited-sites and cloud plans; plans bought before April 24, 2025 keep the old allowance of up to 100 (
plan versions). The trial runs for the hosting plan’s billing period, up to one year, and ends early if the hosting plan expires. Each trial mailbox gets 1 GB of storage, IMAP, POP3, and SMTP access for mail clients, and webmail through hPanel. After the trial, the paid Business Email plans run 5 GB, 20 GB, or 50 GB per mailbox. Forwarding rules are configured in the same hPanel section; no separate forwarding service is needed.
Hostinger manages DNS through hPanel for any domain whose nameservers point at Hostinger. The standard A, CNAME, MX, and TXT record types are editable in the dashboard, and the “Connect automatically” option publishes the MX, SPF, and DKIM records for the mailbox in a single step. If DNS lives elsewhere (Cloudflare is the common one), the records are added manually at that provider, and the auto-publish convenience disappears.
Authentication (SPF, DKIM, DMARC)
Hostinger auto-publishes SPF and DKIM when the domain uses Hostinger nameservers and the operator clicks “Connect automatically.” The
SPF record is v=spf1 include:_spf.mail.hostinger.com ~all, and DKIM is three CNAME records (hostingermail-a, -b, and -c._domainkey) that cover the mailbox path. Domains set up under the older include:spf.mx.hostinger.com still pass, because that name now points at the new one, but it costs an extra DNS lookup. On a domain connected automatically, mail leaving through smtp.hostinger.com is already SPF-aligned and DKIM-signed at the mailbox layer, which is the platform’s main authentication asset.
What the auto-publish does not cover is the PHP mail() path on the default wp_mail() route. Mail leaving the local server through sendmail uses neither the mailbox SMTP nor the DKIM key published for the bundled mailbox. That path is unsigned, and the SPF check it relies on depends on the IP address of the shared server rather than the mailbox SPF record. The standard fix is to install an SMTP plugin and route WordPress through smtp.hostinger.com:465 so that wp_mail() traffic inherits both the SPF alignment and the DKIM signature the platform already publishes for the mailbox.
SPF (the DNS record listing which servers are authorised to send mail under the domain) can need hand-merging when a third-party relay is also in play. A site that signs through smtp.hostinger.com and uses a relay that sends with the root domain as its envelope sender needs the includes for both. Postmark and SMTP2GO document SPF on provider-managed return paths, so their default sending setup needs no SPF include on the root domain. Amazon SES uses a subdomain of amazonses.com as its default MAIL FROM domain, so SPF is handled by SES. If you configure a custom MAIL FROM domain in SES, publish the MX and SPF TXT records AWS specifies on that domain. Mailgun’s SPF record belongs on its configured sending domain; Mailgun recommends using a subdomain. Hostinger’s own guidance on the
auto-config flow covers the bundled mailbox alone.
DMARC is treated as the operator’s choice. The automatic setup does not add a DMARC record; Hostinger’s
DMARC guide has the operator add a _dmarc TXT record by hand, starting from p=none. Adding a rua= reporting address to that policy is the conservative first step; tightening belongs after aggregate reports confirm clean alignment.
When Hostinger’s include:_spf.mail.hostinger.com needs to sit alongside a third-party relay’s include, the SPF merger folds the two together and counts the DNS lookups against RFC 7208’s ten-lookup ceiling. Once the record is published, the DNS auth checker reads how the domain’s SPF, the Hostinger-published DKIM, and DMARC resolve from the receiver’s perspective, so a stale nameserver or a missed include shows up before real traffic does.
What Hostinger does not provide
- DKIM on the PHP
mail()path. The defaultwp_mail()route is unsigned. Routing WordPress throughsmtp.hostinger.com:465via an SMTP plugin inherits the auto-published DKIM; a third-party relay brings its own. Either fixes the gap. - A dedicated sending IP. Outbound mail shares the hosting server’s IP with other Hostinger customers on shared plans, and the bundled mailbox path shares Hostinger’s own mail-server IP across tenants. Deliverability isolation requires a relay with a dedicated-IP add-on (Postmark once sending reaches 300,000 emails a month; Mailgun on its 100,000-a-month plans and up).
- Per-message delivery logs, bounce tracking, and webhook events. Hostinger surfaces no log of what was sent, what bounced, or what hit spam. Relays with delivery webhooks (Postmark, Mailgun, SMTP2GO) are the way to get that visibility.
- Marketing or bulk sending allowance. Bundled mailbox traffic is for human-to-human and transactional use; broadcast traffic belongs on a dedicated marketing platform (Mailchimp, MailerLite, ConvertKit).
- A custom return-path domain on the mailbox path. The bundled Hostinger mailbox uses the mailbox address as both header and envelope From; on the PHP
mail()path the envelope is whatever the local sendmail config sets. Third-party relays (Postmark, Mailgun) expose a configurable return-path domain.
When a third-party relay is needed
Hostinger’s bundled mail and the smtp.hostinger.com route, used together, are enough for most low-traffic WordPress sites. A personal site, a small WooCommerce store running a handful of orders a day, a membership site with a few hundred active users: all of these sit comfortably inside the 100-a-day-per-mailbox limit with the SMTP plugin pointed at a Hostinger mailbox.
A dedicated relay is the right call when:
- Mailbox volume crosses the daily cap. A
noreply@ororders@mailbox approaching 100 outbound messages a day on the trial, or 1,000 on the 5 GB Business Email plan, should move WordPress to a relay that does not share the mailbox quota. SMTP2GO is the cheapest credible option for low volumes; Postmark is the cleanest fit for transactional sites under 100,000 a month; Mailgun is where higher volumes make economic sense. - A missed email has a real cost. Sites whose business depends on order confirmations and password resets landing in the inbox should not rely on a shared-IP host’s deliverability alone. Layering a relay with bounce webhooks, suppression lists, and event logs is how a site catches and reacts to failed delivery.
- Delivery visibility is required. Per-message delivery, bounce, and complaint events arrive as webhooks from Postmark, Mailgun, and SMTP2GO, with searchable logs and aggregate dashboards. Hostinger’s bundled path surfaces none of this.
- The site needs marketing or newsletter sending. Bundled mailboxes are not the right route. A marketing platform (Mailchimp, ConvertKit, MailerLite) handles the campaign side; a dedicated transactional relay handles the transactional side.
Because the standard submission ports are open, an SMTP plugin connects to any of these providers without an API-only constraint. SMTP is simpler to set up; the providers’ HTTP APIs hold up better when DNS or network changes shift things around. Both work.
Going the other way, sites following the WordPress without the plugin minimum-stack pattern can use Hostinger’s bundled mailbox as the WordPress sender directly and skip the SMTP plugin; the host’s relay is what makes that no-plugin slice viable here.
Verdict
Hostinger is the right pick for budget-conscious operators who want WordPress hosting and bundled mailboxes from one provider, are happy to wire WordPress through an SMTP plugin to inherit the auto-published DKIM, and are willing to plan for the higher renewal prices. The intro pricing genuinely is cheap ($2.49/month on the 3-site plan for a 48-month commitment) and the auto-publish DKIM is more than most budget hosts ship. The trade-offs are the renewal step at year four ($10.99/month for 3 sites, $16.99/month for unlimited sites, $25.99/month for the entry cloud plan), mailboxes that turn into a paid add-on when the trial ends, and two 100-a-day caps: one on the unsigned PHP mail() default path, and one per trial mailbox that any per-mailbox transactional flow will run into. For the WordPress email setup that supplements Hostinger’s default path, see how to configure WordPress email.
Corrections
- 2026-11-02: an earlier version said every Hostinger WordPress plan includes up to 100 free mailboxes per domain. That allowance applies only to plans bought before April 24, 2025; plans sold today include 2 mailboxes per website on the 3-site plan and unlimited mailboxes on the higher plans, as a free trial that lasts up to a year.
- 2026-11-12: an earlier version said a site using a third-party relay such as Postmark, SMTP2GO, or Mailgun needs that relay’s include in its SPF record. SPF is checked against the envelope sender’s domain. Postmark and SMTP2GO document provider-managed SPF on their default return paths, so they need no root include; Mailgun’s SPF record belongs on its configured sending domain, and Mailgun recommends using a subdomain.

