Business Email on Your Own Domain: Setup Guide for Founders
Business email on your own domain, explained: the four DNS records (MX, SPF, DKIM, DMARC), the order to set them up, and how to test before you rely on it.
To get business email on your own domain, you need three things: a domain you control, a mailbox provider (the service that stores and sends your mail), and four DNS records that connect the two. The records are MX, SPF, DKIM and DMARC. Set them up in that order, send yourself a test, and you're done. This guide explains each one in plain words.
Why bother with your own domain
An address like
you@yourbusiness.comlooks more trustworthy than
yourbusiness123@gmail.com. It also keeps your email tied to a name you own, so you can switch providers later without changing your address.
What you need before you start
- A domain you own. If you have a website, you already have one.
- Access to your DNS settings. DNS is the address book of the internet. It lives wherever you manage your domain (your registrar, or a service like Cloudflare). If you can't log in there, fix that first.
- A mailbox provider. Pick one and keep its setup page open. It will give you the exact values to paste in.
The four records, in order
1. MX records: where incoming mail goes
MX records tell the internet which servers receive mail for your domain. Without them, your address exists on paper but nothing arrives. Your provider gives you the values; you add them in your DNS settings.
Common gotcha: if your DNS host offers a "proxy" toggle (Cloudflare calls it the orange cloud), mail records must not be proxied. Leave MX records as DNS-only.
2. SPF: who may send as you
SPF is a TXT record listing the servers allowed to send mail from your domain. Receiving servers check it to spot fakes.
Common gotcha: a domain should have only one SPF record. If you use more than one service to send mail, merge them into a single record instead of adding a second.
3. DKIM: a signature on every message
DKIM adds a signature to outgoing mail so receivers can tell it wasn't altered. Your provider generates the key; you publish it in DNS.
4. DMARC: what to do with failures
DMARC tells receiving servers what to do with mail that fails SPF and DKIM. Most beginners start in monitoring mode, then tighten the policy once they see their real mail passing.
Receiving and sending are separate
A frequent surprise: getting mail to arrive (MX) does not mean your outgoing mail is trusted (SPF, DKIM, DMARC). Set up both before you email customers, or your messages may land in spam.
How to test
- Send a message from another account to your new address. Confirm it arrives.
- Reply from the new address to a personal account. Check it isn't in spam.
- Look at the message's headers or your provider's checker to confirm SPF and DKIM pass.
- Wait. DNS changes can take a while to spread, sometimes up to a day or two.
If you'd rather not do it by hand
KodeMail is a KodeBase product for business email on a custom domain. See what it does on the KodeMail page, or browse the full catalog. Check the product page for exactly what's included before you buy.
FAQ
Do I need all four records? For a working inbox, MX is the minimum. For mail that reaches people's inboxes instead of spam, set up SPF, DKIM and DMARC too.
Can I keep my current website? Yes. Email records are separate from the records that point your domain at your website.
How long does it take? The edits take minutes. Spreading across the internet can take longer, so test later if it doesn't work right away.
Key takeaways
- Own the domain, have DNS access, pick a provider.
- Add MX, then SPF, DKIM, DMARC.
- One SPF record only, and don't proxy MX.
- Test both receiving and sending before you rely on it.
Moving off Base44, or stuck on an app problem?
See how a Base44 migration works, or browse the tools and services that help you build and secure your app.