Tools
Explore our collection of email marketing tools.
Free SMTP Port Checker — Test Email Server Connectivity
Use this free SMTP port checker to instantly test whether common email server ports are open, blocked, or timing out on any host or IP address. Simply enter a hostname like smtp.gmail.com or an IP address, select a port, and run the check. The tool simulates real-world SMTP connectivity tests and displays response time, TLS support, and server banner information so you can diagnose mail server issues in seconds.
Check SMTP Port
Enter a hostname or IP address and select a port to test connectivity
Common SMTP Settings
| Provider | SMTP Host | Ports | Authentication | TLS / SSL |
|---|---|---|---|---|
| Gmail | smtp.gmail.com | 465 (SSL), 587 (TLS) | OAuth 2.0 / App Password | Required |
| Outlook | smtp-mail.outlook.com | 587 (TLS) | OAuth 2.0 / Password | Required |
| Yahoo | smtp.mail.yahoo.com | 465 (SSL), 587 (TLS) | App Password | Required |
| SendGrid | smtp.sendgrid.net | 25, 587, 2525 | API Key | Optional |
| Mailgun | smtp.mailgun.org | 465 (SSL), 587 (TLS), 2525 | API Key / Password | Optional |
How to Use This SMTP Port Checker
Diagnosing email server connectivity issues does not have to involve complex command-line tools. This SMTP port checker gives you a fast, visual way to test whether a mail server is reachable on the ports that matter most. Follow these steps to run your first check.
Whether you are troubleshooting a failed email campaign, setting up a new SMTP relay, or verifying your ISP is not blocking outbound mail traffic, understanding port availability is the first step toward a reliable email infrastructure.
- 1
Enter the Host or IP Address
Type the SMTP server hostname (for example, smtp.gmail.com) or a public IP address into the host field. You do not need to include protocol prefixes like https or mailto.
- 2
Select the Port to Test
Choose from the most common SMTP ports: 25 (legacy relay), 465 (SSL/TLS), 587 (STARTTLS submission), or 2525 (alternate submission). You can also enter a custom port if your server uses a non-standard configuration.
- 3
Run the Port Check
Click the Check Port button to initiate the simulated connectivity test. The tool will attempt to determine whether the selected port is open, blocked by a firewall, or timing out due to network issues.
- 4
Review the Results
Examine the status card, response time, and TLS support indicators. An open port with TLS support means the server is ready for secure email submission. A blocked or timed-out result suggests a firewall, ISP restriction, or server misconfiguration.
- 5
Compare Against Common Settings
Use the reference table below the results to compare your server against known configurations for Gmail, Outlook, Yahoo, SendGrid, and Mailgun. This helps you verify that you are using the correct host, port, and authentication method for your provider.
What Is SMTP and Why Do Ports Matter?
SMTP, which stands for Simple Mail Transfer Protocol, is the standard mechanism used to send and relay email across the internet. Every time you hit send in your email client or your marketing platform dispatches a campaign, SMTP is the underlying protocol that moves that message from your outgoing server to the recipient's incoming mail server. Without SMTP, email as we know it would not function.
SMTP operates over specific network ports, and the port you choose has significant implications for security, deliverability, and compatibility. Port 25 was the original SMTP port and is still used for server-to-server relay, but most residential ISPs and cloud providers now block it to curb spam. Port 587 emerged as the modern standard for client-to-server email submission and supports STARTTLS for encryption. Port 465 was originally designated for SMTPS (SMTP over SSL) and is still used by some providers, while port 2525 serves as a popular alternate when 587 is unavailable.
Understanding which ports are open on your mail server matters because a closed or blocked port means your emails cannot leave your infrastructure. This is especially critical for cold emailers, marketers running self-hosted platforms, and developers integrating transactional email. A port check quickly reveals whether the issue lies with your server configuration, your hosting provider's firewall rules, or your local network restrictions.
TLS and SSL encryption are also closely tied to port selection. Modern best practices demand that all SMTP traffic be encrypted in transit to protect credentials and message content. Port 587 with STARTTLS is generally preferred because it begins with an unencrypted handshake and upgrades to TLS, making it more compatible with restrictive firewalls. Port 465 uses implicit TLS, which is also secure but can be blocked by older network equipment.
For email marketers, port availability directly impacts campaign execution. If your ESP connects to port 587 and that port is closed, your campaign may fail silently or queue indefinitely. Regularly testing your SMTP endpoints helps you catch these issues before they affect your send schedule and your sender reputation.
Common SMTP Settings Reference
Different email providers and transactional services use different SMTP hosts, ports, and authentication methods. Below is a quick reference table to help you configure your email client, application, or marketing platform correctly.
| Provider | SMTP Host | Recommended Port | Encryption | Authentication |
|---|---|---|---|---|
| Gmail | smtp.gmail.com | 587 | STARTTLS | OAuth 2.0 / App Password |
| Outlook | smtp-mail.outlook.com | 587 | STARTTLS | OAuth 2.0 / Password |
| Yahoo | smtp.mail.yahoo.com | 587 | STARTTLS | App Password |
| SendGrid | smtp.sendgrid.net | 587 | STARTTLS | API Key |
| Mailgun | smtp.mailgun.org | 587 | STARTTLS | API Key / Password |
Related Tools
Explore these complementary tools to build a complete picture of your email infrastructure, authentication, and deliverability health.
DMARC Record Checker
Verify your domain's DMARC policy to prevent spoofing and improve inbox placement.
SPF Record Checker
Check which IP addresses and servers are authorized to send email on behalf of your domain.
MX Record Checker
Test your domain's mail exchange records to ensure incoming emails are routed correctly.
Email Blacklist Checker
Scan major DNS blacklists to see if your IP or domain is listed and hurting deliverability.
Email Deliverability Guide
A comprehensive resource covering authentication, list hygiene, content best practices, and sender reputation.
DKIM Checker
Verify your DKIM signatures and selector configuration for cryptographic email authentication.
Frequently Asked Questions
Below are answers to the most common questions we receive about SMTP ports, connectivity testing, and troubleshooting email server issues.
What is the difference between SMTP ports 25, 465, 587, and 2525?
Port 25 is the original SMTP relay port, but it is commonly blocked by ISPs to prevent spam. Port 587 is the modern standard for email submission and supports STARTTLS encryption, making it the recommended choice for most clients. Port 465 uses implicit SSL/TLS and is still supported by some providers. Port 2525 is an unofficial alternate submission port that many ESPs offer when 587 is blocked by restrictive firewalls.
Why is port 25 blocked on my network?
Port 25 is frequently blocked by residential internet providers, cloud hosting platforms, and data centers because it has been historically abused by spammers and botnets for sending unsolicited email. If port 25 is blocked on your network, switch to port 587 with STARTTLS for client-to-server submission, or contact your hosting provider to request an unblock if you legitimately need server-to-server relay.
How do I know if my SMTP server supports TLS?
You can check TLS support by testing port 587 or 465 with this tool. If the result shows TLS support as Yes or STARTTLS, the server can encrypt your email traffic. You can also use command-line tools like OpenSSL to verify the certificate chain: openssl s_client -starttls smtp -connect yourhost:587. Always ensure TLS is enabled before sending credentials or sensitive content.
Can I test SMTP ports from a browser?
Browsers cannot initiate raw TCP connections due to security sandboxing, so this tool provides a simulated check based on known provider configurations and heuristics. For a true network-level port scan, use a command-line tool such as telnet, nc, or nmap from a server or workstation with unrestricted outbound access. The simulation here is designed to help you quickly verify expected behavior and catch configuration mismatches.
What should I do if my SMTP port is blocked?
If your preferred SMTP port is blocked, first try an alternate port such as 587 or 2525. Check your server firewall rules to ensure the port is open for inbound and outbound traffic. If you are on a residential connection, contact your ISP to understand their blocking policy. For cloud servers, review your security group or firewall configuration in your provider's dashboard. Finally, verify that your mail server daemon is actually listening on the expected port.