What is an SMTP test?
This SMTP test resolves a domain's primary MX, opens a connection on port 25, reads the greeting banner and the EHLO capability list, and reports whether the server offers STARTTLS for encrypted delivery. It is a quick way to confirm a mail server is reachable and TLS-capable.
How the SMTP handshake and EHLO work
When you submit a domain, IPeek looks up its MX records, picks the highest-priority host, and opens a TCP connection on port 25. The server answers with a 220 greeting banner that names the software, usually Postfix, Exim, or Microsoft. IPeek then sends EHLO and parses the multi-line 250 response listing supported extensions. Look for STARTTLS in that list: it signals the server can upgrade the plaintext session to an encrypted TLS channel before any mail data is exchanged. SIZE, PIPELINING, and 8BITMIME commonly appear alongside it.
How to read your SMTP test results
Start with the banner. A 220 response means the server accepted the connection and is ready. If STARTTLS appears in the EHLO capability list, the server can encrypt inbound delivery; its absence means mail may be relayed in cleartext. A timeout or refused connection usually points to a firewall, a wrong MX target, or a host that is down. Note that port 25 is for server-to-server delivery, not client submission, which uses 587 or 465. The banner hostname should match your PTR record to satisfy receivers that check it.
Common SMTP problems and how to fix them
Connection refused or timed out is the most frequent failure, typically a firewall blocking port 25 or an MX record pointing at the wrong host. A missing STARTTLS line means the receiving server cannot negotiate TLS, so add a certificate and enable it in your MTA. A self-signed or expired certificate still advertises STARTTLS but breaks strict TLS policies like MTA-STS and DANE. If the banner reports a generic hostname that differs from your reverse DNS, fix the PTR record, because many receivers reject mail when the banner and PTR disagree.