Reading time: 9 min · Last verified: August 2026 · SMTPedia editorial team
There is no such thing as a Bluehost mail server. Search for one and you will be handed mail.bluehost.com, a hostname that does resolve and that no Bluehost help article ever asks you to type. The real answer is that Bluehost sells two different email products, and each answers the hostname question a different way: cPanel Email points you at your own domain, and Professional Email points you at Titan. Neither is a variant of the other. Putting one product’s hostname next to the other product’s port is the fastest way to make a working mailbox stop connecting.
If your mailbox came with your hosting plan, the incoming and outgoing server is your own domain name. If you bought Professional Email, it is a titan.email hostname. Both use 993 for IMAP, 995 for POP3 and 465 for SMTP, so the ports look interchangeable and the hostnames are not. The Google AI Overview for this query currently prints both products in one merged table, with 587 listed as an alternate outgoing port. That alternate belongs to the plaintext cPanel row only. Titan does not document 587 outside its EU-hosted accounts.
Which Bluehost Mailbox Do You Have?
Your address looks the same either way. It is you@yourdomain.com in both products, so the address itself tells you nothing. What tells you is where the mailbox was created and what appears in your Bluehost portal.
Created inside cPanel, under Email Accounts, on a shared or VPS hosting plan. The mailbox lives on the same server as your website. Bluehost documents it under the heading of setting up cPanel email with POP and IMAP settings.
Sold as a separate subscription and run by Titan, not by Bluehost. The Bluehost setup guides for Outlook, Mac Mail and iPhone all name titan.email servers. Full detail on the platform lives in the Titan mail server settings and their regional hosts.
Resold, not operated. Those mailboxes take Google hostnames and are covered in the Google Workspace mail server reference. The same logic applies to any Microsoft 365 mailbox and its own server names.
cPanel Email: The Server Name Is Your Domain
This is the product most people mean by Bluehost email settings, and the one that produces the confusion. Bluehost publishes two rows for it, and the hostname changes between them.
| Protocol | Server | Port | Encryption |
|---|---|---|---|
| IMAP (incoming) | yourdomain.com | 993 | SSL/TLS |
| POP3 (incoming) | yourdomain.com | 995 | SSL/TLS |
| SMTP (outgoing) | yourdomain.com | 465 | SSL/TLS |
| IMAP (plaintext) | mail.yourdomain.com | 143 | None |
| POP3 (plaintext) | mail.yourdomain.com | 110 | None |
| SMTP (plaintext) | mail.yourdomain.com | 25 or 587 | None |
Read the two blocks as a pair, not a menu. Bluehost puts the bare domain in the secure rows and the mail. prefix in the standard rows. Username is the full email address in every case, and outgoing authentication is required. Use the secure block. | |||
Two things about that table are worth slowing down for, because both are Bluehost-specific rather than general practice.
The first is that the encrypted rows drop the mail. prefix. Most hosts keep one hostname and change only the port. Bluehost does not, and the reason is certificate matching: the secure connection has to be made to a name the server can prove it owns. The mechanics of that check are set out in the guide to how SSL and TLS certificates are validated for mail. A client configured with mail.yourdomain.com on port 993 will often fail on the certificate name rather than the password, which is why the error you see makes no mention of the hostname at all.
The second is that your domain only works as a mail hostname while its DNS still points at the Bluehost server. Move the website elsewhere and keep the mailbox, or park the domain, and the encrypted rows quietly stop resolving to the right machine. That is the single most common way a Bluehost mailbox that worked for two years stops working overnight, and it is a DNS question rather than a client question. The behaviour of the records involved is covered in the reference on what MX records do and how delivery follows them.
Where the exact server name is written down
Bluehost does not want you to guess it, and it publishes the path to the authoritative copy. In the Bluehost portal, open Hosting, click cPanel Email, then click Connect Devices next to the mailbox. The panel that opens is headed Mail Client Manual Settings and contains the values for that account. An older Bluehost article gives the equivalent route inside cPanel itself: the Email tab, then Email Configuration in the side menu.
What that panel often shows is not your domain and not mail. anything, but a server name of the form boxNNNN.bluehost.com. Those names are real and they are per-machine. Checked from an outside resolver on August 28, 2026, box5555.bluehost.com answers with an address while box9999.bluehost.com and a randomly generated subdomain of bluehost.com both return NXDOMAIN, which rules out a wildcard and confirms that each name belongs to a specific server. If Bluehost gives you one, it is the most robust value you can enter, because it does not depend on where your domain currently points.
Professional Email: The Servers Belong to Titan
Bluehost Professional Email is a Titan mailbox sold under the Bluehost name. The Bluehost setup articles for Outlook, Mac Mail and iOS all list the same three hostnames, and none of them contains the word bluehost.
| Protocol | Server | Port | Encryption |
|---|---|---|---|
| IMAP (incoming) | imap.titan.email | 993 | SSL/TLS |
| POP (incoming) | pop.titan.email | 995 | SSL/TLS |
| SMTP (outgoing) | smtp.titan.email | 465 | SSL/TLS |
Verified at the DNS layer on August 28, 2026: all three names resolve, and a randomly generated subdomain of titan.email returns NXDOMAIN, so the resolution is real rather than a wildcard catching every typo. | |||
Titan also runs a European estate whose hostnames carry a numeric suffix: its guide for EU-hosted accounts gives imap0101.titan.email on 993 and smtp0101.titan.email on 465, both with SSL, and it is the only Titan article that offers 587 with STARTTLS as an alternate. Those names resolve too, to addresses in a different region from the default pair. You do not choose between the two sets; the account is provisioned on one of them and the panel tells you which. If your Professional Email mailbox refuses the default hostnames, that is the case to check before anything else, and the Titan settings page covers the regional split and the prerequisites in full.
Port 587 Belongs to One Row Only
This is where merged tables do real damage. Port 587 appears exactly once in the Bluehost documentation for cPanel email, and it appears there as an alternative to port 25 inside the standard, unencrypted block. It is not offered as an alternative to 465. On the Titan side it does not appear at all outside the EU-hosted article.
The only encrypted outgoing port Bluehost publishes for cPanel email, and the only one Titan publishes for Professional Email. TLS is negotiated before the SMTP conversation starts.
Published by Bluehost only alongside mail.yourdomain.com in the standard block. Reach for it when a network blocks 465, and expect your client to warn you about the connection.
The combination no Bluehost page publishes and the one people assemble from a merged table. It fails on the handshake, before authentication, so the error never mentions the port.
The distinction underneath is not a Bluehost quirk. Port 465 opens encrypted immediately; port 587 opens in the clear and upgrades on a STARTTLS command. Both end secure when the server supports them, and they fail differently when it does not. The reference on mail protocols and which port belongs to which service sets out the whole set, and the specific refusal you get when a server insists on the upgrade is unpacked in the analysis of the must issue a STARTTLS command rejection.
Entering the Settings in a Mail Client
The values do not change between platforms. What changes is the label each client puts on the same encryption method, and Bluehost autodiscovery is unreliable enough on custom domains that manual entry is usually faster than fighting it.
| Client | What to do |
|---|---|
| Outlook | Choose the manual or advanced setup path and pick IMAP. Selecting SSL/TLS on 993 and 465 is correct; the label to avoid is SSL on 587. |
| Apple Mail and iOS | Add the account as Other rather than letting Mail detect the provider, and fill in the outgoing server password even where the field is marked optional. |
| Android, Gmail app | Use Manual setup and enter the same three values. Personal, not Exchange. |
| Thunderbird | Let it probe, then correct the hostname by hand. Its guess for a custom domain is frequently the mail. form on an encrypted port, which is the pairing Bluehost does not publish. |
Choosing between the two incoming protocols is a separate decision from choosing a hostname. IMAP leaves messages on the server and mirrors them everywhere; POP3 downloads them and, by default, takes them off the server, which matters more than usual on a shared plan where mailbox space is finite. The walkthroughs of how an IMAP account should be configured and what POP3 retention actually does to your server copy cover the trade-off, and the general guide to configuring outgoing mail on any provider covers the sending half.
The 500 per Hour Limit Nobody Reads Until It Bites
Bluehost states the same figure on two separate help pages: each domain on a shared server is allowed 500 outgoing emails per hour. The limit applies per domain, and Bluehost notes that addon domains, subdomains and mailing lists each carry their own allowance. Cross it and messages are simply not delivered until the hour rolls over, with a Speed Limit Exceeded response. On VPS and dedicated plans Bluehost publishes no set limit for outgoing mail and asks for mailing list best practice instead.
The practical reading is that a hosting mailbox is not a sending platform. A newsletter, a WooCommerce store on a busy day or a plugin retrying failed notifications will reach 500 without anybody feeling like they sent a campaign, and the symptom is mail that vanishes rather than mail that errors visibly in the client. Campaign and transactional traffic belongs on a dedicated service; the survey of what each business email hosting plan actually lets you do puts the mailbox products and the sending products side by side.
When Bluehost Email Stops Working
Configuration, not credentials. Webmail never touches the hostname, so it proves the password is right and proves nothing else. Re-enter the values from Mail Client Manual Settings rather than resetting anything.
Outgoing authentication is off, or the port is blocked. Bluehost requires authentication on the outgoing server; a client that submits without it is refused in the way described in the breakdown of a relay access denied response.
Almost always the mail. prefix on an encrypted port. Drop it, or use the server name Bluehost gives you in the portal.
An authentication question, not a settings one. Confirm the domain publishes a policy that covers the Bluehost servers using the SPF record checker, and read the syntax rules in the guide to how an SPF record is built and where it usually breaks.
Read the bounce text before touching a client field. The directory of SMTP error codes and what each one means resolves most of them in a minute. If the address is meant to relay elsewhere, the behaviour is described in the guide to how forwarding is set up and where it breaks authentication.
What Bluehost Does Not Publish
Third-party settings pages fill gaps the provider left empty, and the filled-in values are guesses often enough to be worth naming. As read in August 2026, the Bluehost help centre publishes no application-specific password scheme for cPanel email: the mailbox password is the mail client password. It publishes no single canonical hostname to substitute for your domain, which is why every one of its own articles routes you to the portal instead. It publishes no per-message recipient ceiling alongside the hourly figure. Values circulating for any of those three did not come from Bluehost, and none of them appear on this page.
One more absence is worth flagging because it changes what you should type. Bluehost does not document mail.bluehost.com as a customer mail server anywhere, despite the name resolving. A hostname that answers DNS is not a hostname a provider supports.
Bluehost Email Settings FAQ
What is the SMTP server for Bluehost?
It depends on the product. For a cPanel mailbox that came with your hosting plan, the Bluehost SMTP server is your own domain name on port 465 with SSL/TLS, or mail.yourdomain.com on 25 or 587 without encryption. For Bluehost Professional Email it is smtp.titan.email on port 465 with SSL/TLS. There is no shared smtp.bluehost.com endpoint, and authentication is required either way.
Is Bluehost email POP or IMAP?
Both are available on both products. The Bluehost IMAP settings use port 993 with SSL/TLS; the POP3 settings use 995 with SSL/TLS. On cPanel email the hostname is the same for either, and on Professional Email they differ, imap.titan.email against pop.titan.email. Choose IMAP unless you have a specific reason not to, particularly on a shared plan where a POP3 client set to delete server copies is hard to undo.
What are the port settings for IMAP on Bluehost?
Port 993 with SSL/TLS in every documented configuration. Bluehost also lists 143 with no encryption in its standard block, paired with the mail. hostname. Use 993. The one pairing to avoid is 993 with the mail. prefix, which is not a combination Bluehost publishes and which typically fails on certificate validation rather than on the password.
Why is my Bluehost email not working?
Test webmail first. If webmail accepts the password, the account is fine and the fault is in the client configuration, most often the hostname or the encryption label. If sending stopped abruptly on an otherwise unchanged setup, check the hourly allowance: shared plans are held to 500 outgoing messages per hour per domain, and the messages beyond it are not delivered rather than rejected in a way you will notice. If receiving stopped after a site migration, the domain no longer points where the mailbox lives.
How do I access my email through Bluehost?
Through webmail in the browser, which needs no settings at all, or through a mail client using the values above. Bluehost keeps the authoritative copy of your account settings in the portal: open Hosting, click cPanel Email, then Connect Devices next to the mailbox, and read the Mail Client Manual Settings panel. That panel is worth trusting over any generic table, including this one, because it names the specific server your mailbox sits on.
Are the Bluehost email settings different on iPhone or Android?
No. Hostnames, ports and encryption are identical on every platform, and a page promising special Bluehost settings for iPhone is describing an interface rather than a protocol. On iOS, add the account as Other so Mail does not guess, and enter the outgoing password even where the field says optional. On Android, use Manual setup in the Gmail app and choose Personal rather than Exchange.
Settings for the other hosting mailboxes documented on this site:
GoDaddy Email Settings · IONOS Email Settings · Namecheap Private Email Settings · Titan Email Settings
About This Guide
These values were verified on August 28, 2026 against Bluehost and Titan documentation: the Bluehost article on setting up cPanel email with POP and IMAP settings for the secure and standard tables and for the Connect Devices route, its iOS setup article for the same pair and the cPanel Email Configuration route, its Outlook guide for Professional Email for the titan.email hostnames, the Titan article on configuring other apps by IMAP and POP for the same three values, the Titan guide for EU-hosted accounts for the numbered regional hosts and the single documented 587 row, and both the Bluehost outbound limits article and its account limits summary for the 500 per hour figure. Hostnames were additionally resolved from an outside resolver on the same date, with negative wildcard controls on bluehost.com and titan.email. Fields Bluehost does not publish, including any application-specific password and any canonical customer mail hostname, are absent rather than filled in from third-party pages. SMTPedia re-verifies provider settings quarterly. If Bluehost publishes a value that contradicts this page, the provider is right and we want to hear about it.
About the Author
Alaa · LinkedIn
Email infrastructure specialist with 8+ years of hands-on experience in SMTP, deliverability, and email verification. I’ve configured and troubleshot mail systems across Postfix, Exchange, and cloud relays, managed IP reputation and warmup campaigns, and built verification pipelines processing millions of addresses. My work spans DNS authentication (SPF, DKIM, DMARC, BIMI), bounce handling, blocklist monitoring, and compliance frameworks including CAN-SPAM and GDPR. I write every article on SMTPedia to give email professionals, developers, and marketers the accurate, RFC-grounded reference they need.
About SMTPedia
SMTPedia is an independent email industry reference covering SMTP, IMAP, POP3, email deliverability, marketing platforms, DNS authentication, and email verification. Every article is researched from official provider documentation, IETF RFCs, and industry best practices. Settings and configurations are verified quarterly.
We are cited as a source by ChatGPT, Microsoft Copilot, and thousands of email professionals worldwide. Learn more about our editorial process.
