SMTP Tester Online: Check Your Mail Server Settings in Seconds
CodexFuse Team · 2026-11-05T21:04:59.307Z · 8 min read min read
Test your SMTP server settings in seconds with a free online SMTP tester. Check ports, authentication and TLS — and fix the email failures costing you orders.
An SMTP tester is a free online tool that checks whether your mail server accepts connections, authenticates your login, and can actually send an email — before your customers ever notice a problem. Instead of guessing why order confirmations stopped arriving, you enter your server details, run the test, and get a clear pass or fail in seconds.
If your business runs on email — invoices, booking confirmations, password resets, quotes — a broken SMTP connection is a silent revenue leak. This guide shows you how to test your settings properly, how to read the result, and what to do when the test fails.
What does an SMTP tester actually check?
An SMTP tester opens a real connection to your mail server on the port you specify, negotiates encryption if required, attempts to log in with your credentials, and reports exactly where the process succeeds or breaks. It checks the connection, the port, the encryption handshake, and the authentication — the four points where outgoing mail most often fails.
Why do emails stop arriving when nothing changed?
Most SMTP failures feel sudden, but they usually have a quiet cause. A hosting provider changes a port policy. A password expires after a migration. A firewall rule tightens. Your mail provider drops support for an old encryption method. Nothing on your screen looks different — but the mail pipeline is broken.
- The silent failure: contact forms still submit, so you assume the email went out. It never left the server.
- The delayed failure: emails queue for hours and arrive long after the customer has moved on — or bounce back days later.
- The authentication failure: a password changed during a migration, and every send attempt now fails at login.
The cost is rarely the email itself. It is the missed booking, the unpaid invoice, the customer who assumes you ignored them. An SMTP tester catches these breaks in minutes instead of letting them run for weeks.
How do I run an SMTP test in under two minutes?
The CodexFuse SMTP tester is free and unlimited. You need a free account to use it, and the test itself takes less than a minute once your details are ready.
- Open the SMTP tester: go to the SMTP tester tool and sign in to your free CodexFuse account.
- Enter your SMTP details: type in the server address, port, encryption type, and the mailbox username and password.
- Run the connection test: the tool connects to your server, negotiates encryption, and attempts authentication, reporting each step as it goes.
- Read the result: a pass means your server is ready to send. A fail tells you exactly which step broke — connection, encryption, or login.
Test with the exact mailbox your business actually sends from, not a personal account. A test that passes on the wrong credentials tells you nothing about the mailbox your customers depend on.
Which port should I use?
Port choice is one of the most common sources of SMTP confusion. The right port depends on your provider, and using the wrong one produces a connection timeout that looks like the server is down.
| Port | Encryption | When to use it |
|---|---|---|
| 25 | None or STARTTLS | Server-to-server relay; often blocked by ISPs for outbound mail |
| 465 | SSL/TLS from the start | Implicit encryption; common with many business email providers |
| 587 | STARTTLS | The modern standard for submitting mail from apps and websites |
When in doubt, start with port 587 and STARTTLS. It is the most widely supported combination for sending mail from a website or app.
A worked example: the bakery whose order emails vanished
Crumb & Craft, a fictional online bakery in Lahore, takes cake orders through its website. Each order triggers a confirmation email to the customer and a copy to the bakery's orders inbox. One Monday, the owner notices something odd: the website shows 14 orders over the weekend, but only 3 confirmation emails arrived.
The owner opens the SMTP tester and enters the details from the hosting panel: server mail.crumbcraft.pk, port 587, STARTTLS, username [email protected], and the mailbox password. The test fails at the authentication step: "535 Authentication failed". Connection and encryption both pass.
The cause: the hosting provider had migrated mailboxes to a new server the previous Friday. The migration reset mailbox passwords to a temporary value and emailed the new password — to the same mailbox that was now unreachable. The website was still using the old password, so every send attempt failed at login.
An authentication failure after a migration or password change is the single most common SMTP problem for small businesses. If your test fails at login and nothing else changed, check whether your provider recently migrated your mailbox or forced a password reset before you touch anything else.
What does each test failure actually mean?
A failed test is useful only if you know what the failure means. Each step points at a different fix.
- Connection timeout: the server never answered. Check the address for typos, try a different port, and confirm your host or firewall is not blocking outbound SMTP.
- Connection refused: the server is reachable but nothing listens on that port. You are almost certainly on the wrong port.
- TLS handshake failure: encryption negotiation broke down. Try the other encryption mode, or check whether the server's certificate expired.
- Authentication failed (535): the server answered and encryption worked, but the login was rejected. Reset the password and check for app-password requirements.
- Relay access denied (554): you authenticated, but the server refuses to send to that recipient. The mailbox may lack sending permission.
What an SMTP tester cannot tell you
Passing an SMTP test proves your server can send. It does not prove your emails reach the inbox. Several problems live entirely outside the SMTP connection.
- Spam folder delivery: mail can send perfectly and still land in spam. That is a reputation and authentication problem — SPF, DKIM, and DMARC records. Check your domain with an SPF record checker.
- Blacklisted IP: if your server's IP is on a blocklist, receiving servers reject your mail no matter how clean your settings are. Run a blacklist checker on your domain or IP.
If your business email keeps failing silently, move it to CodexFuse — fully managed business email on credits, with the server, DNS records, and deliverability handled for you instead of left to trial and error.
Get Started with CodexFuseWhen is the problem bigger than one test?
A single SMTP test fixes a single break. But if you are testing your mail server every few weeks, the real problem is that nobody owns your email. Small businesses usually end up in one of two places: a DIY setup where the owner is the accidental IT department, or a provider that charges a monthly subscription for every mailbox and still leaves the configuration to you.
On CodexFuse, business email is a concrete workflow, not a settings page you have to interpret. Create your mailboxes on your own domain, point your domain's DNS at the managed mail service, and let the platform handle the SPF, DKIM, and DMARC records that keep your mail out of spam. You pay in credits for what you actually use — mailboxes, storage, sending volume — with no per-seat subscription and no lock-in. If a test fails later, the support team investigates the server side instead of handing you a log file.
For a fuller walkthrough of setting email up properly from the start, read our business email setup guide for beginners. And if deliverability is your recurring headache, the story of how one nonprofit fixed email deliverability in 30 days shows what a systematic fix looks like.
Still seeing emails vanish after a passing test? Read how to stop worrying about email deliverability for the full checklist of DNS, reputation, and content fixes.
Frequently Asked Questions
Is an SMTP tester free to use?
Yes. The CodexFuse SMTP tester is free and unlimited,
Do I need to share my real email password?
Yes, the tester needs your real mailbox password to attempt authentication — that is the point of the test.
What is the difference between port 587 and port 465?
Port 587 uses STARTTLS, which starts as a plain connection and upgrades to encryption. Port 465 uses implicit SSL/TLS, which encrypts from the very first byte. Most modern providers recommend 587, but some still require 465
Why does my SMTP test pass but emails still go to spam?
A passing test only proves your server can send. Spam placement depends on your domain's SPF, DKIM, and DMARC records, your sending reputation, and the content of the message.
How often should I test my SMTP settings?
Test after every change — a migration, a password reset, a new website, a provider switch — and run a quick check monthly even when nothing changed.
Stop guessing whether your mail works
Email is the one system every business assumes is working until a customer proves it is not. A two-minute SMTP test replaces that assumption with evidence: your server connects, your login works, and your mail can actually leave the building.
And if you are tired of being your own mail administrator, move your business email to CodexFuse now — set up your mailboxes on your domain, let the platform handle the DNS records and deliverability, and pay only in credits for what you use. Your next order confirmation should reach your customer, not a dead server.
