What Is an Email Domain Name?
An email domain is the part of an email address that appears after the @ symbol. In the address [email protected], the email domain is example.com. The email domain determines where messages are routed and is central to email authentication, branding, and deliverability.
How Email Routing Uses the Domain
When a sending mail server needs to deliver a message to [email protected], it does not connect to "example.com" directly. Instead, it follows this process:
- The sending server queries DNS for the MX (Mail Exchanger) records of example.com.
- DNS returns one or more MX records, each pointing to a mail server hostname with a priority value (e.g.,
10 mail.example.com). - The sending server connects to the highest-priority (lowest number) mail server via SMTP on port 25.
- If the first server is unreachable, it falls back to the next-priority MX record.
Without valid MX records, email cannot be delivered to a domain. Use our MX lookup tool to verify your domain's mail server configuration.
Free vs. Custom Email Domains
Free Email Domains
Services like Gmail (gmail.com), Outlook (outlook.com), and Yahoo (yahoo.com) provide free email addresses on their own domains. These are convenient for personal use but carry limitations for professional and business communication:
- You cannot control the domain's reputation or authentication policies.
- You cannot customize the domain portion of the address.
- Sending marketing email from a free domain violates most ESP terms of service and triggers spam filters.
Custom Email Domains
A custom email domain (e.g., [email protected]) requires owning a domain and configuring its DNS records:
- MX records pointing to your mail provider (Google Workspace, Microsoft 365, Fastmail, etc.).
- SPF records authorizing your provider's servers to send on your behalf. Validate with our SPF check tool.
- DKIM records for cryptographic message signing.
- DMARC records for policy enforcement and reporting.
Custom domains provide full control over your email authentication stack and build brand recognition with every message sent.
Common Email Domain Providers
| Provider | Domain Used | Setup |
|---|---|---|
| Google Workspace | Your custom domain | MX records point to Google's servers (aspmx.l.google.com, etc.) |
| Microsoft 365 | Your custom domain | MX records point to outlook.com servers |
| Fastmail | Your custom domain | MX records point to in1-smtp.messagingengine.com, etc. |
| Zoho Mail | Your custom domain | MX records point to mx.zoho.com, etc. |
Email Domain and Authentication
The email domain is the anchor for all authentication checks. When a receiver gets a message from [email protected]:
- SPF checks whether the sending IP is authorized for the envelope sender's domain.
- DKIM verifies the cryptographic signature against a public key published in the signing domain's DNS.
- DMARC checks that at least one of SPF or DKIM passes with alignment to the From header domain.
Mismatches between your email domain and your authentication records are one of the most common causes of deliverability problems. Run a full domain analysis to check all of these at once.
Stay on top of your email infrastructure. Sign up for the InboxTooling newsletter for deliverability tips, tool updates, and best practices.