Who Is My Email Provider? How to Tell Who Hosts It

If you're asking "who is my email provider" about an address on your own domain, the answer is whoever that domain's MX records point at. Read the MX hostname and you know who hosts your email: smtp.google.com means Google Workspace, a host ending in .mail.protection.outlook.com means Microsoft 365, and so on.

The quickest way to see it is to paste the domain into our free MX record checker, which puts a provider label next to each domain when it recognizes the host. And if the address ends in @gmail.com, @outlook.com, @yahoo.com or @icloud.com, you can skip all of this, because the provider is the brand after the @.

Below is how to read the answer, and the things it won't tell you.

Who is my email provider? Read the MX records

Most domains that receive mail publish MX records in DNS. Each record is a priority number plus a hostname, and that hostname belongs to whoever accepts mail for the domain. That's why MX is the record to read for an email provider lookup: a sending server reads the same record to decide where to deliver.

These are the hosts you'll run into most, with the labels the checker gives them:

The checker also knows Gmail (personal Gmail addresses), Namecheap Private Email and Postmark inbound. When it doesn't recognize a host, it shows the top-priority MX hostname instead, and that hostname usually gives the company away anyway. Something like mx1.someprovider.com is rarely a mystery.

If you see two different providers for one domain, it's most often a leftover from a move that never got cleaned up. The checker flags that with a warning, since senders can end up delivering to either one.

Consumer addresses vs custom domains

For a free consumer address, the answer is in the address. @gmail.com is Google, @outlook.com and @hotmail.com are Microsoft, @yahoo.com is Yahoo and @icloud.com is Apple. Only those companies host mail for their own domains, so there's nothing to look up.

A custom domain is different, because anyone can host its mail. you@yourcompany.com could live in Google Workspace, Microsoft 365, Zoho, a forwarding service, or something a previous developer set up and nobody remembers. So for any address on a domain you or a client own, check the MX.

The usual mix-up is the registrar. The company you bought the domain from, whose DNS panel you log into, isn't automatically your email host. A lot of registrars sell email too (Porkbun puts three email options behind one icon), and if you bought it from them, the MX points at their mail servers. If you didn't, the domain only has whatever MX someone added. Either way the MX answers it, and the registrar's name on the invoice doesn't.

What MX does not tell you

MX answers one question: which server accepts incoming mail for this hostname. A few things it leaves out:

• Who owns the domain and where it's registered. That's a WHOIS lookup.
• Who hosts the website. That's the A record, and it's often a different company than the mail host.
• Who sends mail as the domain. Sending is authorized with SPF and DKIM, so a domain can receive in Google Workspace while its receipts go out through Postmark or Resend, and MX shows none of that.
• Where the mail finally lands. MX names the first stop, which can be a forwarder or a filtering gateway that passes mail on to a mailbox somewhere else.

The last one is my own setup. beyondfolder.com receives through Cloudflare Email Routing, so the checker says Cloudflare Email Routing, which is correct. But Cloudflare only routes the mail, forwarding it to an inbox I already read. With a forwarding MX, the honest answer to "who hosts my email" is two companies.

Two results are easy to misread too. No MX at all doesn't prove nobody uses email there. Senders fall back to the domain's A record, and the address you have in mind might sit on a different hostname than the one you checked. A null MX (a single record of 0 .) is the opposite case: the domain is saying on purpose that it accepts no mail.

When you want a different host

Sometimes the lookup is step one of a change. You find out the domain is on Google Workspace, and what you actually wanted was a place to receive replies to your app's email, or an address for a new project.

My advice: if the current host works for the people using it, leave its MX alone. MX is looked up per hostname, so a subdomain like updates.yourdomain.com can point at a different host while yourdomain.com stays where it is. I wrote up how that works, with the records I run, in the guide to email on a subdomain. That's what I did on beyondfolder.com: the root still forwards through Cloudflare, and updates.beyondfolder.com is connected to Mailyond.

If you're picking a host for several domains at once, the costs stack up in a way they don't for one, and email hosting for multiple domains walks through the real options. Sending is a separate decision (which service signs mail for each domain), and how to send email from multiple domains covers that half.

Where Mailyond fits

If the lookup showed your domains spread across a few hosts and you're tired of checking each one, that's the problem Mailyond is built for. You connect each domain or subdomain with one 5-minute DNS setup (a DKIM TXT record, a Return-Path CNAME and an MX record), and the mail for every address on them comes into one inbox, tagged by domain. Replies go out from the address the message was sent to, and your app can send through a Resend-compatible API on the same domains.

Run a connected domain through the checker afterwards and it says Postmark inbound, because that's the infrastructure Mailyond receives on. So you'd see that label for my updates.beyondfolder.com too.

Plans start from $10/month: Basic is $10, Pro is $20 and Agency is $40 a month, and you can get started for free with a 7-day trial. If you only have one domain and its mailbox works, keep it. If you have several, you can start the trial and connect the first one.

FAQ

Who is my email provider?

For an address on your own domain, it's the company the domain's MX records point at. Look up the MX and match the hostname to a provider: smtp.google.com is Google Workspace, *.mail.protection.outlook.com is Microsoft 365. For a free address like @gmail.com or @outlook.com, it's the company in the address.

How do I find who hosts a domain's email?

Look up the domain's MX records, either in a terminal or with our free MX record checker, which shows a provider label when it recognizes the host and the top MX hostname when it doesn't. That's who receives the domain's mail. If it's a forwarder like Cloudflare Email Routing, the mail is passed on to a mailbox somewhere else.

Is my domain registrar my email host?

Usually not. The registrar sold you the name and may run your DNS, but your mail goes wherever the MX records point. If you also bought email from the registrar, the MX points at them, and the lookup shows that.

Does MX show who sends my mail?

No. MX only covers incoming mail. Who can send as your domain is set by SPF and DKIM, so a domain can receive in Microsoft 365 and send app email through a service like Postmark or Resend at the same time.

Can different hostnames on one domain use different email hosts?

Yes. MX is per hostname, so yourdomain.com can stay on Google Workspace while updates.yourdomain.com receives somewhere else. It's the safest way to add a new email host without moving the inbox people already use.