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.
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.
| Port | Option in the tool | Used for | Encryption |
|---|---|---|---|
| 587 | SMTP Submission | Apps and mail clients sending through a provider (Gmail, Microsoft 365, your host) | Starts plain, upgrades with STARTTLS (RFC 6409) |
| 465 | SMTPS | Same job as 587, with TLS from the first byte | Implicit TLS (RFC 8314) |
| 25 | SMTP | Server-to-server delivery to a domain's MX host | Optional STARTTLS (RFC 5321) |
| 2525 or other | Custom Port | Alternative submission port some sending services offer when 587 is blocked | Depends 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.
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.These are real results from the tool:
| Host | Port | State | Response | Resolved IP |
|---|---|---|---|---|
| smtp.gmail.com | 587 | OPEN | 4.04 ms | 172.217.76.109 |
| smtp.gmail.com | 465 | OPEN | 2.77 ms | 172.217.76.109 |
| smtp.office365.com | 587 | OPEN | 6.70 ms | 52.97.208.34 |
| smtp.gmail.com | 2525 (custom) | TIMEOUT | 3,503.56 ms | 172.217.76.109 |
| mail.example.com | 587 | Error: "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.
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.
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):
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.openssl s_client -connect smtp.example.com:465 -crlf then EHLO test.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.
192.168.x.x or office servers behind a VPN cannot be tested.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.