Test a mail server
Sessions are opened from Cloudflare's edge. No credentials are sent — the test stops after reading AUTH mechanisms. 6 checks per minute.
How it works
Resolve and connect
The host is resolved and a TCP session opened from Cloudflare's edge on each port you tick — TLS-on-connect for 465 and 993, plain then STARTTLS for 587, 2525 and 143.
Talk SMTP or IMAP
The greeting is read, EHLO (or CAPABILITY) is sent, STARTTLS is attempted where offered, and EHLO is repeated over TLS to get the real capability list.
Judge the port
Works means connect, TLS and at least one AUTH mechanism. No TLS, no AUTH and refused sessions are called out with the server's own response line.
Recommend settings
The best SMTP and IMAP combination is written out as host, port and encryption — the three fields every sending tool and mail client asks for.
Which port to use, and why it matters
Port 587 is the submission port: clients connect in plain text, say EHLO, and upgrade with STARTTLS before authenticating. Port 465 is implicit TLS — the connection is encrypted from the first byte — and after years of being deprecated it is standard again. Port 2525 is a convention some hosts use when 587 is blocked; it is only safe if STARTTLS is offered there. Port 25 is for servers talking to servers and should never carry a login; it is also the one port Cloudflare's edge cannot open, which is why this tool does not test it and the MX checker exists. For IMAP, 993 is implicit TLS and 143 is STARTTLS; Google and Microsoft only offer 993. A port that connects and accepts AUTH without ever offering TLS is a working configuration that leaks your password to every network between you and the server — the tool marks it NO TLS on purpose.
Reading the extensions
The EHLO response lists what the server supports. AUTH PLAIN LOGIN is password login; XOAUTH2 means the server prefers OAuth tokens — Google and Microsoft have been retiring password auth, so if XOAUTH2 is listed and PLAIN is not, an app password or OAuth connection is required. SIZE is the maximum message size, which decides whether that 12 MB deck attaches. PIPELINING and 8BITMIME are normal; their absence usually means a very old or very locked-down relay. SMTPUTF8 allows non-ASCII addresses. The software line is inferred from the greeting when it identifies itself — Postfix, Exim, Exchange, Sendmail — which is often the first clue about what kind of host you are looking at.
Cold email tools and custom SMTP
Instantly, Smartlead, lemlist and the rest all accept a custom SMTP and IMAP pair per inbox, which is how self-hosted mailboxes, cPanel accounts and private relays get into a sequence. Nearly every “inbox failed to connect” I get asked about is one of four things: the wrong port for the encryption setting, a host that only offers STARTTLS being configured as SSL/TLS (or vice versa), IMAP disabled on the account, or a provider that has turned off basic auth. Run the host here, read the recommendation box, and set the tool's fields to exactly that. If 587 and 465 both fail from the edge but work from your laptop, the server is allowlisting IPs — common on cPanel — and the tool's sending IPs need adding.
Limits
The test proves a session can be opened and authenticated in principle; it never logs in, so it cannot tell you a password is right or that the account is unlocked. It runs from Cloudflare's network, so a firewall that only accepts your office IP will show as a connection failure. Six checks per minute and sixty per day per visitor keeps the tool from being used as a scanner.
Frequently asked questions
Why is port 25 not tested?
Cloudflare's edge, where this runs, cannot open outbound port 25. It is the server-to-server port and never the right choice for a client login anyway; use the MX checker and MTA-STS checker for the inbound side.
587 works from my laptop but fails here. Why?
Almost always an IP allowlist or a geo-block on the server. Cloudflare's addresses are being refused. Check the server's firewall or the hosting panel's SMTP access list.
What settings should I put in Instantly or Smartlead?
Exactly what the recommendation box says: SMTP host, port and encryption, and IMAP host, port and encryption. If the box recommends 465 with SSL/TLS, do not pick STARTTLS in the tool for that port.
Does it try my password?
No. It stops after reading the AUTH mechanisms. Nothing you enter here is a credential and nothing is stored.
Why does IMAP show LOGINDISABLED?
The server refuses password login on that connection — normally because it is plain text, sometimes because the account is OAuth-only. Use 993, and if it still shows, use an app password or OAuth.
Last reviewed
What to run next
The checks that most often follow this one.
More in this category
Guides that go deeper
When the tools tell you something is wrong
The diagnostics here are free and always will be. When the fix is bigger than a DNS record, this is the work I do.
Deliverability rescue
Mail landing in spam, replies gone quiet, or a domain suddenly blocked. I find the actual cause rather than guessing, and fix it.
- Authentication and alignment failures
- Blocklist delistings and reputation repair
- Gateway and filter-level blocks
- A written report on what broke and why
Email & sending infrastructure
Sending domains, inboxes, authentication and warmup, built to survive volume instead of burning down in a month.
- Domain and inbox fleets at any scale
- SPF, DKIM, DMARC and tracking domains
- Google Workspace and Microsoft 365 inboxes
- Handover documentation you actually own
Domain, DNS & migration
Changing registrar, mail provider or host without a day of downtime or a week of mail silently failing.
- Registrar and nameserver moves
- Workspace and Microsoft 365 migrations
- MX, SSL and subdomain cutover
- Staged rollout with rollback at every step
Monitoring & retainer
Infrastructure drifts. Records get edited, certificates expire, domains get listed. Ongoing eyes on the fleet.
- Scheduled checks across every domain
- Alerts before your clients notice
- Monthly reporting
- Priority response when something breaks
Start with a call
Bring a domain and the symptom. I will tell you what is actually wrong and whether you need me at all — plenty of people leave that call able to fix it themselves.
Thirty minutes, no pitch
We will run the checks together on your actual domains, and you will leave knowing what is broken, what it takes to fix, and what it should cost. If that is a job you can do in-house, I will say so.