"Email for my website" is the question every operator asks the week after launching a site. The website works; emails to hello@yourcompany.com bounce because no mail server claims the domain. Fixing it takes about 90 minutes if you know the four steps and the right order — and a lot longer if you accept the bundled package the registrar pushes at checkout.
Most registrar bundles tie website hosting and email hosting together as one product. The bundle is convenient on day one and operationally restrictive thereafter. When the website needs to move (faster hosting, better CDN), the email moves with it. When the email needs to move (better deliverability, cheaper tier), the website moves with it. Getting email for my website to work properly over the long run means setting the two up independently from the start.
This guide walks the four-step setup that keeps website and email on separate hosts but at the same domain. Getting email for my website right at signup saves the migration friction that bundle-path operators face at year two. For the broader walkthrough see how to create email with domain.
What "Email for My Website" Actually Means
Email for my website means hello@mycompany.com routes to a working mailbox while mycompany.com serves the website. Two services share one domain on separate infrastructure. The website needs A or CNAME records; the email needs MX records. Both record sets live at the same DNS host.
The two services do not interfere with each other when configured correctly. They only collide when one host tries to claim both — which is what happens with bundled packages from registrars or web hosts. The four-step setup below keeps them deliberately separate.
Two Paths: Bundle vs Separate Hosts
Two paths cover essentially every "email for my website" decision. The bundle path takes whatever email the website host or registrar sells alongside the website plan. The separate-hosts path picks the website host and the mailbox host independently and lets DNS coordinate the two. The setup time difference is small; the long-run flexibility difference is large.
| Path | Year-1 cost | Flexibility | Migration friction |
|---|---|---|---|
| Bundle (web host + bundled email) | $10-25/year extra above website | Locked together | High (switching either moves both) |
| Separate (web host + independent mailbox host) | $0-50/year for email | Each replaceable independently | Low (DNS record change) |
The honest pick for any business expecting to operate the website for more than two years is the separate-hosts path. The 15 minutes of extra setup buys flexibility worth years of compounding. Most operators who pick the bundle path do so because the bundling vendor showed it first at checkout; the decision is rarely informed.
A second consideration: the bundle vendors' email tiers usually skip per-customer DKIM rotation, ship without proper alias governance, and put 2FA behind paid add-ons. The cheaper bundled email is cheaper because features get subtracted. The separate-hosts path lets you pick a mailbox host whose feature defaults match what you actually need.
Step 1: Pick the Domain Once
Step one when setting up email for my website is to pick the domain once and register it at a real registrar. Cloudflare Registrar at-cost, Namecheap, or Porkbun. Avoid registrars that bundle email or web hosting — they make the separate-hosts path harder by interfering with the DNS records you'll publish in step four.
The domain is the only thing that's the same between the website and the mailbox. Everything else (hosting, DNS, mail server) lives at different vendors. Picking the right registrar at step one keeps every later step easy. Picking a bundle registrar at step one means fighting the registrar's defaults at every later step.
Step 2: Set Up Website Hosting
Step two of "email for my website" sets up the website itself. The web host options are wide: Vercel, Netlify, GitHub Pages, Cloudflare Pages for static sites; AWS, Render, Fly.io for dynamic; WordPress on managed hosting for content sites. Pick whichever fits the tech stack. The web host generates A or CNAME records you'll publish in step four.
The web host should not also be your mailbox host. If the chosen web host offers a bundled email add-on, decline it; that's the path you're avoiding. The web host's job is to serve the website. Email lives somewhere else and gets coordinated via DNS.
Step 3: Set Up Mailbox Hosting
Step three sets up the mailbox host independently of the web host. TrekMail Nano (free) for solo operators with 10 domains × 10 mailboxes; Starter at $4/month for higher send volume or larger teams. Add the domain in the dashboard and note the MX, SPF, DKIM, and DMARC records the platform generates.
The mailbox host should not also be your web host. The reason for keeping them separate is the same in reverse — if the chosen mailbox host offers a bundled website service, decline it. The mailbox host's job is to receive and send email. The website lives somewhere else.
Step 4: Coordinate DNS Records for Both
Step four publishes both sets of records at the DNS host. Website records (A and CNAME pointing at the web host) for the root and www. Email records (MX, plus SPF, DKIM, DMARC TXT) for the same domain. The two record sets don't conflict because they use different types.
The DNS host should be independent of both the web host and the mailbox host. Cloudflare DNS at the free tier is the standard pick — fast, well-documented, and operationally separate from any other service. Other valid choices include Route 53, the registrar's built-in DNS if it supports modern records, and smaller dedicated DNS providers. The independence matters for the same reason as steps one through three: future migrations of either service should be MX or CNAME flips, not full DNS migrations. See set up email on my domain for the email-records detail.
Old Way vs New Way of Coordinating
The old way of setting up email for my website was to buy a hosting bundle that included both website and email, then accept whichever email tier the bundle shipped. The bundle was cheap at year one and operationally restrictive thereafter. Moving the website meant moving the email; moving the email meant interrupting the website.
The new way picks the four layers independently — registrar, DNS host, web host, mailbox host — and coordinates them through DNS records. The setup takes 30 extra minutes at signup. The flexibility difference compounds across every year of operation. Most operators who pick the new way at signup never face a website-or-email migration project that touches both at once. Most operators who pick the old way face it at year two or three when one service falls short.
Where the Bundle Path Breaks
The bundle path for email for my website breaks in three common patterns. First: the bundled email tier has weak DKIM rotation and outbound starts landing in spam. Second: the bundled web host has slow pages or weak CDN coverage. Third: a security incident at the bundle vendor compromises both services at once.
The fix for any of these is to migrate, which is the moment the bundle path's lock-in costs show up. Migrating the website out of the bundle moves the email too, requiring DNS changes for both at the same time. Migrating the email out of the bundle moves the website too. The bundle path's convenience at signup converts to coordinated downtime at year two. See email for my business for the broader decision frame and custom domain email for the conceptual framing.
Next Steps
The honest "email for my website" setup picks the four layers independently and coordinates them through DNS at an independent DNS host. Total year-one cost: $9 for the domain plus whatever the website host charges plus $0 (TrekMail Nano free) or $42/year (TrekMail Starter) for the mailbox. The setup takes about 90 minutes and stays portable for years.
Test TrekMail Nano free at trekmail.net/pricing — no card required. The Nano tier covers 10 domains × 10 mailboxes; Starter expands to 50 × 100 when needed. The four-step setup works identically across all tiers and across any reasonable web host.
One migration tip worth noting: if you're moving email for my website from a bundled host to the separate-hosts setup, lower your DNS TTL to 300 seconds 48 hours before the cutover. The shorter TTL means the MX change propagates in minutes rather than hours, compressing the window during which inbound mail might land at the old host. After the migration is stable, raise the TTL back to 3,600 seconds. This costs nothing and prevents most of the inbox-gap issues operators worry about when switching mailbox hosts mid-operation.
