SMTP Checker — Frequently Asked Questions
22 answers covering SMTP testing, ports, app passwords, encryption, sending limits and why email ends up in spam.
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, AOL and Outlook.com all require app passwords for third-party SMTP clients. 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.
Leave the recipient field empty and the tool will still connect, negotiate encryption and authenticate — it just stops before transmitting a message body. That verifies your host, port and credentials without delivering anything. Supplying a recipient additionally proves the server will accept and relay a real message.
STARTTLS (used on port 587) opens a plaintext connection and then upgrades it to an encrypted one with the STARTTLS command. Implicit SSL/TLS (used on port 465) encrypts the connection from the first byte. Both end up equally secure with modern TLS versions. The difference matters only because you must match the port to the method — using STARTTLS settings on port 465 produces a handshake failure.
Google removed support for "less secure app access". A standard Gmail password can no longer authenticate over SMTP. You must turn on 2-Step Verification, generate a 16-character App Password, and use that instead. Full walkthrough on our Gmail SMTP settings page.
SPF is a DNS record listing which servers may send mail for your domain. DKIM adds a cryptographic signature to each message so receivers can verify it was not altered and genuinely came from your domain. DMARC ties the two together and tells receivers what to do when a message fails both. Together they are the single biggest factor in whether authenticated mail reaches the inbox.
Nearly every residential ISP and cloud provider blocks outbound port 25 to limit spam, and they rarely unblock it. Use port 587 with STARTTLS or 465 with SSL/TLS, both of which are intended for authenticated submission and are almost never blocked. If those are also blocked, many relay services — SendGrid, Mailgun, Brevo, SMTP2GO — accept submissions on port 2525.
Yes. Any reachable SMTP host works — Postfix, Exim, Microsoft Exchange, iRedMail, Mailcow, Mail-in-a-Box or a container running on a public IP. Point the tool at your hostname and port. It is a practical way to confirm a new server accepts authenticated submission from outside your own network, which is exactly the path a real client takes.
The server is refusing to forward mail to a domain it does not host, because your session is not authenticated. Either SMTP authentication was not attempted, or the credentials failed and the client carried on anyway. Enable SMTP AUTH in your client and verify the username and password are accepted.
Limits are set by the provider, not by SMTP itself. Free Gmail allows about 500 recipients a day, Google Workspace 2,000, Outlook.com 300 messages, Microsoft 365 10,000 recipients, and Yahoo and iCloud roughly 500. Transactional relays scale far higher but meter by plan. Exceeding a limit produces a 550 or 421 rejection until the window resets.
No. A successful test proves the transport layer works: the server is reachable, encryption negotiated, credentials were accepted and the message was handed over. Where it lands afterwards depends on domain authentication, sending reputation, content filtering and recipient rules — none of which SMTP itself controls.
The server presented a TLS certificate that does not validate — usually self-signed, expired, or issued for a different hostname than the one you connected to. Connect using the exact hostname on the certificate. For a self-hosted server, install a valid certificate (Let's Encrypt is free). Disabling certificate verification removes the protection TLS provides and should be a last resort on trusted networks only.
An SMTP relay is a third-party service that accepts your mail and delivers it on your behalf — SendGrid, Mailgun, Amazon SES, Brevo, Postmark and similar. Relays are used for transactional and bulk sending because they manage IP reputation, handle bounces, provide delivery analytics and scale well past mailbox provider limits. See our SMTP settings directory for configuration details.
Yes, with openssl s_client -starttls smtp -connect smtp.example.com:587 you can run the handshake manually and issue EHLO, AUTH LOGIN and MAIL FROM yourself. It gives you the raw server replies, which is excellent for debugging. This tool does the same conversation for you and formats the result, which is faster when you just need an answer.
Still stuck?
Run a live test against your server — the reply it returns usually answers the question immediately.
Test SMTP Server