FFraudFree toolsMX lookup

Check where a domain's email goes.

Type a domain or an email address. The lookup shows its MX records in the order mail servers try them, the mail service each one belongs to, and what FFraud knows about the domain.

Mail for gmail.com

Gmail

5 MX records · the lowest number is tried first

  1. 5gmail-smtp-in.l.google.comGmail · Google LLC · 173.194.206.27 · AS15169
  2. 10alt1.gmail-smtp-in.l.google.comGmail · Google LLC · 142.250.100.26 · AS15169
  3. 20alt2.gmail-smtp-in.l.google.comGmail · Google LLC · 172.253.149.26 · AS15169
  4. 30alt3.gmail-smtp-in.l.google.comGmail · Google LLC · 142.250.96.26 · AS15169
  5. 40alt4.gmail-smtp-in.l.google.comGmail · Google LLC · 172.253.132.27 · AS15169

gmail.com is a major email provider. FFraud never treats its addresses as disposable. See FFraud's record of gmail.com.

To check one address rather than its domain, use the email checker.

Behind every check

24.6 million
IP addresses profiled
2.7 million
malicious domains tracked
228,000
disposable email domains
2.3 million
networks scored

Counts read live from the engine, not written into the page. The full dataset is published on GitHub under the MIT license and rebuilt every 30 minutes.

What MX records are

MX records are the DNS entries that tell the rest of the internet which servers accept email for a domain. A sending server looks them up for every message, tries the lowest number first, and moves to the next record when that server does not answer.

Priority

The number before each host. Lower is tried first; records with the same number share the load.

Mail host

The server name that accepts the mail. It usually gives the service away: Google, Microsoft 365, Proofpoint and the rest each use their own names.

Mail service

The provider recognized from the host name, so you see at a glance who handles the domain's email.

Address and network

Who runs each mail host's address, read from FFraud's IP records.

FFraud's record

Whether the domain hands out disposable mailboxes or is listed for phishing.

MX records and fake signups

A domain without MX records or a working address cannot receive mail, so an address there cannot confirm a signup or a password reset. A null MX says the same on purpose. Throwaway mailbox services often run many domains on the same few mail hosts, so a domain's MX records can give it away before it lands on any list. The email checker and the API flag the disposable domains FFraud already knows.

Common MX mistakes

A few mistakes break mail delivery again and again: an MX record that points at a name with no address, an IP address entered where MX needs a host name, records left over from a previous mail provider, and an old provider's record kept at a lower number than the new one, so senders still try the old servers first.

Questions people ask.

A query for a domain's MX records, the DNS entries that name the servers accepting its email. Type a domain or an email address above to run one.

Type the domain above. The lookup lists every MX record in the order senders try it, with the mail service it belongs to. If your mail provider gave you records to publish, they should appear here exactly as given.

Senders try the record with the lowest number first and fall back to higher numbers when it does not answer. Records with the same number share the traffic.

Yes. Senders then fall back to the domain's own address, the implicit MX rule of RFC 5321, which only works when a mail server listens there. A domain that wants no mail at all publishes a null MX (RFC 7505): a single record that points nowhere.

Up to the old record's TTL, the time resolvers may keep a copy: often an hour, sometimes a day. A sender that looked up the old record keeps using it until its copy expires.

No. It proves the domain accepts mail. Whether a single mailbox exists is up to the mail server, and many accept every address and sort it out later. The email checker tells you what FFraud knows about an address.

Many companies run their email on Google Workspace or Microsoft 365, so their MX records point at Google's or Microsoft's mail servers. The domain stays theirs; the mailboxes live with the provider.

Do it in code.

The same answer from a free API endpoint, with the reason, the recency and the network around the address. Or download the confirmed blocklist for bulk blocking. No card, no quota, no expiry.