Toolsky

Free Online Tools & Utilities for Every Task.

Online SMTP Test

Free advanced online tool to Test and check your SMTP server.

Leave empty if no authentication is required
Leave empty if no authentication is required
Common SMTP Settings
  • Gmail smtp.gmail.com, Port 587, TLS
  • Outlook smtp.office365.com, Port 587, TLS
  • Yahoo smtp.mail.yahoo.com, Port 465, SSL

Email failures are uniquely miserable: the form says "message sent", the customer waits, and the mail never existed. The fault usually sits in the sending server's configuration — a wrong port, a rejected password, a TLS mismatch — and guessing at it from inside your application is slow. An online SMTP test cuts through the guessing by connecting to your mail server exactly as a sending application would, walking through the SMTP conversation step by step, and showing you the transcript of what the server actually said.

What an SMTP Test Actually Checks

SMTP — the Simple Mail Transfer Protocol, standardised in RFC 5321 — is the language mail servers speak when handing messages to each other. A test tool opens a connection to your server on the port you specify, reads its greeting banner, introduces itself with an EHLO command, negotiates encryption if offered, authenticates with the credentials you supply if you choose to test that stage, and can send an actual test message to confirm the full path works. Each step produces a numbered reply code from the server, and the test displays the exchange, so instead of "mail doesn't work" you get "the server refused authentication with a 535 response" — a fact you can act on.

What the Test Connects and Reports

  • Connection and banner — whether the server answers on the given host and port at all, and what it calls itself when it does.
  • EHLO capabilities — the list of features the server advertises, such as STARTTLS encryption, authentication methods and maximum message size.
  • TLS negotiation — whether encrypted submission works, both the upgrade style (STARTTLS) and the implicit style used on port 465.
  • Authentication result — whether the username and password are accepted for relaying.
  • Test message delivery — whether the server accepts a real message for a recipient, and the reply code it returns when it does.
  • A readable transcript — the full command-and-response log, which is the document your hosting support will actually want to see.

How to Run an SMTP Test

  1. Gather your server's details: hostname, port, and whether it expects STARTTLS or implicit TLS.
  2. Before testing sending, confirm the domain's mail routing is right — an MX lookup shows which servers are supposed to receive its mail.
  3. Enter the hostname and port into the test tool.
  4. Select the encryption mode that matches the port: STARTTLS typically on 587, implicit TLS on 465, plain (or opportunistic) on 25.
  5. If you need to test authenticated sending, add the mailbox username and password for the account that will send.
  6. Set a sender and a recipient you control, then run the test.
  7. Read the transcript from the top: the first step that fails, and its reply code, is where your real problem lives.

Example: Reading a Test Transcript

A healthy authenticated session reads like a polite, predictable conversation. The server greets you with a 220 banner ("mail.example.com ready"). Your EHLO earns a 250 reply listing its capabilities, including STARTTLS and AUTH. After encryption is established and you log in, the server answers 235 — authentication succeeded. You name the sender and recipient (each met with 250), announce the message body with DATA (a 354 invites you to send it), and finish with a final 250 confirming the message was accepted and queued. Now change one detail — the password — and the same transcript collapses at the login step with 535 Authentication failed. Nothing else in the log matters until that line is fixed. That is the entire discipline of SMTP troubleshooting: find the first non-2xx/3xx reply, and you have found the fault.

When the Test Fails: Common Causes

Connection timeouts usually mean a firewall or hosting firewall rule is silently dropping the port, or the network you test from blocks outbound port 25 (many ISPs do; ports 587 and 465 are the usual way around it). TLS errors typically come from a mode mismatch — asking for STARTTLS on a port that expects implicit TLS, or the reverse. Authentication failures are most often a wrong password, a username that must be the full email address rather than the part before the @, or an account that requires an app-specific password. One boundary worth knowing: a successful SMTP test proves your server accepts and relays a message. It says nothing about whether the receiving side will file it in the inbox or the spam folder — that depends on SPF, DKIM and reputation, separate checks entirely. After delivery works, run addresses through the email validator to catch malformed recipients, and check your sending IP with an email blacklist check if messages vanish at particular providers.

Frequently Asked Questions About SMTP Testing

Which port should I test — 25, 465 or 587?

Port 587 is the standard submission port for authenticated sending with STARTTLS, and the first choice for application mail. Port 465 is the implicit-TLS alternative with the same job. Port 25 is primarily for server-to-server relay and is blocked by many networks, so test it only when diagnosing relay specifically.

Is it safe to enter my mailbox password into an online test?

Use judgement: test with a dedicated test mailbox or an app-specific password rather than your main account credentials, and change the password afterwards if you have any doubt. Never test with credentials you reuse for anything important.

The test passed, but mail still lands in spam. Why?

Because sending and deliverability are different problems. The test verifies that your server accepts and relays mail; inbox placement depends on your domain's SPF and DKIM records, message content and sender reputation, none of which the SMTP handshake measures.

What does an "open relay" warning mean?

It means the server accepted a message for an outside recipient without authentication. Open relays are abused to send spam and will get the server blacklisted, so if a test flags one on your server, treat closing it as urgent.

Why does the connection time out on port 25 but work on 587?

Port 25 is blocked by default on many ISP and cloud networks as an anti-spam measure. Port 587 exists precisely for client submission, so it is the port applications are expected to use.

Can I test Gmail or Outlook SMTP servers?

You can test connectivity to them, but they require full account authentication (and usually app passwords or OAuth) before accepting anything, so a meaningful send test needs credentials for an account on that service.

What does reply code 550 mean?

It is a permanent refusal — commonly "relaying denied" (you are not authorised to send through the server) or "mailbox unavailable" (the recipient does not exist). The text after the code usually says which of the two applies.

Know Mail Works Before Your Users Find Out It Doesn't

Every silent mail failure starts as a configuration fact that a two-minute test would have surfaced. Run the transcript, read the first failing line, fix that one thing — in that order, mail stops being a mystery.