How to set up a free business email, and what it costs you on deliverability

A business email address is possible without paying for hosting, but the free routes split into two very different categories: a free address on a provider's own domain (yourname@gmail.com) and a free or low-cost way to use your own custom domain through a provider's free tier. The second is almost always worth the extra setup step.

Free address, no custom domain

Services like Gmail, Outlook.com, or similar free webmail providers let you create an address instantly with no domain purchase. The trade-offs:

• Credibility: a @gmail.com or @outlook.com address for business correspondence reads as less established than a custom domain, especially in B2B contexts where recipients expect a matching company domain.
• Deliverability is actually fine at the individual level - these are major, well-authenticated platforms - but you inherit the platform's shared reputation rather than building your own, and you have no control over SPF/DKIM/DMARC for a domain you don't own.
• No portability: if you later want to move to a custom domain, there's no way to "upgrade" the same address.

Free or low-cost custom domain email

Several providers offer a path to using your own domain without a large upfront cost:

• Google Workspace and Microsoft 365 both offer custom-domain business email, typically with a trial period rather than a permanently free tier, but with full control over sending infrastructure once set up.
• Some newer providers position themselves around free or low-cost custom-domain email specifically, often with more limited send volume or feature sets than the established players.
• A domain registrar's free email forwarding (mail to your@yourdomain.com forwards to an existing inbox) is a middle ground - it gives you a professional-looking address without full mailbox hosting, but sending mail *from* that address for real correspondence usually still routes through whatever account receives the forward, and you need to configure SPF to include that sending source.

What to set up regardless of provider

1. SPF: a TXT record listing which servers are authorized to send as your domain - required for mail "from" a custom domain to be trusted.
2. DKIM: enabled through your provider's admin console, which publishes the public key in DNS.
3. DMARC: published separately (most providers don't do this automatically), starting at p=none to monitor before moving to enforcement.
4. MX records pointed at whichever provider actually hosts your inbox, distinct from SPF/DKIM/DMARC which govern sending, not receiving.

Skipping any of these on a custom domain - a common gap on free or trial tiers, where the setup wizard doesn't always walk through DNS configuration - means mail sent "from" your domain is unauthenticated, which increases the odds it lands in spam regardless of how good the content is.

What not to do

• Don't use a free webmail address (no custom domain) for ongoing B2B correspondence if credibility with recipients matters - the cost of a domain is small relative to the perception difference.
• Don't skip DMARC because a provider's free tier doesn't prompt for it - an unprotected domain (SPF/DKIM only, no DMARC) is more exposed to spoofing and generally reads as less trustworthy to receiving systems that check for a full authentication stack.
• Don't assume a forwarding-only free address gives you the same sending reputation as a real mailbox - what's authorized to send on your behalf still needs explicit SPF inclusion.

A complete worked DNS record set

For a custom domain yourbusiness.com set up through a typical business email provider, the full record set looks like this:

; Receiving - where mail to the domain is delivered
yourbusiness.com.        MX   10 mx1.yourprovider.com.
yourbusiness.com.        MX   20 mx2.yourprovider.com.

; Sending authentication
yourbusiness.com.        TXT  "v=spf1 include:_spf.yourprovider.com ~all"
default._domainkey.yourbusiness.com. TXT "v=DKIM1; k=rsa; p=MIGfMA0GCSq..."
_dmarc.yourbusiness.com. TXT  "v=DMARC1; p=none; rua=mailto:dmarc@yourbusiness.com"

MX records govern where *inbound* mail to @yourbusiness.com lands; SPF, DKIM and DMARC govern whether *outbound* mail sent as @yourbusiness.com is trusted by receivers. Both halves are required and commonly confused - a correctly configured MX with no SPF/DKIM/DMARC means you can receive mail fine while everything you send gets filtered.

Comparing the setup effort across routes

The deliverability outcome across the paid custom-domain options converges once all four record types are correctly set - the provider matters less than whether setup actually included DMARC, which most onboarding flows don't configure by default.

Once a custom domain's authentication is in place, MailPilot warms the mailbox over OAuth (Gmail, Outlook) or SMTP/IMAP, checks SPF/DKIM/DMARC against what's actually published, and tracks reputation daily - useful specifically for the free-or-low-cost setups where DNS configuration is easy to get half-done.