SMTP Connectivity Tester

Check whether an SMTP server is reachable on port 587, 465, 25 or a custom port. Shows OPEN, CLOSED or timeout, the resolved IP and the connection time.

SMTP Connectivity Tester

Check whether an SMTP server is reachable on port 587, 465, 25 or a custom port. Shows OPEN, CLOSED or timeout, the resolved IP and the connection time.

Use a public host or domain only.
Choose a common port or switch to custom.
Manual port input.
Live analysis is enabled where server-side checks are available. A few tools still fall back to readiness mode when they need external network services or third-party APIs.

What this SMTP tester checks

When an app, website contact form, printer or email client says "could not connect to SMTP server", the first question is whether the mail server is reachable at all on the port you configured. This tool answers exactly that. It resolves the host name you enter to a public IP address, then opens a TCP connection from our server to that IP on the port you choose and reports whether the port is OPEN, CLOSED or timed out, together with the resolved IP and the connection time in milliseconds.

It is a reachability test, not a full mail session. It does not read the server's greeting banner, send EHLO, start TLS, test a username and password, or send a message. Knowing where its job ends tells you what to check next, so the sections below cover both.

Which port should you test?

PortOption in the toolUsed forEncryption
587SMTP SubmissionApps and mail clients sending through a provider (Gmail, Microsoft 365, your host)Starts plain, upgrades with STARTTLS (RFC 6409)
465SMTPSSame job as 587, with TLS from the first byteImplicit TLS (RFC 8314)
25SMTPServer-to-server delivery to a domain's MX hostOptional STARTTLS (RFC 5321)
2525 or otherCustom PortAlternative submission port some sending services offer when 587 is blockedDepends on the provider

If you are setting up a website plugin or an app to send mail, you almost always want 587 or 465 with the host name your provider gives you (for example smtp.gmail.com or smtp.office365.com), not port 25.

How to run the test

  1. Enter the server name in SMTP Host, for example smtp.office365.com. You can also type a public IP address. Leave out smtp:// and any port number. The quick example chips fill in a sample host.
  2. Pick the Application Type: SMTP (25), SMTP Submission (587) or SMTPS (465). The Port box fills in automatically and locks. Choose Custom Port to type any port from 1 to 65535 yourself.
  3. Click Test SMTP Connectivity.
  4. Read the badge next to host:port, then the Response, Port and State cards, and the resolved IP shown under "Public network target".

Worked example

These are real results from the tool:

HostPortStateResponseResolved IP
smtp.gmail.com587OPEN4.04 ms172.217.76.109
smtp.gmail.com465OPEN2.77 ms172.217.76.109
smtp.office365.com587OPEN6.70 ms52.97.208.34
smtp.gmail.com2525 (custom)TIMEOUT3,503.56 ms172.217.76.109
mail.example.com587Error: "Unable to resolve host to a public IP."

Reading these: Gmail and Microsoft 365 accept connections on their submission ports, so if your app fails against them on 587, the problem is on your side of the connection (a firewall, your host blocking outbound mail ports, or wrong credentials) rather than the provider being down. The 2525 test shows what a port that nothing answers on looks like: no reply, so the tool gives up after about 3.5 seconds. The last row shows a host name with no public DNS record, which usually means a typo or an internal-only name. Your IPs and times will differ; providers return different addresses by location, and times are measured from our server, not from your network.

How to read each result

  • OPEN: the server accepted a TCP connection on that port. The host name, DNS and the server's firewall are fine from the outside. If your app still fails, move on to TLS settings and login details.
  • TIMEOUT: nothing answered. A firewall is silently dropping traffic, the server is down, or you have the wrong port. Check the port number your provider documents first.
  • CLOSED: the connection was refused or could not be made. The machine is reachable but nothing listens on that port, or a network along the way rejected the attempt.
  • Unable to resolve host: DNS has no public address for the name. Check spelling, and use the MX Record Checker if you are looking for a domain's incoming mail server.

An important note about port 25

Many cloud and hosting networks block outbound connections to port 25 to stop spam, and the network our checker runs on is one of them. In our own tests, port 25 returned CLOSED within a millisecond with "Network is unreachable", even for Gmail's inbound MX host, which certainly accepts mail. So a CLOSED result on port 25 from this tool does not prove your server rejects connections. Test port 25 from another network, or use the commands below from the server that needs to deliver mail. Ports 587, 465 and custom ports are tested normally.

What to check after an OPEN result

An open port only proves the first step. To see the rest of the conversation, run one of these from the machine that will send mail (OpenSSL is installed on most Linux and macOS systems):

  • Port 587: openssl s_client -starttls smtp -connect smtp.example.com:587 -crlf then type EHLO test. You should see a 220 greeting, a valid certificate chain, and a 250-AUTH line listing login methods.
  • Port 465: openssl s_client -connect smtp.example.com:465 -crlf then EHLO test.
  • Windows PowerShell, reachability only: Test-NetConnection smtp.example.com -Port 587, where TcpTestSucceeded : True matches an OPEN result here.

If the connection works from this tool but not from your server, your hosting provider is probably blocking outbound mail ports; many shared and cloud hosts do this until you ask them to lift it, or they expect you to send through an email API instead.

Limits and privacy

  • Only public host names and public IPs are accepted. Private ranges such as 192.168.x.x or office servers behind a VPN cannot be tested.
  • The test runs from our server, so it does not tell you whether your own office or home network blocks the port.
  • You never enter a username, password or message here, and the tool sends no email data.
  • One port per test. Run it twice to compare 587 and 465.

This tool vs. testing by hand

Telnet or OpenSSL from your own server is the most complete test because it runs from the real sending machine and shows the full SMTP dialogue, but it needs shell access and a little protocol knowledge. This page is faster when you just need an outside view: is the host name right, does it resolve, and is the port answering? For a broader check, the Open Port Checker tests any TCP service, the SPF DKIM DMARC Checker looks at the DNS records that decide whether your mail lands in the inbox, and the Mail Header Analyzer shows the route a delivered message actually took.

Frequently Asked Questions

Both are for sending mail from an app or client with a login. 587 starts unencrypted and upgrades with STARTTLS; 465 uses TLS from the start (RFC 8314). Use whichever your provider documents. Gmail and Microsoft 365 both accept 587.

Many hosting and cloud networks block outbound port 25 to stop spam, including the network this checker runs on. A CLOSED result on port 25 here does not prove your server is refusing mail. Test it from the sending server with telnet or openssl.

Reachability is fine, so check the next steps: the encryption setting (STARTTLS for 587, SSL/TLS for 465), the username and password or app password, and whether your hosting provider blocks outbound mail ports from your server.

No. It only opens a TCP connection to the host and port. It never asks for credentials and sends no email, so use openssl s_client or your mail client to test login.

Nothing answered within about 3.5 seconds. Usually a firewall is dropping the traffic, the port number is wrong, or the server is down. Confirm the port your provider uses first.