SMTP egress checks for cold email

SMTP egress checks matter when a cold email operation sends through a direct IP or custom relay. Domain authentication can be correct while the connecting server still looks suspicious because reverse DNS is missing, HELO is unrelated, or the IP is listed.

The checks to run

For each direct sending IP, verify:

• PTR exists.
• PTR is not a generic cloud hostname.
• PTR forward-confirms back to the sending IP.
• HELO/EHLO aligns with the approved mail identity.
• SMTP banner does not contradict the configured hostname.
• Port and banner checks are reachable when probing is enabled.
• The sending IP is not on major blocklists.

Why sending platforms do not cover this

Hosted platforms manage their own egress. But teams using custom SMTP infrastructure own the mail-server identity receivers see. A launch checklist that stops at SPF, DKIM, and DMARC misses that layer.

OutboundQA supports SMTP egress assets so direct-sending teams can include PTR/rDNS, HELO, banner, and IP reputation checks in the same launch verdict. For ongoing ownership after the initial pass, use PTR drift monitoring for custom SMTP egress.

The cold email infrastructure scorecard shows this layer side by side with authentication and link tracking, including which of these server identity checks no tool category covers today.

FAQ

What are SMTP egress checks? SMTP egress checks verify the identity and reputation of a direct sending IP, including PTR, forward-confirmed rDNS, HELO/EHLO alignment, SMTP banner identity, and IP blacklist status.

Who needs SMTP egress checks? Teams sending through custom SMTP relays, dedicated IPs, or self-managed infrastructure need them. Teams using hosted inbox providers usually rely on the provider’s egress.

Are SMTP checks the same as SPF, DKIM, and DMARC? No. SPF, DKIM, and DMARC authenticate the domain. SMTP egress checks verify the server identity that connects to the receiver.