SMTP Test Tool — Check Any SMTP Server Online

We connect to your server, check SSL/TLS and your login, and send a test email. You see every step of the SMTP conversation.

Run an SMTP test

16,100+ checks run Encrypted · not stored

Quick fill

Password used for this one connection only — never stored or logged.

  • Any host & port
  • SSL/TLS certificate check
  • Full server conversation
  • Password never stored

About SMTP Checker

SMTP Checker is an online tool for testing SMTP servers. Enter your server, port and login in the tester above, and it connects to the server, checks the encryption and your credentials, and can send a test email. Every step of the SMTP conversation is shown, so you can see exactly where a problem starts.

What is SMTP?

SMTP (Simple Mail Transfer Protocol) is the internet standard for sending email, defined in RFC 5321. When your website, app or mail client sends a message, it hands it to an SMTP server. That server then looks up the recipient’s mail server through its MX records and delivers the message there.

SMTP only handles sending. Reading mail from a mailbox uses a different protocol, IMAP or POP3, which is why a mailbox can receive mail fine while its outgoing SMTP settings are broken.

Why test your SMTP server?

Email problems are easy to miss. A contact form shows “message sent”, the app logs no error, and the email never arrives. Testing the SMTP server directly tells you whether the problem is the mail server or your website. Other reasons to test:

  • Confirm settings before you go live: check the host, port, encryption and login before you put them into your app.
  • Find the real cause of a failure: see the server’s own reply code instead of a generic “could not send”.
  • Catch blocked ports: many cloud and hosting providers block outgoing connections on port 25, and some block others too.
  • Check your login after a change: a new password or turning on 2-step verification often stops SMTP logins from working.
  • Check the TLS certificate: make sure it is valid, not expired, and issued for the hostname you connect to.

Correct SMTP settings

Most sending problems come down to a few settings. A working setup follows these rules:

  • The server is your provider’s SMTP hostname, such as smtp.gmail.com, not your website address.
  • Port 587 with STARTTLS is the standard port for sending mail. Try it first.
  • Port 465 uses SSL/TLS from the first byte, before any SMTP command is sent.
  • Port 25 is meant for server-to-server delivery and is often blocked for normal sending.
  • Port 2525 is an unofficial alternative that some relay services offer when 587 is blocked.
  • The port and encryption must match: STARTTLS on 587, SSL/TLS on 465. A mismatch causes timeouts or handshake errors.
  • The username is usually your full email address. Relay services differ: SendGrid, for example, uses the word apikey as the username and your API key as the password.
  • Accounts with 2-step verification usually need an app password instead of your normal password.
  • The From address should be the mailbox you log in with, or an alias or domain verified with your provider. Otherwise many servers reject the message.
  • For mail to reach the inbox rather than spam, your domain also needs SPF, DKIM and DMARC records.

You can find the exact values for 22 common providers in our SMTP settings directory. If you are unsure whether your settings are right, run them through the tester above.

Why use SMTP Checker?

Checking an SMTP server by hand means using command-line tools such as openssl s_client, reading server logs, or setting up a mail client just to see an error. SMTP Checker does the same work in a few seconds in your browser and shows you:

  • Each step of the test with a clear pass or fail.
  • The server’s greeting, supported login methods and maximum message size.
  • The TLS certificate: who issued it, when it expires and whether it matches the hostname.
  • The exact reply code when something fails, with a link to what it means in our SMTP error code reference.

There is no account to create. Your password is used for one login attempt and is never stored or logged. For extra safety, test with an app password and revoke it afterwards.

How does SMTP Checker work?

When you run a test, SMTP Checker opens a connection to your server on the port you chose and reads its greeting. It sends EHLO to learn which features the server supports, then sets up encryption with STARTTLS, or connects with SSL/TLS from the start on port 465. Next it logs in with your username and password. If you turned on “Send test email”, it then hands over a short test message for delivery.

The result shows how far the test got and the server’s replies along the way. If a step fails, you see which step it was and the server’s error, so you can fix the right thing instead of guessing. More about SMTP Checker.

FAQ

Frequently asked questions

Everything people ask about testing SMTP servers, ports, app passwords and delivery.

An SMTP checker is an online diagnostic tool that opens a real connection to your outgoing mail server, negotiates TLS, attempts to authenticate with the credentials you supply, and optionally delivers a test email. It tells you in seconds whether your SMTP host, port, encryption method and login are correct — without having to configure a mail client first.

Enter your SMTP hostname (for example smtp.gmail.com), the port (587 for STARTTLS or 465 for SSL/TLS), your username and password, and the address you want the test email sent to. Click Test SMTP. Our server performs a live SMTP handshake and reports the exact result, including the server's own reply code if something fails.

Port 587 is the modern standard for authenticated mail submission with STARTTLS and should be your default. Port 465 uses implicit SSL/TLS and is widely supported. Port 25 is for server-to-server relay and is blocked by most ISPs and cloud providers. Port 2525 is an unofficial fallback offered by many relays when 587 is blocked. See our SMTP port guide for the full comparison.

A 535 reply means the server rejected your username or password. The usual cause is using your normal account password where the provider requires an app password. Gmail, Yahoo, iCloud and AOL require app passwords for third-party SMTP clients, and Outlook.com accounts only accept OAuth 2.0 sign-in. SendGrid requires the literal username apikey. Microsoft 365 requires SMTP AUTH to be enabled on the mailbox. See the SMTP error code reference.

No. Your password is used only for the single authentication attempt against the server you specify and is never written to our database or logs. We record the hostname, port, username and the test outcome so the tool can show you diagnostics — the password is discarded as soon as the connection closes. Submissions travel over HTTPS. For maximum safety, test with an app password you can revoke afterwards.

SMTP sends mail. IMAP and POP3 retrieve it. SMTP pushes a message from your client to a mail server and onward to the recipient. IMAP keeps messages on the server and syncs state across devices; POP3 downloads messages and traditionally deletes the server copy. A working SMTP configuration has no bearing on whether you can read mail, and vice versa.

A timeout means packets never reached the SMTP service. The common causes are an outbound firewall rule on your network, an ISP blocking port 25, a cloud provider blocking outbound SMTP by default (AWS, Azure, Google Cloud and DigitalOcean all do this), a typo in the hostname, or the wrong port for the encryption method you chose. Try port 587 and 465 in turn, and test from a different network to isolate the block.

A 250 reply after the message body means the receiving server has accepted responsibility for the message — not that it reached the inbox. The message can still be filed as spam, silently dropped by a policy filter, or bounced asynchronously. A successful SMTP test proves your sending path works; inbox placement additionally depends on SPF, DKIM, DMARC and sender reputation.

Yes. The tool is completely free, requires no registration, and has no usage cap for normal diagnostic use. There is no paid tier and no credit card involved.

Delivery and placement are different problems. If the SMTP test succeeded but the mail landed in spam, the sending domain most likely lacks authentication. Publish an SPF record authorising the sending host, sign outgoing mail with DKIM, and add a DMARC policy. Also confirm the sending IP has matching reverse DNS and is not on a public blocklist.

Ready to check your mail server?

Test the connection, encryption and login of your mail server and see exactly where it fails.

Test SMTP Server