How to get a free business email address (and what it costs you)

There is no genuinely free way to *send* business email from your own domain at any volume. There are several free ways to *receive* it, and a few free mailbox tiers with real limits. The distinction matters more than the price, because the moment you start sending from you@yourdomain.com you inherit responsibility for SPF, DKIM, DMARC alignment and reputation — and the free routes are where alignment quietly breaks.

You will also need a domain. That is the one unavoidable cost, and it is annual rather than monthly.

The options, honestly

Two notes on the free mailbox tiers specifically. Limits change frequently — user counts, storage caps and whether IMAP/SMTP access is included have all moved over the years — so check the provider's current terms rather than an article. And "webmail only" is a bigger constraint than it sounds: no IMAP or SMTP means no desktop client, no mobile client beyond the provider's own app, and no connecting the mailbox to any other tool.

The forwarding pattern, and the trap in it

The common free setup is: register a domain, point MX at a free forwarder, and have mail arrive in a personal Gmail account. Inbound works perfectly. Then you reply, and one of two things happens.

If you reply as your Gmail address, the recipient sees yourname@gmail.com. The branding is gone, and the thread now has two identities in it.

If you configure "send mail as" with your custom address, Gmail sends through an SMTP server. Unless that server is authorised to send for your domain *and* signs DKIM for your domain, the message will not align under DMARC:

• Sending via Gmail's own servers with a custom From on a free account means DKIM is signed by gmail.com, not by your domain. DKIM alignment fails.
• SPF authenticates the envelope sender, which in that path is Google's, not yours. SPF alignment fails too.
• With a DMARC policy at p=quarantine or p=reject on your domain, your own replies can be filtered or rejected.

There is also a forwarding-specific effect worth understanding: forwarding breaks SPF but preserves DKIM. When your forwarder relays mail to your inbox, the connecting IP is the forwarder's, so SPF fails for the original sender's domain unless the forwarder rewrites the envelope (SRS). The original DKIM signature survives, which is why DKIM alignment is the mechanism to rely on. This is a reason senders see DMARC failures in reports that are not attacks — they are forwards.

What to do, by situation

You only need to receive mail at your domain. Use registrar forwarding or Cloudflare Email Routing. Publish MX for the service, publish an SPF record with -all or ~all and no senders, and publish v=DMARC1; p=reject; — a domain that never sends should say so loudly. This is the cleanest free setup there is.

You need to send occasional one-to-one mail. Take a free mailbox tier if it includes SMTP, or pay for one mailbox. Configure DKIM for your domain with that provider, put their include: in SPF, and verify alignment on a delivered message before you rely on it.

You need to send campaigns or outbound sequences. Nothing free works. You need mailbox hosting plus, for bulk, a sending platform — and you need a warmed domain. Attempting cold outreach from a free tier produces rate limits, poor alignment and a new domain with no history, which is the worst combination in email.

Verify alignment before you trust it

dig mx example.com +short
dig txt example.com +short
dig txt _dmarc.example.com +short

Then send a message to a mailbox you control elsewhere and read the header:

Authentication-Results: mx.google.com;
  dkim=pass header.i=@example.com;
  spf=pass smtp.mailfrom=example.com;
  dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=example.com

The part that matters is header.from=example.com matching the domain that authenticated. If dkim=pass header.i=@gmail.com appears alongside header.from=example.com, you have a pass without alignment, which DMARC counts as a failure.

What not to do

1. Do not run a business from a consumer address. You cannot add colleagues, you cannot transfer it when someone leaves, and you cannot authenticate your brand.
2. Do not use "send mail as" without DKIM for your domain. It is the most common cause of a small business's own replies going to spam.
3. Do not publish a permissive SPF record to make a free setup work. +all authorises the entire internet to send as you.
4. Do not skip DMARC on a receive-only domain. An unprotected domain with no outbound mail is an easy spoofing target, and p=reject costs nothing there.
5. Do not cold-email from a free tier. Rate limits aside, a brand-new domain with no sending history and partial alignment will not reach the inbox.
6. Do not use a free throwaway domain or a cheap, heavily-abused TLD for business mail. Domain age and TLD reputation are real inputs.
7. Do not stack two free forwarders. Each hop adds an SPF failure and a point of silent loss.

MailPilot works with whichever route you choose: it warms mailboxes over OAuth (Gmail, Outlook) or SMTP/IMAP including custom SMTP, checks SPF, DKIM and DMARC on mail as delivered — which is where alignment problems in a forwarding or send-as setup actually show up — and measures real inbox placement per provider. There is a free plan, and every plan includes unlimited mailboxes.