Self-hosted business tools on a private VPS
If you choose a self-hosted mailbox, it lives next to the rest of the self-hosted stack.
Read this guide →
Cloud & Infrastructure / Deep Dive
Professional email setup for your own domain: registration, DNS, branded mailboxes and the SPF, DKIM and DMARC records that decide whether your messages reach the inbox or the spam folder. We register, configure and test it all, then hand you a deliverability report.
Email is still the default channel for sales, contracts, support and operations. The easiest way to lose a deal is to land in the recipient's spam folder. Gmail, Outlook, Apple Mail and every corporate filter decide that before a human reads the message.
They judge three things: your domain's authentication records, the sending IP's reputation and the structure of the message. Get those right and a small business sending from its own domain is treated like any large company. Get them wrong and even one-to-one email gets quarantined.
This guide is part of our managed cloud hosting service. It covers the full setup: the right domain, the right mailbox host, SPF, DKIM, DMARC and the details that move deliverability.
SPF + DKIM + DMARC
you@yourcompany.com
Workspace, 365, self-hosted
The domain is the foundation. It shows up on every business card, every contract and every email. The setup is small but it lasts: register the right TLD, lock the domain so it cannot be transferred without confirmation, turn on WHOIS privacy and use registrar-level DNS you actually understand. We also check for typo and lookalike domains that competitors or scammers might exploit.
There is no single right mailbox host. The pick depends on team size, existing tools, compliance needs and budget. We map the trade-offs and choose once, on purpose, instead of drifting into whatever the previous IT person installed.

These three records tell receiving mail servers three things. SPF lists the servers allowed to send email for your domain. DKIM signs every outgoing message, so a recipient can verify it really came from your infrastructure. DMARC says what to do when a message fails those checks, and reports back so you can see who is trying to spoof you.
Major mailbox providers now require all three for bulk sending, and increasingly for transactional and one-to-one mail. Without DMARC enforcement anyone can send mail that appears to come from your domain, and your customers' filters might not catch it.
Configuration is a one-time DNS task with one ongoing piece, the DMARC report review. It changes how reliably your email is delivered.


The most visible change is that customers stop saying your email went to spam. Behind the scenes, four things shift.
Outbound deliverability climbs because every message is signed and authenticated. Spoofing attempts get blocked, because DMARC enforcement tells receivers to reject mail that is not really from you. The DMARC report stream shows who is impersonating the domain, which helps with incident response. And mailbox sprawl gets cleaned up: aliases, groups and shared inboxes are organised, so the right person sees the right mail and nobody is logged into seven mailboxes at once.
Mailboxes are also part of the backup plan. See our guide to disaster recovery and backup solutions.
Most deliverability problems trace back to broken or missing DMARC, a soft-fail SPF or a forgotten third-party sender. Send us the domain. We will run the diagnostics and quote a fix.
Audit my email deliverabilityAuthentication
Mailbox hosts
Deliverability report
FAQ
What teams ask before they move their email.
Yes. Most mailbox hosts let you add a custom domain to an existing account, route inbound mail through their filter and send outbound mail from your domain. The move usually needs an MX record change, a DKIM record per sending platform and a few hours of mail-in-flight handling. You do not have to create new mailboxes from scratch unless you want to.
DMARC ties SPF and DKIM together by telling receivers what to do when a message fails authentication. Without it, anyone can send mail that claims to be from your domain and the receiver has no instruction on how to handle it. With DMARC at enforcement, spoofed mail is rejected and you receive aggregated reports of every attempt. Major receivers now require it for bulk senders, so yes, you need it.
No. For most businesses a managed host such as Google Workspace, Microsoft 365, Fastmail or Zoho is the right answer, because deliverability, spam filtering and calendar and file integrations come with the package. Self-hosting makes sense for three reasons: regulatory requirements, very high volume where per-mailbox pricing stops working, or a deliberate policy of owning the full stack. We deploy both and tell you honestly which one fits.
From a fresh domain, a typical small-team setup takes 1 to 3 business days. Registration and DNS happen on day one. Mailbox creation and DKIM signing follow on day two. DMARC moves to enforcement after a one-week reporting window. Migrations from an existing setup take longer because of in-flight mail, usually 1 to 2 weeks end to end.
Both are part of the setup. Branded HTML signatures are deployed centrally, so every outbound message carries the same identity. Aliases such as sales@, support@ and hello@ are set to land in the right inbox or shared mailbox. For larger teams we organise distribution groups and shared inboxes, so the right person handles each inbound message.
Three signals. DMARC aggregate reports show authentication pass rates climbing toward 100%. Third-party tools such as GlockApps and Mail-tester score the domain in the inbox range. Seed-list tests across the major mailbox providers confirm the mail lands in the primary inbox. We take a baseline measurement before the work and a follow-up two to four weeks after, so the change shows up in numbers.
Tell us the domain, or what you want to register, and the team size. We will deliver registration, mailbox setup, full authentication and a deliverability report you can verify.
Set up branded emailEach guide stands alone, but the full picture is built from all four. Pair this with the related deep dives or jump back to the Cloud, Hosting & Infrastructure pillar.
If you choose a self-hosted mailbox, it lives next to the rest of the self-hosted stack.
Read this guide →Webmail and admin consoles can be published through tunnels for an extra access layer.
Read this guide →Mailboxes are part of the backup plan, so deletion and account compromise both recover from snapshots.
Read this guide →