networkutils.org

Home / Email Tools / SMTP Test

SMTP Test

Email Tools

Full SMTP conversation, banner, TLS and relay check.

Run this tool: the interactive SMTP Test loads here (requires JavaScript). Input: Mail host — e.g. mail.example.org.

Description

The SMTP Test opens a full SMTP conversation with a mail server, capturing the banner, the supported extensions, whether STARTTLS is offered, and whether the server would accept (relay) a message for an external recipient.

Features

✓ Full SMTP banner and greeting capture
✓ EHLO extension and STARTTLS detection
✓ Open relay test for unauthorised submission
✓ Connection and response timing

How to Use

Enter a mail host (mail.example.org) and run the tool. The probe connects on port 25 and walks through the SMTP handshake, reporting each stage.

Input: Mail host — e.g. mail.example.org.

Understanding the Results

The output shows the server banner, the extensions advertised by EHLO (SIZE, PIPELINING, STARTTLS, AUTH…), whether TLS was negotiated, and the result of a relay test. An "open relay" result is a serious misconfiguration that allows anyone to send mail through your server and will get you blacklisted quickly.

Common Use Cases & Examples

→ Check a mail server banner and EHLO extensions after a change.

→ Confirm STARTTLS is offered on port 25.

→ Verify a server is not an open relay before going live.

→ Diagnose why a remote mail server cannot deliver to yours.

Frequently Asked Questions

What is an open relay and why is it bad?

An open relay accepts outbound mail from unauthenticated, arbitrary senders for arbitrary recipients. Spammers abuse it to send bulk mail through your server, which gets your IP blacklisted and your legitimate mail blocked. Always require authentication for submission and restrict relay to authenticated users or trusted IPs.

Should my mail server offer STARTTLS?

Yes. STARTTLS upgrades a plain SMTP connection to TLS opportunistically. While it is not a substitute for MTA-STS/DANE, offering it improves transport confidentiality and is expected by modern mail providers.

What port does this test use?

The test connects on port 25 (SMTP), which is used for server-to-server delivery. Submission from email clients uses port 587 (or 465 for implicit TLS) and requires authentication; those ports are not tested here.

About this tool

Maintained by
networkutils.org editorial team
Last updated
September 2026
Testing methodology
MX, SPF, DKIM and DMARC checks query DNS TXT/MX records through Node.js dns.promises; the SPF check walks include/redirect mechanisms recursively and counts the RFC 7208 10-lookup limit; the SMTP Test opens a real SMTP conversation on port 25; the Blacklist Check queries the Spamhaus ZEN DNSBL for each A/MX address.
Technical references
RFC 5321 — SMTP · RFC 3207 — SMTP STARTTLS