Definition
A free email domain means an email address at a domain name that costs you nothing to use. The honest answer to "can I get an email domain free" is: sometimes the mailbox is free, while a domain name you own is a registration you pay for and renew.
The domain is the part of an address after the at sign. An email account at a domain someone else registered, such as a webmail address or a free subdomain, is free because the email provider owns the name. A mail account at a name you register is yours, and that registration is paid.
The phrase also has a second, narrower meaning in B2B marketing. A list of free email domains is the set of consumer webmail domains, such as gmail.com or yahoo.com, that lead forms and scoring rules treat differently from company domains. This page covers both meanings.
For a side project, the difference between the two kinds of address barely matters. For outbound sales it decides whether your mail authenticates, whether replies reach you, and whether the mail systems at Gmail, Yahoo and Outlook accept the message at all.
Can you get an email domain free?
Yes, in three narrow ways, and no if you mean a free name of your own. You can create a free email account on a domain the provider owns. You can create one on a free subdomain under someone else's registered name.
The third way is the useful one for a business: a free email plan, running on a custom domain you registered and pay to renew yourself. The mail service costs nothing. The domain name does not.
What you cannot count on is the registration of a name like yourcompany.com at no cost and with no strings. ICANN describes an accredited registrar as an entity that offers domain name registration services to registrants of a generic top-level domain with direct access to the registries.
ICANN adds that the relationship between a registrant and an accredited registrar is governed by a registration agreement between the two. Bundled offers exist, where a hosting or website plan includes a name for a first term, but the name is paid for inside the plan rather than given away.
Free email account on someone else's domain: easy to get. Free email account on your own custom domain: available on some small free plans. Free domain name with no plan attached: rare, restricted, and the wrong foundation for outbound email.
The five things people mean by a free email domain
Search results for this phrase mix categories of providers that behave very differently once you try to send mail. Sorting them first saves a migration later.
| What is free | What you get | Who owns the domain | Fit for outbound sales |
|---|---|---|---|
| Consumer webmail account | An email address at the provider's own domain | The provider | Poor: you cannot authenticate a third-party sender |
| Shared-pool vanity domain | An email account on one of the provider's many brand-style domains | The provider | Poor: the name is not your business |
| Free subdomain service | A name under a parent domain that a registry or project holds | The parent domain holder | Weak: control is shared and can be withdrawn |
| Free email plan on your own custom domain | A small number of email accounts, limited storage and features | You, through a registrar | Workable, within the free plan's limits |
| Domain bundled with a paid plan | A registration included for a first term of web hosting or a website builder | You, but billed inside the plan | Workable, if renewal terms are clear |
Only the last two rows put your business name in the email address and your hands on the DNS zone. That is the line that matters for everything below, because authentication is published in DNS by whoever controls the domain.
What a domain actually costs to own
A domain registration is not a one-time purchase. It is a term you renew, every year or every few years, and when you stop renewing, the name leaves your control on a published schedule.
ICANN's Expired Registration Recovery Policy sets out that schedule for generic top-level domains. Registrars must notify the registrant of an upcoming expiration at least two times before it happens, roughly one month and one week ahead, and send a further notice within five days after expiration.
For registrations deleted within eight days of expiration, the registrar must interrupt the DNS resolution path the registrant specified. Except for sponsored top-level domains, registries must then offer a redemption grace period of 30 days after deletion, during which the registration can be restored.
The same policy says registrars must make their renewal, post-expiration renewal and restore fees reasonably available at the time of registration. That is where to look before you commit a sending domain to a registrar.
Registration and renewal prices differ by registrar, by top-level domain and by promotion, and they change. This page does not quote any. Compare the renewal price, not the first-term offer, before you commit a sending domain to it.
The practical cost of a domain is therefore the renewal, plus whatever mail plan sits on top, plus the attention to keep both from lapsing. An expired sending domain takes your replies and your bounce reports down with it.
Free email domain for business: where the free plans stop
On this page, a free email domain for business means a free email plan on a custom domain you registered. Those free plans are real and they work. They are also designed to be outgrown, so read the plan's feature list against the work you need it to do.
- User count. A cap on how many email accounts the free plan lets you create, sometimes with no room for aliases per person.
- Storage. A per-user mail storage allowance that attachments fill faster than people expect.
- Protocol access. Desktop clients and sync may need a paid plan on some services, because IMAP and SMTP access is a feature providers can choose to charge for.
- Domains. One custom domain only, which blocks the pattern of a separate sending domain for outreach.
- Admin controls. Routing rules, retention, audit logs and group addresses may sit above the free line.
- Support. Community forums rather than a ticket queue, which matters on the day email stops flowing.
None of that is a reason to avoid a free plan for a first business email account. It is a reason to check the two limits that break outbound work specifically: whether you can add a second domain, and whether the free plan gives you SMTP and DKIM signing for your own business domain.
A free trial is not a free plan
Some articles list a business suite's free trial next to genuinely free plans. They are different things. A trial lets a business create professional email accounts on its own domain and test the features, then asks for a subscription when the trial period ends.
That is a reasonable way to choose a paid business email service, and Google's own help points businesses that need to send as a custom domain toward Google Workspace. Just plan for the trial ending: the accounts, the DNS records and the sending reputation you build during it all belong to a paid plan afterward.
Free email hosting bundled with a website plan
The other common route to a free business email address runs through a website. Web hosting companies and website builders bundle a domain registration and a number of email accounts into one plan, and the email feels free because it carries no separate line on the invoice.
- Web hosting plans. Many shared hosting plans include email accounts at the hosted domain, set up in the hosting control panel.
- Website builders. A website builder plan may include a domain and one or more professional email addresses, sometimes through a partner email service.
- Registrar bundles. A registrar may include an email account, or only a forwarder, with each domain it registers.
- Standalone free email plans. A mail provider may run a free plan on a domain you bring, with a low user count and reduced features.
For a business that needs a website anyway, that is an efficient way to set up custom domain email. Check two features before you rely on it: SMTP sending with DKIM signing for your own domain, and whether the domain is included past the first year or only as an introductory offer.
In every one of these cases the mail service is tied to the plan. Cancel the hosting and the email accounts go with it, so a business that expects to move its website keeps mail where it can be kept. Check the export path before you create the first account.
What free mailbox providers say about business sending
Free consumer mailboxes come with terms, and those terms speak directly to outbound sales. The lines below were read on each provider's own help and terms pages on Oct 1, 2026. Terms change, so read the current version before you plan around them.
- Gmail. Google's Gmail Program Policies say not to use Gmail to distribute spam or unsolicited commercial mail, and not to automate the Gmail interface in a way that misleads or deceives users.
- Outlook.com. The Microsoft Services Agreement says not to send spam, and defines spam as unwanted or unsolicited bulk email, postings, contact requests, text messages or similar communications.
- Yahoo Mail. Yahoo's Terms of Service prohibit sending unsolicited emails, and bar commercial activity on non-commercial properties or high volume activity without Yahoo's prior written consent.
- Proton Mail. Proton's terms prohibit spam, bulk email to people who have not agreed to be on the list, and operating a large number of free accounts for one organization or individual.
Google adds a caution worth repeating to any sales team: your definition of unsolicited or unwanted mail may differ from your recipients' perception. A free consumer account is licensed for personal mail first, and a sequence of cold messages is exactly the use these terms describe.
Two account rules also matter for a business that keeps a free mailbox as a reply address. Microsoft says you must sign in at least once in a two-year period to keep the account active. Proton says it may suspend or delete free accounts inactive for 12 consecutive months.
Sending limits on free accounts, as each provider states them
| Provider | What its own help page says | What it means for outreach |
|---|---|---|
| Gmail, free account | More than 500 recipients in a single email, or more than 500 emails sent in a day, can trigger a sending limit; you should be able to send again within 1 to 24 hours | A consumer ceiling, not a sequence plan |
| Outlook.com | For Microsoft 365 subscribers: 5,000 daily recipients, 500 recipients per message, 1,000 daily non-relationship recipients; lower for non-subscribers; new accounts start on a low quota | A cold prospect is, by Microsoft's definition, a non-relationship recipient |
| Yahoo Mail | Yahoo does not disclose the number of recipients or emails that can be sent at one time; for regular bulk email it suggests a third-party bulk email option | No published number to plan against |
| Proton Free | 50 emails an hour and 150 emails a day; ten recipients on one email count as ten emails; Proton says it is not designed for bulk mailing | Too small for any sequence |
Microsoft defines a non-relationship recipient as someone you have never sent email to before. Every first touch in a cold sequence fits that definition, which is why the per-day figure that matters for outreach is the smaller one.
Using Gmail with your own domain for free, and why that path is closing
A popular free setup pairs a forwarding service on your own domain with a free Gmail account: mail to your domain is forwarded into Gmail, and Gmail's "Send mail as" feature sends replies as your custom address. Google's own help pages describe both how this works today and its end date.
Gmail's help says you can send mail as another address you own, and for a work or business address you enter that provider's SMTP server and account. It also warns that recipients using Outlook or another service may see the Gmail address shown as sending on behalf of the other address.
The bigger change is dated. Google says that starting January 2027, Gmail will no longer support "Send as" for third-party email accounts, on the web or in the mobile apps. Gmail-to-Gmail aliases and Google Workspace "Send as" are not affected.
Google describes Q3 to Q4 2026 as a transition period in which the feature keeps working but Gmail may restrict new configurations. Forwarding mail from another provider into Gmail keeps working, because it does not depend on "Send as".
For a business that relies on "Send as", Google's help recommends a desktop mail client with IMAP and SMTP support, the third-party provider's own interface, or Google Workspace for a custom domain.
Read that as the sending half of the free pairing going away: receiving can stay free, while sending as your domain moves to a real mail account.
Free email domain versus a business domain
The comparison below is about control, not about brands. A business domain here simply means a name your business holds the registration for, with a mail service attached.
| Compared | Free provider domain | Your own business domain |
|---|---|---|
| Address shape | [email protected] or [email protected] | [email protected] |
| DNS control | None: the provider publishes the records | Yours: you publish MX, SPF, DKIM and DMARC |
| Third-party sending | Cannot be authorized for the provider's domain | Authorized by adding the sender to SPF and DKIM |
| DMARC alignment | Fails for anything the provider did not send | Passes when the sending service is set up correctly |
| Terms of use | A consumer agreement that bars unsolicited commercial mail | The business plan you chose, plus the law |
| Portability | Change providers, change every email address | Move the mailboxes, keep the addresses |
| Replies and bounces | Land in the free mail account, if it still exists | Route to a mailbox your team works, through your MX records |
For an inbox that only receives, the left column is fine. For a business that sends into other businesses, the right column is the only one that satisfies what receiving providers now ask for.
What a professional email address gives a business
A professional email address is an email account at your company's own domain, created for a person or for a function. The case for it is not aesthetics. Every control an email sender needs sits on the domain, and a free webmail account has none of them.
| What a business wants | Free webmail account | Professional email on a custom domain |
|---|---|---|
| Brand in the email address | The provider's brand | Your business name |
| Add new email accounts | A separate signup each time | Add a user from the admin console |
| Joiners and leavers | The account belongs to the person | The business keeps the mailbox and its history |
| Aliases and group addresses | Limited or absent | Role addresses routed to whoever covers them |
| Outbound features | Consumer sending limits | SMTP for a sending tool, signed with your own DKIM key |
| Website and email together | Unrelated | One business domain behind the website and the email |
None of this requires a large plan. A free email plan on a domain you own delivers much of a professional setup, so the useful question is not whether the email is free. It is whether the plan lets your business publish DNS records and create the accounts it needs.
Why gmail.com and outlook.com addresses hurt B2B outreach
Two separate problems sit behind the same address. One is how the email is judged by a machine. The other is how it is judged by a buyer who sees the From line before the subject.
The mechanical problem
Outbound teams send through a sequencing tool, an email API or a shared platform. That service is not on the free email provider's list of authorized senders and cannot sign with the free provider's DKIM key, because it does not control the domain.
RFC 7489, the DMARC specification, defines a domain owner as an entity or organization that owns a DNS domain, and explains that "owns" means it holds the registration. You do not hold the registration of gmail.com or outlook.com, so you cannot publish anything for it.
The human problem
A free webmail address also tells the reader that the business has no custom domain, or chose not to use it. In this page's view, that is a weak first signal in a cold email to a buyer deciding whether you are a real supplier, and the message may not get the reading it deserves.
Sending tools and deliverability vendors publish inbox placement and reply rate figures measured on their own users. This page quotes none of them. Measure your own bounce, reply and complaint rates per sending domain, before and after you move off a free address.
What Gmail, Yahoo and Outlook require from every sender
Google, Yahoo and Microsoft each publish sender requirements for mail sent to their consumer mailboxes. A domain you control can meet them. A free provider's domain, used through someone else's sending service, cannot.
| Requirement | Google, Gmail | Yahoo | Microsoft, Outlook.com |
|---|---|---|---|
| Who it covers | Mail sent to personal Gmail accounts, ending in @gmail.com or @googlemail.com | Mail to Yahoo domains | Mail to the consumer service: outlook.com, hotmail.com and live.com |
| All senders | SPF or DKIM; valid forward and reverse DNS; TLS; spam rate below 0.3%; RFC 5322 formatting | SPF or DKIM at a minimum; spam rate below 0.3%; valid forward and reverse DNS | Not split out; the announcement targets high volume domains |
| Volume threshold | More than 5,000 messages a day to personal Gmail accounts | Bulk senders | Domains sending more than 5,000 emails a day |
| Authentication above it | SPF and DKIM, plus DMARC; the DMARC policy can be set to none | SPF and DKIM; a valid DMARC policy of at least p=none, and DMARC must pass | SPF and DKIM must pass; DMARC at least p=none |
| Alignment | For direct mail, the From domain must align with the SPF domain or the DKIM domain | From aligned with SPF or DKIM; relaxed alignment is acceptable | Align with SPF or DKIM, preferably both |
| Unsubscribe | Above the threshold, one-click unsubscribe plus a visible link for marketing and subscribed messages | One-click list-unsubscribe and a visible link; honor unsubscribes within 2 days | A functional, clearly visible unsubscribe link |
Google also tells every sender not to impersonate Gmail From headers, and says Gmail will begin using a DMARC quarantine enforcement policy. Its display name guidelines list using an @gmail.com domain as the display name for bulk email as a form of spoofing.
Microsoft's guidance adds that the From or Reply-To address should be valid, reflect the true sending domain, and be able to receive replies. Read that against a free webmail address sent through an outreach tool: the From line does not reflect the true sending domain.
One scope note for B2B. Google's sender guidelines FAQ says the guidelines and Google's enforcement apply only to mail sent to personal Gmail accounts, not to Google Workspace accounts. Treat the published rules as a floor for any prospect's mailbox, not as the whole test.
DMARC rejection of free-domain sending
DMARC is what turns "your From line is wrong" into a delivery decision. Under RFC 7489, a message has identifier alignment when the domain in its From address matches a domain validated by SPF or DKIM, in relaxed or strict mode.
Your outreach tool is not in the free email provider's SPF record and holds none of its DKIM keys. So both checks either fail or return a soft result, alignment is never reached, and the recipient's server applies whatever policy the provider published.
RFC 7489 defines those policies. With none, the domain owner requests no specific action. With quarantine, failing mail is treated as suspicious, which can mean the spam folder. With reject, the owner wants failing mail rejected, preferably during the SMTP transaction.
What those providers actually publish
We ran the lookups ourselves against a public resolver on Oct 1, 2026. The records below are what receivers found on that date, and providers do change them.
| Domain | DMARC policy found | End of the SPF record | Effect on unauthorized sending |
|---|---|---|---|
| gmail.com | p=none, sp=quarantine | ~all, a softfail | No policy action on the domain itself, but no pass either, and Google says Gmail will begin using quarantine enforcement |
| yahoo.com | p=reject, pct=100 | ?all, neutral | Requested disposition is rejection |
| aol.com | p=reject, pct=100 | ?all, neutral, same SPF host as Yahoo | Requested disposition is rejection |
| outlook.com | p=none, sp=quarantine | -all, a fail | SPF fails outright; subdomains are quarantined |
| hotmail.com | p=none | -all, a fail | No pass, and Microsoft junks non-compliant high volume mail |
| icloud.com | p=quarantine, sp=quarantine | ~all, a softfail | Requested disposition is quarantine |
The qualifiers come from RFC 7208: a plus is a pass, a minus is a fail, a tilde is a softfail and a question mark is neutral. None of those is the pass that DMARC alignment needs, because your tool is not one of the hosts the record authorizes.
Microsoft's announcement is the blunt version. Non-compliant email from domains sending more than 5,000 a day goes to Junk first, and may eventually be rejected with a 550 5.7.515 access denied response naming the sending domain.
A note on the standard itself. RFC 9989, published in May 2026, obsoletes RFC 7489 and keeps the core rule: a DMARC pass needs an SPF or DKIM pass on a domain aligned with the author domain. It also retires the pct tag, which some providers still publish.
RFC 9989 warns in the other direction too: a DMARC pass by itself does not guarantee that delivery to the inbox would be safe or desirable. Authentication buys you eligibility, not placement. For the rest of that picture, see email deliverability.
Free subdomains and shared domains carry someone else's record
A free subdomain looks like a middle path: your own word in front of a name you did not register. For receiving email it can work. For sending, several things follow from how DMARC handles domain hierarchy.
- The organizational domain is not yours. RFC 7489 defines it as the domain that was registered with a registrar, and relaxed alignment compares organizational domains, so your subdomain is judged against a parent you do not control.
- The parent's subdomain policy can apply. If no DMARC record exists at your subdomain, receivers query the organizational domain, whose sp tag sets the policy for its subdomains.
- Volume is counted together. Google's FAQ says messages sent from the same primary domain count toward its 5,000 a day bulk sender threshold, so a parent name's traffic is not split per subdomain.
- Control can be withdrawn. The holder of the parent registration can change or remove your subdomain, and your addresses go with it.
The same logic applies to a shared-pool domain, where a provider offers email accounts across many brand-style names. The address may read better than a webmail one, but the DNS zone still belongs to the provider.
Free forwarding is the receiving half
A popular free option is email routing at a DNS provider: point the custom domain's records at the service, and email to an address at your domain is forwarded into an email account you already have. It is free and useful.
It is also only half of an email service. Cloudflare's documentation describes Email Routing, for handling incoming emails, as available on Free and Paid plans, and lists Email Sending for outbound transactional emails as a beta on its Workers Paid plan.
Treat routing as incoming mail, not as a mail sender for outreach. If you reply from the forwarded-to mailbox, the reply leaves with that mailbox's domain in the From line, which is the free-provider address you were trying to avoid.
Registrar bundles can behave the same way. An included email address is sometimes a forwarder rather than a real email account, so check whether the offer includes SMTP sending and DKIM signing before you build a sequence on it.
Setting up a real sending domain
The six steps below are the setup this page recommends for outbound teams: keep the corporate domain for normal business email, and set up a separate registered custom domain for sequences, so a problem in one does not touch the other.
Step one: register a name you will keep
Choose a name close to the business brand, register it through an accredited registrar, and note the renewal date and renewal fee rather than the introductory offer.
Step two: create the mail accounts
A free email plan is acceptable if it gives you a real account, SMTP sending and DKIM signing for your custom domain. Forwarding alone is not enough.
Step three: publish MX, SPF, DKIM and DMARC
One SPF record listing every mail service that sends for the domain, DKIM keys from each of them, and a DMARC policy record at the _dmarc name.
Step four: point replies at a human
Make the From and Reply-To addresses deliverable and read daily, so answers and bounce notices reach a person instead of vanishing.
Step five: warm the domain before volume
Send low volume mail to engaged recipients first, as covered in email warm up, then raise sending gradually. Google's guidelines also advise increasing volume slowly.
Step six: verify from outside
Send to an account at a different mail provider, open the headers, and confirm SPF, DKIM and DMARC all report a pass before the first sequence.
Two SPF rules from RFC 7208 are easy to break in step three. A domain must not have multiple records that would select more than one SPF record; if it does, the check returns permerror. And the include, a, mx, ptr and exists terms, plus redirect, are limited to 10 DNS lookups per evaluation.
{{sendingDomain}}. IN TXT "v=spf1 include:{{mailProvider}} include:{{sendingTool}} -all" {{selector}}._domainkey.{{sendingDomain}}. IN TXT "v=DKIM1; k=rsa; p={{publicKey}}" _dmarc.{{sendingDomain}}. IN TXT "v=DMARC1; p=none; rua=mailto:{{reportAddress}}"
This example was written for this page. The values in braces come from your own providers, never from an article, and the DKIM selector is whatever your mail service tells you to publish. Google requires a DKIM key of 1024 bits or longer for mail to personal Gmail accounts and recommends 2048 where supported.
Which mailboxes to create on the new domain
A free email plan caps the number of users a business can create, so the addresses you choose matter. RFC 2142 defines mailbox names for common business functions, and some of them are worth having on a sending domain from the first day.
| Address | Function in RFC 2142 | Why an outbound team wants it |
|---|---|---|
| postmaster | SMTP; the mail standards require it | Gives other mail administrators the standard place to reach you |
| abuse | Customer relations, for inappropriate public behavior | Gives recipients a standard place to complain to you directly |
| info | Marketing, for packaged information about the business | A neutral inbox for replies that are not for one rep |
| sales | Sales, for product purchase information | Catches answers when the named rep has left |
| A named person | Not in the RFC: the actual sender of your sequences | People reply to people, and Microsoft wants a From address that can receive replies |
| A DMARC report address | Not in the RFC: receives aggregate reports | Shows which services are sending as your domain |
If the free plan lets you create fewer email accounts than that, use aliases into one inbox for the role addresses and reserve real accounts for the people who send. In this page's view, a role address that bounces is worse than no role address.
Free email domains in lead forms and lead scoring
Marketing teams meet the phrase from the other side: a free email domain list used to keep consumer webmail addresses out of B2B lead forms. Two platforms document this as a setting, and both describe the trade-off in their own words.
- LinkedIn Lead Gen Forms. LinkedIn Help says a work email field can use Validate work email, which blocks the most commonly used free email domains, such as Hotmail, Yahoo and Gmail. It does not block every domain, and submission rates might decrease.
- HubSpot forms. HubSpot's Knowledge Base describes a Block free email providers setting, per form or account wide. A visitor who enters a blocked domain is asked for a different address before the form submits.
HubSpot publishes the list behind its setting and says free email domains are regularly monitored, so some blocked domains may not appear on the list yet. Its page also says disposable email domains are blocked by default whether or not the free provider setting is on.
On Oct 1, 2026, HubSpot's published list included gmail.com, googlemail.com, yahoo.com, aol.com, outlook.com, hotmail.com, live.com, icloud.com, proton.me, protonmail.com, mail.com, gmx.com and yandex.com. Any list like this is a snapshot that its owner keeps changing.
This page gives no figure for how many leads use free addresses or how they convert. Neither LinkedIn nor HubSpot publishes one in the pages cited. Count it in your own CRM, by source, before deciding to block.
Blocking is a lead quality decision, not a deliverability one. A founder, consultant or sole trader may run the business from a webmail address, so a free domain is a reason to check the lead, not proof it is a bad lead.
A company domain is not automatically clean either. A domain that accepts every address, a catch-all email domain, cannot be verified mailbox by mailbox. Both cases belong in your email hygiene routine rather than in a single yes or no rule.
When a lead with a free address replies and loops in a colleague, read the copy line: a company domain there can tell you which account the thread belongs to. The email CC entry covers who sees what once a thread grows.
What the law expects in the From line
In the United States, the FTC's compliance guide for the CAN-SPAM Act sets rules that touch the domain question directly. The guide says the law covers all commercial messages and makes no exception for business-to-business email.
- Accurate headers. The From, To, Reply-To and routing information, including the originating domain name and email address, must be accurate and identify who initiated the message.
- Honest subject lines. The subject must accurately reflect the content of the message.
- A physical postal address. The message must include a valid postal address for the sender.
- A clear opt-out. An opt-out request must be honored within 10 business days, and the opt-out mechanism must work for at least 30 days after you send.
- Your responsibility stays yours. Hiring another company to handle your email does not contract away the legal responsibility to comply.
Sending from a free mailbox is not itself unlawful. Sending in a way that makes the originating domain unclear, or that leaves an opt-out request with nobody to read it, walks toward the parts of the rule that are. Gmail's policies separately bar using Gmail to send in violation of CAN-SPAM.
When a free plan is genuinely enough
Not every use of email needs a sending domain with its own reputation. A free plan can carry a real business for a long time, and moving early can cost a small business more attention than it returns.
Forwarding a handful of website email addresses into one mail account is cheap, reliable and needs no outbound setup at all.
A free email plan on your own custom domain covers a founder writing individual emails to people who expect them, with authentication in place.
Operations, finance or support accounts write mostly to people who already know your business, which is the easiest mail to deliver.
The moment a tool sends on your behalf to strangers, you need a domain you control and records you publish.
The upgrade trigger worth watching is not mail storage. It is the first sequence, the first extra sending domain, or the first time a prospect says your email landed in spam. That is also when outbound lead generation starts to depend on the setup.
How to compare free plans without a vendor list
This page ranks no providers. Instead, here are the questions that separate a free plan you can build outbound on from one you will abandon in a quarter. Ask them of any provider before you point DNS at it, whatever its feature list says.
- Does it sign my domain with DKIM? If the free plan signs only with the email provider's domain, alignment depends entirely on SPF.
- Can I add a second domain? A one-domain limit blocks the separate sending domain pattern before you start.
- Do I get SMTP and IMAP? Without those features you cannot connect a sequencing tool or a desktop mail client.
- Can I still publish my own records? If the provider requires its own MX hosts, confirm you can still publish your own SPF and DMARC.
- What do the terms say about business use? Read the acceptable use or anti-spam section, not just the feature page.
- What happens at the cap? Find out whether mail queues, bounces or silently drops when a sending limit is hit.
- Can I export? A free plan without mail export is a migration your business pays for later.
Symptoms that point back to the domain
| Symptom | Likely cause | Fix |
|---|---|---|
| Sequences land in spam from day one | Sending as a free email provider's domain through a third-party tool | Move the From address to a domain you registered and authenticate it |
| Bounce says 5.7.515 access denied | The sending domain does not meet Microsoft's authentication level | Publish SPF, DKIM and DMARC for the actual sending domain |
| Bounce says 5.7.26 | Google could not authenticate the message with SPF or DKIM | Authenticate the sending domain; check the tool is in SPF and signs with DKIM |
| Some receivers accept, one rejects everything | The From domain publishes p=reject and you are not an authorized sender | Stop sending as that domain; use your own |
| Authentication results show permerror | Two SPF records on the same domain, or more than 10 lookups | Merge every sending service into one SPF record and trim includes |
| "You have reached a limit for sending mail" | A free Gmail account passed its daily sending limit | Stop; a consumer account is not a sending platform |
| Replies never arrive | The free address forwards but the account was abandoned, or MX is missing | Route replies to a monitored email account and verify the MX lookup |
| Everything breaks on the same date | The registration lapsed and the resolution path was interrupted | Set renewal reminders and keep the registrar contact address reachable |
Mistakes with free email domains
- Running outbound sequences from a free webmail address and blaming the copy when no email lands.
- Building a business on Gmail "Send as" for a third-party address after Google dated its end.
- Assuming a free forwarding service lets you send mail, then replying from the personal account behind it.
- Picking a free email plan that allows one custom domain, then needing a separate sending domain a month later.
- Taking the first-term offer for the real cost and losing the business domain at renewal.
- Publishing a second SPF record for a new tool instead of adding it to the existing one.
- Choosing a free subdomain and inheriting a parent domain's policy and control.
- Blocking every free email domain on a lead form without first checking how those leads perform.
- Leaving the sending domain unable to receive mail, so replies and bounces disappear.
Getting the domain decision made
In many teams the block is not technical. Someone has to agree to register a custom domain and set up its mail before sales outreach can start. The note below makes the case in the terms that decide it, and pairs with the email campaign checklist.
Subject: A sending domain before {{campaignName}} goes out Hi {{decisionMaker}}, As things stand, our first sequence would leave from {{currentAddress}}. That address sits on a domain we do not control, so we cannot authorize {{sendingTool}} to send for it, and the receiving server has no way to tie the message to us. What that costs us: messages filtered or refused before anyone reads them, and replies landing in a mailbox nobody works. The fix is {{proposedDomain}}, registered in our name, with MX, SPF, DKIM and DMARC published, replies routed to {{replyMailbox}}, and a warm-up period before {{startDate}}. Can you approve the registration this week, or point me to whoever should? {{senderName}}
The note opens with the acronyms instead of the consequence, so the reader files it as an IT ticket and it waits.
It also backfires when the proposed domain looks nothing like the company, because prospects then read the address as a spoof. Lead with the business cost, and keep the name recognizable.
Frequently asked questions
Can I get an email domain free?
Partly. You can get a free mailbox on a domain the provider owns, a free subdomain under someone else's name, or a free mailbox plan on a domain you register. Registering your own name is a paid registration that you renew, not a free one.
What is an email domain?
The email domain is the part of an address after the at sign. It is a registered domain name, and its DNS records decide where incoming mail is delivered and which servers are allowed to send on its behalf.
Is a free email domain for business a good idea?
For a first mailbox on a name you own, yes, within the plan's limits. For outbound sequences, check two things before you commit: whether the free plan signs your domain with DKIM, and whether it lets you add a second sending domain.
What is the difference between a free email domain and a business domain?
Control. On a provider's domain you cannot publish DNS records, so a third-party sending tool can never be authorized. On a domain you registered you publish MX, SPF, DKIM and DMARC yourself, and you keep the addresses if you change provider.
How much does an email domain cost?
Prices are not quoted here, because they differ by registrar and top-level domain and change often. ICANN's policy requires registrars to make renewal fees reasonably available at registration, so compare the renewal cost, not an introductory offer.
Can I send cold email from a Gmail address?
You can write individual messages, but not run sequences through a tool. The tool is not authorized in gmail.com's SPF record and holds no DKIM key for it, so DMARC alignment fails. Gmail's Program Policies also say not to use Gmail for unsolicited commercial mail.
Why does my email fail DMARC when I send from a free provider's address?
Because DMARC needs an SPF or DKIM pass on a domain aligned with the From domain. Only the domain owner can publish those records, and RFC 7489 describes the domain owner as whoever holds the domain's registration.
Do free email domains hurt deliverability?
Sending as a free provider's domain from a third-party service does, because authentication cannot pass. A free mailbox plan on your own domain does not, as long as you publish SPF, DKIM and DMARC and keep your list clean.
What do Gmail, Yahoo and Outlook require from senders?
All three want SPF or DKIM at a minimum. Above 5,000 messages a day, Google and Microsoft want SPF, DKIM and a DMARC policy of at least p=none with alignment, and Yahoo asks the same of bulk senders. Google and Yahoo both ask for spam rates below 0.3%.
Can I use Gmail with my own domain for free?
For now, partly. Gmail can send as an address you own through that provider's SMTP server, but Google says "Send as" for third-party accounts ends in January 2027. Forwarding into Gmail keeps working; sending as your domain then needs a real mail account.
Does free email forwarding let me send email too?
No. Forwarding routes incoming mail to a mailbox you already have. Cloudflare's documentation, for example, offers Email Routing on free plans and lists outbound Email Sending separately, on a paid Workers plan. Replying from the forwarded-to mailbox puts that mailbox's domain in the From line.
How many emails can I send from a free Gmail account?
Google's help says more than 500 emails in a day, or more than 500 recipients on a single message, can trigger a sending limit, and that you should be able to send again within 1 to 24 hours. That is a consumer ceiling, not an outbound plan.
Should I block free email domains on lead forms?
It depends on who buys from you. LinkedIn and HubSpot both offer settings that block common free domains, and LinkedIn notes submission rates might decrease. Check how free-address leads perform in your own CRM before blocking, because some real buyers use webmail.
Should I use a separate domain for outreach?
This page recommends it. A separate registered domain, close to the brand, keeps sequence volume away from the corporate domain that carries invoices and contracts. It needs its own MX, SPF, DKIM, DMARC and warm-up before the first send.
- Google, Gmail Help, Email sender guidelines, for the requirements for all senders and for senders of more than 5,000 messages a day to personal Gmail accounts, the DKIM key length, the display name spoofing rule and the quarantine enforcement note, checked Oct 1, 2026.
- Google Workspace Admin Help, Email sender guidelines FAQ, for the rule that the guidelines apply only to mail sent to personal Gmail accounts and that messages from the same primary domain count together, checked Oct 1, 2026.
- Google, Gmail Help, Limits for sending and getting mail, for the 500 recipient and 500 email daily limits on a Gmail account and the 1 to 24 hour wait, checked Oct 1, 2026.
- Google, Gmail Help, Send emails from a different address or alias, for how "Send mail as" works with another provider's SMTP server and the "on behalf of" display, checked Oct 1, 2026.
- Google, Gmail Help, Learn about changes to third-party email account support in Gmail, for the January 2027 end of "Send as" for third-party accounts, the transition period and Google's recommended alternatives, checked Oct 1, 2026.
- Google, Gmail Program Policies, for the spam and bulk mail policy on unsolicited commercial mail and CAN-SPAM, checked Oct 1, 2026.
- Microsoft Support, Sending limits in Outlook.com, for the daily, per message and non-relationship recipient limits, the lower limits for non-subscribers and the low quota on new accounts, checked Oct 1, 2026.
- Microsoft Services Agreement, effective Sep 30, 2026, for the definition of spam in the code of conduct and the two-year sign-in rule for keeping an account active, checked Oct 1, 2026.
- Microsoft Defender for Office 365 Blog, Strengthening Email Ecosystem: Outlook's New Requirements for High-Volume Senders, Microsoft's own announcement for the 5,000 a day threshold, the SPF, DKIM and DMARC requirements, the From or Reply-To guidance, the Junk then reject behavior and the 5.7.515 response, checked Oct 1, 2026.
- Outlook.com Postmaster, Announcements, for Microsoft's confirmation of the high volume sender requirements on its own postmaster site, checked Oct 1, 2026.
- Yahoo Help, Limits on sending email in Yahoo Mail, for Yahoo not disclosing its sending limits and its suggestion of a third-party option for bulk email, checked Oct 1, 2026.
- Yahoo Terms of Service, for the anti-abuse policy on unsolicited email, commercial activity and high volume activity, checked Oct 1, 2026.
- Yahoo Sender Hub, Best practices, for Yahoo's authentication, alignment, spam rate, reverse DNS and unsubscribe requirements, checked Oct 1, 2026.
- Proton Support, Proton Mail sending limits, for the Proton Free hourly and daily sending limits, the recipient counting rule and the note that Proton Mail is not designed for bulk mailing, checked Oct 1, 2026.
- Proton Support, Proton plans explained, for what Proton Free includes and which plans list custom email domain support, checked Oct 1, 2026.
- Proton Terms of Service, last modified June 23, 2026, for the rules on spam, bulk email, multiple free accounts and inactive free accounts, checked Oct 1, 2026.
- LinkedIn Help, Lead Gen Form fields, for the Validate work email option that blocks commonly used free email domains and its effect on submission rates, checked Oct 1, 2026.
- HubSpot Knowledge Base, Block form submissions from specific email domains or free email providers, for how the setting works per form and account wide, checked Oct 1, 2026.
- HubSpot Knowledge Base, Domains blocked from form submissions, for HubSpot's published free email domain list, its monitoring note and the default blocking of disposable domains, checked Oct 1, 2026.
- RFC 7489, Domain-based Message Authentication, Reporting, and Conformance (DMARC), for the definitions of domain owner, identifier alignment and organizational domain, relaxed and strict mode, the p and sp policies and policy discovery, checked Oct 1, 2026.
- RFC 9989, Domain-Based Message Authentication, Reporting, and Conformance (DMARC), for its May 2026 replacement of RFC 7489, the pass and alignment rule, the removal of the pct tag and the note that a DMARC pass does not guarantee inbox delivery, checked Oct 1, 2026.
- RFC 7208, Sender Policy Framework (SPF), for the qualifiers pass, fail, softfail and neutral, the rule against multiple SPF records and the 10 DNS lookup limit, checked Oct 1, 2026.
- RFC 2142, Mailbox Names for Common Services, Roles and Functions, for the postmaster, abuse, info and sales mailbox names, checked Oct 1, 2026.
- ICANN, Registrars, for the definition of an accredited registrar and the registration agreement between registrant and registrar, checked Oct 1, 2026.
- ICANN, Expired Registration Recovery Policy, for the expiration notices, the interruption of the DNS resolution path, the 30 day redemption grace period and fee disclosure, checked Oct 1, 2026.
- Cloudflare Developer Docs, Email Service, for Email Routing of incoming mail on Free and Paid plans and Email Sending as a separate beta on the Workers Paid plan, checked Oct 1, 2026.
- Federal Trade Commission, CAN-SPAM Act: A Compliance Guide for Business, for the coverage of business-to-business email and the header, subject line, postal address, opt-out and third-party responsibility rules, checked Oct 1, 2026.
- The DMARC and SPF records quoted for gmail.com, yahoo.com, aol.com, outlook.com, hotmail.com and icloud.com come from our own DNS lookups against a public resolver on Oct 1, 2026. Providers change these records, so check them yourself before relying on them.
- Jeluvi entries this term builds on: MX records, email hygiene, catch-all email, lead quality, email warm up.
- No provider is ranked, recommended or paid for on this page, and no prices are quoted. Free plans, terms and their limits change; read the provider's current terms.