Email server settings

The Mail Settings Lookup That Sets Up Your Email Client.

Enter any domain to find its incoming and outgoing mail servers, the IMAP, POP, and SMTP host and port, and the provider behind them, ready to paste into Outlook, Apple Mail, or Thunderbird. No signup.

Try:

Trusted by 500,000+ leading GTM teams of all sizes

From domain to mail settings

How the mail settings lookup works

Three steps, no login, no install. Enter a domain, let Verifox detect the provider from its DNS, then read the incoming (IMAP, POP) and outgoing (SMTP) server settings for your email client.

001DOMAIN

Enter a domain

Drop in any domain you want to inspect. No login, no account, nothing to install. A single domain is all the lookup needs to start.

002QUERY

Query the DNS records

Verifox queries the domain's DNS for its MX records, the same resolution step our verification engine runs first. The records come straight from the authoritative nameservers.

003READ

Read the mail routing

See the MX records in priority order, the provider that runs the mail, and whether the domain accepts mail at all. That is the deliverability signal a verification starts from.

What it gives you

What a mail settings lookup hands you

A mail settings lookup turns a bare domain into a ready-to-use client configuration. In one query you learn who runs the mail, the incoming and outgoing servers, and the host and port for each.

Provider
MXrecords read

Who runs the mail

The MX hosts name the provider behind a domain at a glance, Google Workspace, Microsoft 365, Proofpoint, or a self-hosted server, which is the single most useful thing a mail exchanger lookup tells you.

Routing
0–∞preference order

Routing and priority

Records return in preference order, lowest number first, so you can read the primary mail server and its fallbacks straight away and spot a missing or duplicated backup.

Deliverability
Step 1of deliverability

A deliverability signal

No MX record, or a broken one, means mail will bounce before it is ever sent. An MX lookup is step one of deliverability, then verifying the address confirms the mailbox itself.

Engine
1shared resolver

The same engine, free

This is the exact DNS resolution Verifox runs as the first stage of its verification engine, exposed here free. Pair it with SPF, DKIM, and DMARC checks for the full authentication picture.

The plain-English version

What a mail settings lookup actually does

A mail settings lookup turns a domain into the exact configuration your email client asks for when you add an account: an incoming mail server (IMAP or POP), an outgoing mail server (SMTP), and the host and port for each. Instead of digging through provider help pages, you enter the domain once and read back everything you would otherwise have to assemble by hand.

The trick is that those settings are decided by who runs the domain's mail, and that is written in its DNS. Verifox reads the domain's MX records to detect the provider: hosts pointing at aspmx.l.google.com mean Google Workspace, so the client uses imap.gmail.com on port 993 and smtp.gmail.com; hosts at mail.protection.outlook.com mean Microsoft 365, so it uses outlook.office365.com and smtp.office365.com. Detecting the provider first is what lets the lookup show the right host and port rather than a generic guess, and reading the same MX records is the first thing our verification engine does too.

Here is the honest boundary. A settings lookup tells you how the domain sends and receives mail; it does not prove a specific mailbox on it is live. A domain can have flawless IMAP and SMTP settings while jane@ that domain is long closed. So a settings lookup gets your client connected, and when you need to confirm an actual address is reachable, the free email checkerruns the SMTP-level mailbox check. To go the other way and just read a domain's raw routing, the mail domain lookup and the plain MX lookup show the records themselves. Wiring any of it into your own stack or an AI agent? The same engine is available through the REST API and a native MCP server, with pay-as-you-go pricing localized to your region on the pricing page.

How we stack up

Verifox vs other mail settings tools

Most lookup tools return raw MX hosts and leave the email-client setup to you. Verifox names the provider in plain English, derives the incoming and outgoing server settings from it, runs ad-free with no signup, and flows straight into a real mailbox verification that a standalone DNS tool cannot.

Feature
Verifox
MXToolbox
DNSChecker
Google Toolbox
MX records in priority order
Names the mail providerPlain EnglishHostnamesHostnamesHostnames
No ads, no signup wall
Flows into mailbox verificationBuilt in
REST API for lookups
MCP server for AI agents
Bulk domain lookup
Pricing modelPay as you goSubscriptionFreeFree

What teams are saying

Built for the teams that ship outbound

Growth leads, marketers, and engineers running real campaigns on real lists. Specific numbers, specific tools they switched from, and a verified email address on every byline.

Thomas George, GTM Lead at Stripe

90% lower bill, 0.4% bounces

We were paying ZeroBounce a four-figure monthly bill and still landing 3% bounces on cold campaigns. Switched the pipeline to Verifox, dropped to 0.4% bounces, and cut the bill by more than 90%.
Thomas G.GTM Lead, Stripe
Brittany King, GTM Lead at HubSpot

Catch-all finally has a verdict

Other tools flag 30% of our B2B list as 'risky catch-all' and leave the call to us. Verifox returns a real verdict on those addresses, with a confidence score. We send more, we send safer.
Brittany K.GTM Lead, HubSpot
Dale Micallef, GTM Lead at Slack

Reputation rebuilt in 6 weeks

We had a Gmail spam-folder problem after a bad list import. Verifox cleaned the list and the warmup ran on the same engine. Back in primary inbox in six weeks. One vendor, half the cost.
Dale M.GTM Lead, Slack
Erica Kovalkoski, GTM Lead at Discord

0.7% bounce on 50k

Ran a 50,000-address outbound list through Verifox before our quarterly campaign. Bounces landed at 0.7%, sender reputation didn't move, replies were up 22% over last quarter.
Erica K.GTM Lead, Discord
Greg Lindsay, GTM Lead at OpenAI

MCP in 10 minutes

Their MCP server let me wire email verification directly into our internal Claude agent in about ten minutes. Zero glue code. No other vendor in this space has thought about that workflow.
Greg L.GTM Lead, OpenAI
Rini Vasana, Product Manager at Vercel

10k/min held under 400ms

Tested Verifox at 10,000 verifications per minute on a Tuesday morning. Latency held under 400ms median, no soft failures, no rate-limit walls. The vendor we benched throttled at 2,000/min.
Rini V.Product Manager, Vercel
Jonathan Aharon, GTM Lead at MongoDB

Hygiene that doesn't break pipeline

Our SDRs were enriching from three tools and 14% of the emails were invalid before they hit the sequencer. Verifox sits in the pipeline now and the team stopped seeing 'undeliverable' replies the next week.
Jonathan A.GTM Lead, MongoDB
Emma Fox, GTM Lead at Linear

Bulk that actually ships

Bulk upload, sorted CSV back in twenty minutes, plug into our growth stack. The half-day list-hygiene project per cohort turned into something the marketing intern runs on autopilot.
Emma F.GTM Lead, Linear
David Hare, GTM Lead at Snowflake

Scores you can act on

Verifox returns a 0-100 confidence score per address, not just a label. We thresholded at 75 for the cold sequencer, 60 for nurture, and our deliverability team finally has a knob they can tune.
David H.GTM Lead, Snowflake

Trust & compliance

Enterprise-grade security and scale

Every layer of the stack carries a third-party attestation, so you can ship into regulated industries without rebuilding your compliance posture.

  • Claymation Japanese hanko seal in jade-green clay with a twisted shimenawa rope rim, the words SOC 2 TYPE II embossed in cream clay on its face.

    SOC 2 Type II

    Independently audited to the SOC 2 Type II standard.

  • Claymation Japanese hanko seal in cobalt-blue clay with a twisted shimenawa rope rim, the word GDPR embossed in cream clay on its face.

    GDPR

    Built for the EU with full GDPR data-subject rights.

  • Claymation Japanese hanko seal in rose-pink clay with a twisted shimenawa rope rim, the word CCPA embossed in cream clay on its face.

    CCPA

    California opt-out, do-not-sell, plus DSAR handling.

  • Claymation Japanese hanko seal in terracotta clay with a twisted shimenawa rope rim, the text ISO 27001 embossed in cream clay on its face.

    ISO 27001

    Information security held to the ISO 27001 standard.

  • Claymation Japanese hanko seal in lilac-purple clay with a twisted shimenawa rope rim, the text ISO 42001 embossed in cream clay on its face.

    ISO 42001

    AI governance aligned to the new ISO 42001 standard.

Common questions

Mail settings, answered

The questions we get from people who land here to set up an email client, with what each server does, which ports to use, and where a settings lookup fits next to verifying an address.

What is a mail settings lookup?

A mail settings lookup takes a domain and works out the mail server settings an email client needs to connect to it: the incoming server (IMAP or POP), the outgoing server (SMTP), and the host and port for each. Type a domain into the tool above and Verifox detects the provider and lays out those settings.

It works by reading the domain's MX records, the same DNS resolution our verification engine runs first. The MX hosts reveal the provider, and the provider determines the standard IMAP, POP, and SMTP servers you plug into Outlook, Apple Mail, or Thunderbird.

How do I find the email server settings for a domain?

The simplest way is to enter the domain into the lookup above and read the settings back. You get the incoming mail server (IMAP or POP) and the outgoing mail server (SMTP), each with its host and port, no account and nothing to install.

If your provider publishes its own help docs you can confirm there too, but those make you first work out who actually runs the mail. The Verifox mail settings lookup names the provider for you by reading the MX records, then shows the matching server settings in one place.

What is the difference between the incoming and outgoing mail server?

The incoming mail server delivers mail to your client. It speaks either IMAP, which keeps mail on the server and syncs every device, or POP, which downloads mail to one device. The outgoing mail server sends the mail you write and always speaks SMTP.

A working email client needs both: an incoming server so you can read mail and an outgoing SMTP server so you can send it. The lookup above lists each one with its host and port so you can fill in both halves of the account setup screen.

What are IMAP, POP, and SMTP?

They are the three protocols an email client uses. IMAP and POP are both for receiving mail: IMAP keeps everything on the server and mirrors it across your phone, laptop, and webmail, while POP pulls mail down to a single device. SMTP is for sending.

For most people IMAP is the right incoming choice because it keeps every device in sync. The mail settings lookup gives you the host and port for all three so you can pick the incoming protocol you prefer and pair it with the SMTP server for sending.

Which ports should I use for IMAP, POP, and SMTP?

The standard encrypted ports are 993 for IMAP, 995 for POP, and either 465 or 587 for SMTP. Always use the encrypted port (SSL/TLS or STARTTLS) rather than an unencrypted one so your password is never sent in the clear.

The lookup above shows the exact port for the detected provider next to each server, so you do not have to guess. If a port is blocked on your network, 587 for SMTP is the most widely allowed outgoing port.

Are the Gmail and Outlook mail settings different?

Yes, the host names differ by provider even though the ports are mostly the same. A domain on Google Workspace uses imap.gmail.com and smtp.gmail.com; a domain on Microsoft 365 uses outlook.office365.com and smtp.office365.com.

That is exactly why the lookup detects the provider first. Once it knows who runs the domain's mail from the MX records, it can show the right host and port instead of a generic guess.

Is a mail settings lookup the same as verifying an email address?

No. A mail settings lookup answers a configuration question: which servers does this domain use, so I can connect a client. Verifying an email answers a deliverability question: does jane@example.com actually exist and accept mail.

A domain can have perfectly good IMAP and SMTP settings while a given mailbox on it is closed. So a settings lookup gets your client connected, and the free email checker confirms whether a specific address is live. Verifox runs both on the same engine.

Can I look up mail settings for many domains in bulk?

Yes. The single lookup above is free with no account. For a list of domains, the REST API returns the MX records and the detected provider for each one, which is everything you need to derive the mail server settings programmatically across a whole list.

Bulk lookups run on the same pay-as-you-go credits as the rest of the platform, localized to your region, and those credits never expire. One credit covers a single domain lookup.

Does Verifox store the domains I look up?

No. The domain you enter is resolved in memory and discarded the moment the lookup completes. Nothing logged, nothing retained, nothing sold. A domain's mail records are public DNS data, but your queries are still yours.

Verifox is SOC 2 Type II compliant and GDPR ready. The full breakdown of what we touch and what we do not is in the privacy policy.

Can I run a mail settings lookup from my own app or AI agent?

Yes. The REST API reference documents a lookup endpoint that returns the MX records and the detected provider for any domain, so you can wire mail-server detection into your CRM, your onboarding flow, or any tool that speaks REST.

Verifox also ships native MCP server support, so AI agents (Claude, Cursor, custom LLM apps) can look up a domain's mail setup and verify addresses without glue code. Live uptime and incident history are at status.verifox.ai.