Segmenting an Email List by Mailbox Provider, Using MX Records

To segment a list by mailbox provider, group each address by who hosts the mailbox, which you find from the domain's MX record, not from the domain name. That gives you buckets such as personal Gmail, Google Workspace, Outlook.com, Microsoft 365, Yahoo, Apple iCloud and "behind a gateway". Each provider scores your mail independently, publishes its own sender rules and offers its own reporting tool, so a provider segment is what lets you notice a problem at one of them and slow down there without pausing everything.

Consumer domains are easy, because gmail.com is always Google. Business domains are where the method earns its keep: acme.com tells you nothing until you look up where its mail goes.

Why provider segments are worth the effort

Mailbox providers do not share reputation, so your mail can be fine at one and failing at another on the same day. A single blended bounce or open rate hides that. Three practical reasons to split:

1. Diagnosis. If bounces or deferrals jump, a provider breakdown tells you in one glance whether it is a list problem (spread across everyone) or a reputation problem at one provider (concentrated in one bucket). Each provider also words its rejections differently; see what Gmail, Outlook and Yahoo say when a mailbox doesn't exist.
2. Throttling. When one provider starts deferring with 4xx replies, you can reduce volume to that segment alone instead of to the whole send.
3. Different rules apply. The bulk sender requirements of Google, Yahoo and Microsoft overlap but are not identical, and they apply to their consumer mailboxes.

What the MX records actually say

The MX host is the reliable signal, and it separates consumer and business services from the same company. Here is what dig MX returned on 6 October 2026 (lowest-priority host shown):

Domain	MX host	Segment
gmail.com, googlemail.com	gmail-smtp-in.l.google.com	Personal Gmail
anthropic.com, netflix.com	aspmx.l.google.com	Google Workspace (legacy record set)
hubspot.com	smtp.google.com	Google Workspace (current single record)
outlook.com, hotmail.com	*.olc.protection.outlook.com	Consumer Outlook.com
microsoft.com	microsoft-com.mail.protection.outlook.com	Microsoft 365
yahoo.com, ymail.com	mta5.am0.yahoodns.net	Yahoo
aol.com	mx-aol.mail.gm0.yahoodns.net	Yahoo (AOL)
icloud.com, me.com	mx01.mail.icloud.com	Apple iCloud
salesforce.com, ibm.com	*.pphosted.com	Security gateway; real provider hidden

Two Google rows exist because Google's MX setup guide says "The Google Workspace MX record value is smtp.google.com", while domains set up before 2023 may still use records starting with aspmx, which "are still supported". Both mean Workspace. You can run any domain through the MX lookup tool.

The last row is the one people get wrong. A company whose MX points at a security gateway may well use Microsoft 365 or Google behind it, but the gateway is what accepts or rejects your mail first. For a measured look at how common that is among real companies, see Google Workspace vs Microsoft 365: MX records of 696 companies.

The segments that matter, and the tool for each

Each major provider gives senders a different, partial view of how your mail is doing, and none of them covers business mailboxes the way they cover consumer ones.

Segment	Reporting tool	What it covers
Personal Gmail	Google Postmaster Tools	Spam rate, reputation, authentication and delivery errors, for mail to personal Gmail only. Requires a verified domain
Google Workspace	None for senders	Not included in Postmaster Tools
Outlook.com	Microsoft SNDS	Data "about individual IPs" at Outlook.com; you must request access to IPs you are responsible for
Microsoft 365	None for senders	Each tenant's admins see their own filtering, not you
Yahoo and AOL	Yahoo Sender Hub	Complaint Feedback Loop for DKIM-signed mail from domains you register
Apple iCloud	Apple postmaster page	Guidance and a contact address, no dashboard

Google is explicit about the Workspace gap. Its Postmaster Tools setup page says: "Data in Postmaster Tools only applies to messages sent to personal Gmail accounts." It also warns that "Data might be missing if the total number of messages for a given day is too low." So a B2B sender whose list is mostly Workspace domains can see a healthy Postmaster dashboard built from a small slice of their mail. How to read it is covered in the Postmaster Tools guide.

SNDS works per IP address, not per domain, and access is for IPs you are responsible for. If you send through a shared IP pool at an email platform, that is the platform's job, so ask what it monitors.

Provider rules apply to the consumer segments

The well-known bulk sender requirements target consumer mailboxes, which is another reason to keep consumer and business segments apart.

• Gmail. Google's sender guidelines say they help you deliver "to personal Gmail accounts". Senders of more than 5,000 messages a day to Gmail accounts have extra requirements, and the spam rate reported in Postmaster Tools should stay "below 0.3%", with Google recommending under 0.10%.
• Yahoo. Yahoo's best practices ask all senders to keep the spam rate "below 0.3%" and require bulk senders to "Implement both SPF & DKIM", publish DMARC with at least p=none, and support one-click unsubscribe.
• Microsoft. Since 5 May 2025, Microsoft has required SPF, DKIM and DMARC for domains sending more than 5,000 messages a day to its consumer mailboxes.
• Apple. The iCloud postmaster page asks senders to use SPF and DKIM and to publish a DMARC policy.

Volume thresholds are counted per provider, so a provider segment is also how you know whether you are over one. The side-by-side detail is in Gmail and Yahoo bulk sender requirements and Microsoft Outlook's bulk sender requirements.

How to build the segments in a spreadsheet

Extract the domain, map the consumer domains by name, and look up MX only for the business domains that remain. This keeps the number of lookups small.

1. Extract the domain into a new column. In Excel or Google Sheets, with the address in A2:

   =LOWER(MID(A2, FIND("@", A2) + 1, 255))
   

2. Map consumer domains directly. gmail.com and googlemail.com to Personal Gmail; outlook.com, hotmail.com, live.com and msn.com to Outlook.com; yahoo.com, ymail.com and aol.com to Yahoo; icloud.com, me.com and mac.com to iCloud. Regional variants such as hotmail.co.uk or yahoo.co.uk belong with their parent, but check the MX for any you are unsure of.

3. List the unique remaining domains. On a B2B list this is usually far fewer rows than addresses, because many contacts share a company.

4. Look up the MX for each and map by suffix: google.com to Google Workspace, mail.protection.outlook.com to Microsoft 365, anything else to Other or Gateway.

5. Join the result back to the address rows with a lookup on the domain column.

Refresh the business-domain mapping every few months. Companies migrate between providers and add or remove gateways, and the MX record changes when they do.

Using the segments

Report every send by segment, and act on the one that moves. A practical routine:

• Track bounce rate, deferrals and complaints per segment, not only in total.
• Warm new domains or IPs per provider, starting with the segment where you have the best engagement.
• If one segment degrades, slow it alone. Reduce volume, send only to your most engaged recipients in that segment, and check that provider's tool before resuming.
• Verify before you send, because verification results also differ by provider. Personal Gmail rejects unknown mailboxes during the check, while some gateways and Microsoft 365 tenants accept every address and behave as catch-all. SimpleVerifier returns those as risky rather than valid, so the risky share of each segment is worth reading separately.

Practical takeaway

Segment by MX host, not domain name. Keep personal Gmail apart from Google Workspace and Outlook.com apart from Microsoft 365, because only the consumer side has sender dashboards and published bulk rules. Put gateway-fronted domains in their own bucket, report every send per segment, and when one provider pushes back, slow that segment rather than the whole list.