Skip to content
AdminKit

SMTP HELO/EHLO

What is SMTP HELO/EHLO?

EHLO, the extended form of SMTP's opening HELO greeting introduced by RFC 1869 and carried in RFC 5321, asks a mail server which extensions -- STARTTLS, AUTH, SIZE and others -- it supports. AdminKit's MX lookup tool finds the mail servers a diagnostic EHLO command would actually be sent to.

By AdminKit team, Netbase JSC · Updated

HELO is the command an SMTP client sends to identify itself at the start of a mail session, defined in the original SMTP standard; EHLO is the extended version, introduced by RFC 1869 and carried forward in RFC 5321, that a client sends instead to ask the server which SMTP extensions it supports. A server that receives EHLO replies with a multi-line list of capabilities — STARTTLS, AUTH, SIZE, PIPELINING, 8BITMIME, and others, each tracked in IANA’s SMTP Service Extensions registry — that the client can then actually use during that session, whereas a server that only understands plain HELO limits the session to the base SMTP command set with none of those extensions available — Cloudflare’s explainer on SMTP walks through this same EHLO capability exchange as the first step of a mail session. Essentially every modern mail server speaks EHLO; a server or client falling back to bare HELO today usually signals either deliberately minimal tooling or genuinely old software, and a diagnostic SMTP connection is typically opened with EHLO specifically to see that capability list before deciding how to proceed. Servers can also insist on the greeting: Postfix’s smtpd_helo_required parameter, off by default, makes a client introduce itself with HELO or EHLO before sending MAIL or any other command that requires EHLO negotiation.

SMTP HELO/EHLO is part of AdminKit’s email authentication cluster; the full AdminKit glossary lists other related terms.

Frequently asked questions

What does an EHLO response actually tell a client?

A multi-line list of SMTP extension capabilities -- STARTTLS, AUTH, SIZE, PIPELINING, 8BITMIME and others -- that the client can then use during that session, which plain HELO never reveals.

Is plain HELO still commonly used today?

Rarely -- essentially every modern mail server speaks EHLO, so a server or client falling back to bare HELO usually signals either deliberately minimal tooling or genuinely old software.

Why open a diagnostic SMTP connection with EHLO specifically?

To see the server's full capability list -- like whether STARTTLS is offered -- before deciding how to proceed, rather than guessing what the server supports.

When was EHLO introduced, and what replaced it?

EHLO didn't replace HELO -- it was introduced by RFC 1869 as an extended alternative, later carried forward in RFC 5321, and both commands are still valid today.