Test Any SMTP Server Instantly
Diagnose port reachability, STARTTLS / SSL handshake latency, authentication errors, and generate production-ready code snippets for any mail provider.
SMTP Server Configuration
Port 25, 465, 587, 2525Ready to execute SMTP test connection
Select a preset or enter host details and click "Run Test Connection"
Complete Guide to Free Online SMTP Testing & Diagnostics
Simple Mail Transfer Protocol (SMTP) is the global standard for sending transaction and marketing emails over TCP/IP networks. When developing web applications with Nodemailer, Django, Laravel, WordPress, or Python, connection timeouts, SSL certificate mismatches, or invalid authentication credentials frequently prevent email delivery.
Our free online SMTP test studio opens an active TCP socket to your mail server, negotiates TLS encryption protocols, authenticates credentials (`AUTH PLAIN` / `AUTH LOGIN`), and records high-resolution latency metrics for DNS, TCP handshake, and payload dispatch.
Understanding the Security Audit Rating System (Grade A+ to F)
Strict TLS 1.3 / Implicit SSL
Enforces encrypted socket channels on Port 465 (Implicit SSL) or Port 587/2525 with STARTTLS validation.
Opportunistic STARTTLS
Negotiates TLS 1.2 or STARTTLS after plain TCP greeting banner without requiring mandatory TLS enforcement.
Plain TCP (No TLS)
Connects via plain TCP without SSL/TLS encryption. Credentials travel in plaintext. Recommended only for sandboxes.
Handshake / Auth Error
Target host timed out, refused socket connection, failed authentication (`535`), or rejected STARTTLS commands.
Common SMTP Response Error Codes & Troubleshooting
| Code / Error | Error Description | Root Cause & Recommended Fix |
|---|---|---|
| 535 5.7.8 | Authentication Credentials Invalid | The username or password provided was rejected by the SMTP server. For Gmail/Outlook, generate an App Password rather than your account password. |
| 538 5.7.11 | Must Issue STARTTLS Command First | The server requires encrypted TLS before authentication. Set security mode to STARTTLS or Explicit TLS in your application config. |
| 550 5.1.1 | Requested Action Not Taken: User Unknown | The recipient mailbox does not exist or has been disabled. Verify recipient address syntax. |
| 554 5.7.1 | Relay Access Denied / Blacklisted | The server rejected sending to unauthenticated external domains or your sending IP is on a DNSBL spam blacklist. |
| ECONNREFUSED | Connection Refused by Remote Host | No SMTP service is listening on the target port, or cloud firewall rules (UFW/iptables/AWS Security Groups) are blocking TCP traffic. |
| ETIMEDOUT | TCP Connection Timed Out | Network packet drop or port blockage. Major cloud providers (AWS EC2, DigitalOcean, Google Cloud) block port 25 by default. Use port 587 or 2525. |
Frequently Asked Questions (FAQ)
What ports should I use for SMTP connection testing?
Port 587 is the standard for STARTTLS encrypted email submission. Port 465 is used for Implicit SSL/TLS. Port 2525 is an alternative submission port supported by SendGrid, od2 Sandbox, and Mailtrap when port 587 is blocked by ISPs.
How do I test Nodemailer or Django email delivery locally?
You can test against our free SmtpCove SMTP Sandbox. Host: sandbox.mail.od2.in, Port: 2525 or 587, with any credentials. It captures emails instantly in your private sandbox inbox without sending real emails.
What is the difference between STARTTLS and Implicit SSL?
STARTTLS starts as a plain TCP connection on port 587 or 2525 and upgrades to TLS encryption after issuing the STARTTLS command. Implicit SSL encrypts the entire TCP socket from the first byte on port 465.
Is my password or credential data secure when testing?
Yes! Credentials are used strictly in-memory during the ephemeral socket test and are never stored to disk or database. Furthermore, our anti-brute-force rate limiter protects accounts from password guessing attempts.