Every hosting plan includes mailboxes on your own domain. Getting one into a mail app takes a mailbox, five settings, and nothing else. This guide gives you all of them, plus the browser route when you do not want to configure anything.
Create the mailbox first
In the panel, open your site and go to Emails, then Add account. Pick the address and a password. That password is what every mail app will ask for, so use a real one and keep it.
One address can also be marked catch-all, which means it receives mail sent to anything at your domain that has no mailbox of its own. Useful for a small business, dangerous for spam volume, so only turn it on deliberately.
The settings every mail app asks for
Whether it is Outlook, Apple Mail, Thunderbird or a phone’s built-in client, the questions are the same. Replace yourdomain.com with your actual domain:
| Setting | Value |
|---|---|
| Incoming server (IMAP) | mail.yourdomain.com, port 993, SSL/TLS |
| Outgoing server (SMTP) | mail.yourdomain.com, port 465, SSL/TLS |
| Username | the full email address |
| Password | the mailbox password |
If an app insists on STARTTLS for outgoing mail, use port 587 instead of 465. Both work.
Two mistakes cause almost every failed setup. The username is the complete address, not the part before the @. And the incoming type should be IMAP, not POP3. IMAP keeps the mailbox on the server so your phone and laptop see the same mail; POP3 downloads and deletes, which is almost never what anyone wants today.
Webmail, for when you just want a browser
Your mail is also reachable at webmail.yourdomain.com, with the same address and password. Nothing to configure, works from any machine, and it is the quickest way to test a new mailbox before touching a mail app. The panel’s Emails page also has a Webmail button that takes you to the same place.
If the mail servers cannot be found
The mail. and webmail. addresses exist automatically when your domain’s DNS runs on our nameservers, which is the normal setup. If you manage DNS somewhere else, for example at Cloudflare, those records are your responsibility, and a missing one is why a mail app says it cannot find the server. The Cloudflare guide covers which mail records to keep and why they must stay DNS-only.
Sending works, but lands in spam?
That is not a settings problem, it is a DNS reputation problem, and it has its own guide. The short version: two DNS records tell Gmail your mail is really yours, and on our nameservers they are set up for you.