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.

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

Run an SMTP test

16,000+ checks run Encrypted · not stored

Quick fill

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

Popular presets

Test the most-used SMTP servers in one click

Load verified settings into the tester, add your credentials and run. Or open the full setup guide.

Gmail

Host
smtp.gmail.com
Port
587 · STARTTLS
Guide

Microsoft 365

Host
smtp.office365.com
Port
587 · STARTTLS
Guide
SE

SendGrid

Host
smtp.sendgrid.net
Port
587 · STARTTLS
Guide
MA

Mailgun

Host
smtp.mailgun.org
Port
587 · STARTTLS
Guide
AM

Amazon SES

Host
email-smtp.<region>.amazonaws.com
Port
587 · STARTTLS
Guide

Zoho Mail

Host
smtp.zoho.com
Port
465 · SSL/TLS
Guide

Yahoo Mail

Host
smtp.mail.yahoo.com
Port
465 · SSL/TLS
Guide
BR

Brevo

Host
smtp-relay.brevo.com
Port
587 · STARTTLS
Guide
How it works

Test your SMTP server in four steps

The whole check takes under a minute.

1

Pick your provider

Select Gmail, Outlook, Microsoft 365, Yahoo, iCloud, Zoho, SendGrid and more to auto-fill the correct hostname and port. Choose Other for a custom or self-hosted server.

2

Enter host and port

Use port 587 with STARTTLS, or 465 with SSL/TLS. Leaving encryption on Auto picks the right method for the port you entered.

3

Add your credentials

Supply the SMTP username and password. Most major providers now require an app password instead of your normal account password.

4

Read the result

We connect, negotiate encryption, authenticate and deliver a test message — then show you the server's own reply so you know exactly what to fix.

The basics

What is SMTP, and why test it?

SMTP (Simple Mail Transfer Protocol) is how email gets from one server to the next. Contact forms, invoices, password resets and newsletters all leave your system over SMTP.

When it breaks, nothing tells you. The form says “sent”, the app logs no error, and the message never arrives. An SMTP test talks to your server the same way your app does, and shows the exact step that fails.

What a passing test proves

The server is reachable, encryption is set up and your login is accepted. Whether mail then lands in the inbox or in spam also depends on SPF, DKIM and DMARC and your sending reputation.

What the test checks, step by step

Look up any SMTP reply code
  1. 1

    Connect

    TCP

    Opens a connection to your server on the port you chose.

    If it fails

    Timeout: a firewall or your provider is blocking the port.

  2. 2

    Greeting

    220EHLO

    Reads the server’s greeting and the features it supports.

    If it fails

    No reply: wrong hostname, or it isn’t a mail server.

  3. 3

    Encryption

    STARTTLSSSL/TLS

    STARTTLS on port 587, or encrypted from the start on 465.

    If it fails

    Handshake error: port and encryption don’t match, or the certificate is invalid.

  4. 4

    Login

    AUTH LOGINAUTH PLAIN

    Signs in with your username and password.

    If it fails

    535: wrong password, or an app password is needed.

  5. 5

    Send

    MAIL FROMRCPT TODATA

    Hands over the test message for delivery.

    If it fails

    550 / 554: the server refused it by policy.

When to run an SMTP test

New mailbox or domain

Confirm the host, port and login before you put them into your app.

Contact form stopped sending

Find out whether the mail server or the website is the problem.

Moving to a new host

Check that the new server accepts logins from outside its own network.

Turned on 2-step verification

Your normal password stops working for SMTP. You’ll need an app password.

Cloud server or VPS

AWS, Azure, Google Cloud and DigitalOcean block port 25 by default.

Using a relay service

Check SendGrid, Mailgun, Amazon SES or Postmark credentials outside your app.

Which SMTP port to use

Full SMTP ports guide
587 STARTTLS

The standard port for sending mail. Try this one first.

465 SSL/TLS

Encrypted from the first byte. Supported by most providers.

25 Often blocked

Used between mail servers. Most ISPs and cloud hosts block it.

2525 STARTTLS

An unofficial fallback that relay services offer when 587 is blocked.

Troubleshooting

The four SMTP errors you'll actually hit

Over ninety percent of failed SMTP tests come down to one of these.

535 Authentication failed

Your username or password was rejected. Gmail, Yahoo, iCloud and AOL don’t accept your normal password over SMTP. Generate an app password instead. Outlook.com only allows OAuth 2.0 sign-in. SendGrid requires the literal username apikey. Microsoft 365 needs SMTP AUTH enabled on the mailbox.

Connection timed out

Packets never reached the mail server. An outbound firewall, an ISP blocking port 25, or a cloud provider's default SMTP block is the usual cause. Try port 587, then 465, then test from a different network.

550 Relay access denied

The server will not forward mail for a domain it does not host because your session was never authenticated. Enable SMTP authentication and confirm the credentials are accepted before the MAIL FROM command.

TLS / certificate errors

The port and encryption method do not match, or the certificate fails validation. Pair 587 with STARTTLS and 465 with SSL/TLS, and connect using the exact hostname the certificate was issued for.

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