A2 Hosting was a shared cPanel host with a WordPress focus; in January 2025 it was acquired by World Host Group, and in April 2025 the brand was retired and the property relaunched as Hosting.com. The shared plans bundle domain email through cPanel with mailbox counts that step up by tier (5 on Starter, 40 on Max), and mail WordPress sends through the server leaves via MailChannels. External SMTP is allowed: WordPress can send through the local cPanel mailbox or connect to a third-party provider over SMTP or its HTTP API. The documented ceiling that bites first is 100 messages per hour, per domain; the plans page adds 2,400 a day.
Hosting.com sells three shared plans. Starter (up to 5 sites) renews at $13.99/month after an intro price of $2.99/month on a one-year term, or $1.99/month if you pay for four years upfront. Pro (10 sites) renews at $19.99/month and Max (50 sites) at $27.99/month. Hosting.com sits in the entry shared-hosting band, well below the managed-WordPress tier that Kinsta and WP Engine occupy.
Email on Hosting.com
How wp_mail works by default
A fresh WordPress install on a Hosting.com shared plan sends mail through PHP’s mail() function, which hands off to the server’s local exim configuration. Hosting.com routes that outbound traffic through
MailChannels, an outbound relay and spam filter, rather than letting the server connect directly to recipient mail servers, so the message leaves the host from MailChannels’s IPs instead of a shared cPanel IP that other Hosting.com sites also use. The DKIM signature (the cryptographic signature receiving mail servers use to confirm a message came from the expected domain) is set up per domain in cPanel’s Email Deliverability panel, and Hosting.com’s KB says a domain without it shows a Repair button that installs it.
The practical consequence: password resets, order confirmations, and contact-form notifications go out through a filtered relay, and whether they carry a DKIM signature depends on the domain’s status in Email Deliverability. The From address on a fresh install (wordpress@<domain>) is not a real mailbox. Hosting.com’s
WordPress sending guide has the operator install an SMTP plugin, authenticate against the account’s own mail server, and send from an address that exists on the account. The other route is to skip the bundled path and send through a third-party service with its own authentication chain.
Outbound SMTP port status
| Port | Status | Protocol |
|---|---|---|
| 587 | Open to external servers (recommended) | SMTP with STARTTLS |
| 465 | Open to external servers (recommended) | SMTPS (implicit TLS) |
| 25 | Not recommended for authenticated sending | SMTP (legacy) |
| 993 | Open | IMAPS (incoming, bundled mailboxes) |
| 995 | Open | POP3S (incoming, bundled mailboxes) |
Hosting.com’s
external-SMTP article now reads: “You can use an external SMTP server to send email from your hosting.com account.” It used to depend on the server: accounts on legacy A2 Hosting servers with shared, reseller or managed WordPress plans could not connect to an outside SMTP server, and had to use the provider’s HTTP API instead. The article says that restriction is gone and external SMTP “works across hosting.com servers”. It points WordPress users at an SMTP plugin, recommends port 587 with STARTTLS or 465 with implicit TLS, and says port 25 “is not the right choice for authenticated sending”. It doesn’t mention 2525, so use whichever of 587 and 465 the provider documents.
The same article still makes the case for the HTTP API: it does not depend on outbound SMTP ports being open, it returns clearer errors when a send fails, and it usually reports delivery status back. Either transport works on Hosting.com; the API is the one that tells you more when something goes wrong.
Sending limits
| Limit | Applies to |
|---|---|
| 100 messages per hour | Each domain, on every Hosting.com product |
| 2,400 messages per day | Shared hosting plans (plans page) |
Hosting.com’s
sending-limits article gives the hourly number: 100 messages per hour, per domain. It is per domain rather than per account, so three domains on one plan each get their own 100. Email forwarders count towards it, and so does the spam they pass on. Mail sent through an external provider does not count. The shared-hosting plans page separately lists a send limit of 2,400 a day. Neither page publishes a per-message recipient limit; the article advises breaking large recipient lists into smaller batches. An operator with a real need for more can ask support to raise it.
Hitting the cap is quiet. Messages past the limit are rejected or queued at the server, and WordPress usually reports nothing: the contact form submits, the order completes, the email never arrives. A burst of password resets after a security incident, or a WooCommerce sale with order confirmations stacking up, can reach 100 in an hour long before anyone notices.
The higher tiers buy more mailboxes, more forwarders, more disk, and more databases, but the hourly allowance per domain is the same on Starter and Max. For reference, SiteGround publishes 400 per hour on its entry plan, DreamHost publishes 100 per hour per address, and Kinsta publishes daily caps of 150, 1,000 or 3,000 messages by plan on its MailChannels relay. Hosting.com’s 100/hour is on the tighter end of the published numbers.
Mailboxes, forwarding, DNS
Hosting.com gives the operator a tiered mailbox count rather than unlimited inboxes. Starter ships with 5 mailboxes, Pro with 20, and Max with 40. Each mailbox lives under cPanel, with webmail, IMAP and POP3 access. Email forwarders step up the same way: 20, 80 and 100 across the three plans. A small business that wants a mailbox per staff member will outgrow Starter quickly; a single operator running a personal site or a small WooCommerce store will not.
Mail clients on phones and laptops connect on the standard IMAPS (993) and POP3S (995) ports without anything extra to configure; the same mailbox credentials work in the bundled Roundcube webmail. Forwarding rules and aliases are part of the same cPanel panel; no separate forwarding service is needed.
Hosting.com runs the domain’s DNS by default for any domain registered or pointed through the account, which is what lets cPanel’s Email Deliverability panel publish SPF (the DNS record that authorises which mail servers can send on behalf of a domain) and DKIM records itself. If the nameservers point elsewhere (Cloudflare is the common one), records added in cPanel “will look correct in cPanel and do nothing at all”, in the KB’s words; the values have to be copied into the external DNS provider by hand.
Authentication (SPF, DKIM, DMARC)
Hosting.com’s
authentication article lists the SPF include each product needs: include:spf.mysecurecloudhost.com for web hosting and include:spf.supercp.com for reseller accounts. Earlier versions of the article gave spf.a2hosting.com for shared accounts, so an account migrated from A2 may still carry the old include; the record cPanel’s Email Deliverability panel shows is the one to check. Both includes resolve to relay.mailchannels.net, which is why MailChannels needs no SPF entry of its own: the hosting include already authorises it.
DKIM is set per domain under cPanel → Email Deliverability → Manage. The KB says a domain without DKIM shows a Repair button that sets it up. DMARC is the one record cPanel does not create. The KB has the operator add it in Zone Editor as a TXT record at _dmarc, starting at v=DMARC1; p=none;, and warns against jumping straight to p=reject with strict alignment.
When include:spf.mysecurecloudhost.com needs to sit alongside a third-party relay’s include in one SPF record, the SPF merger folds the two together and counts the DNS lookups against RFC 7208’s ten-lookup ceiling. Hosting.com’s own article makes the same point: one SPF record per domain, with every sender’s include merged into it. Once the record is live, the DNS auth checker reads how the domain’s SPF, DKIM, and DMARC resolve from the receiver’s perspective, so a missing signature or a missed include shows up before real traffic does.
What Hosting.com does not provide
- A dedicated sending IP address. Outbound goes through MailChannels’s pooled IPs, shared with every other Hosting.com account and a long tail of other MailChannels customers. A site that needs to insulate its deliverability from the neighbours needs a sending service 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, SendGrid on Pro.
- Suppression lists and delivery events. MailChannels handles the relay, but Hosting.com documents no delivery-event feed, suppression list, or open and click tracking for the bundled path. A bounce comes back to the sending mailbox as a message, if it comes back at all. Mailgun and Postmark publish those events as they happen.
- Marketing or bulk email allowance. The sending-limits article is blunt: “Do not send newsletters or marketing campaigns through your hosting account.” A single campaign uses up a domain’s hourly allowance many times over. Marketing mail belongs on a dedicated platform.
When a third-party relay is needed
The Hosting.com default path covers personal blogs and small WooCommerce stores whose transactional volume stays well below 100 messages per hour, where WordPress sends from a real mailbox on a domain with DKIM active, and where occasional spam-folder placement on a shared MailChannels IP is acceptable. Most other shapes need to move sending off the bundled path. The triggers:
- The 100/hour cap bites. A site approaching that ceiling needs an external service, and mail sent through one does not count against the hosting limit. Postmark is the cleanest fit for transactional mail under 100,000 messages a month; SMTP2GO is the cheapest credible option; Mailgun becomes economical at higher volumes.
- A missed A transactional email is the automated message a WordPress site sends in response to a single user action – a password reset, an order confirmation, a form receipt – addressed to the user who triggered it. Read full reference → costs money. Sites where a failed password reset means a churned customer cannot depend on a shared MailChannels IP. A dedicated sending service gives both a dedicated IP and a bounce-event stream.
- You need delivery visibility. Hosting.com documents no per-message delivery events for the bundled path. Any third-party service with an API reports them.
- You’re sending newsletters or campaigns. Hosting.com’s own documentation rules out the bundled path for anything resembling bulk.
Any of the standard WordPress SMTP plugins works on Hosting.com: WP Mail SMTP, FluentSMTP, and Post SMTP connect to the provider over SMTP on 587 or 465, or over the provider’s API. Whichever transport you pick, add the DNS records the provider’s domain setup lists first (DKIM, and SPF either as an include on the root domain or on a return-path subdomain, depending on the provider); Hosting.com’s article warns that mail sent through an external provider without them “will be rejected or filtered as spam”.
Verdict
Hosting.com (formerly A2 Hosting) is a reasonable pick for operators who want shared cPanel hosting with bundled domain email and can live with the post-rebrand mailbox caps and the 100-messages-per-hour-per-domain ceiling. The MailChannels relay is better than raw PHP mail() on a shared IP, but deliverability only holds once DKIM is active for the domain and WordPress sends from a real mailbox. Sites that send more than 100 messages an hour, or that need bounce visibility, should add a third-party sending service early. Since Hosting.com dropped its external-SMTP block, that takes an SMTP plugin and the provider’s credentials.
For the WordPress email setup that supplements Hosting.com’s default path, see how to configure WordPress email.
Corrections
- 2026-10-25: an earlier version said external SMTP was blocked on all Hosting.com shared, reseller and managed WordPress plans; Hosting.com’s documentation at the time limited that block to accounts on legacy A2 Hosting servers. It also described DKIM as set per mailbox; cPanel sets it per domain.
- 2026-10-29: an earlier version said Kinsta sends no WordPress mail on the default path. Kinsta relays WordPress mail through MailChannels on every plan and publishes daily caps of 150, 1,000 or 3,000 messages by plan.
- 2026-11-12: an earlier version said to add the provider’s SPF include whichever provider you pick. 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.comas 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.

