Inbox Deliverability Verified for 2026 Expert Reviewed

SMTP Greeting (HELO/EHLO) and Reverse DNS (PTR) Guide

Direct Answer Quick Summary for Senders:

The SMTP greeting (HELO/EHLO) is the initial identification string sent by your mail server, and it must match a fully qualified domain name (FQDN). Reverse DNS (PTR) maps the sending IP address back to that same hostname. Destination mail servers verify Forward-Confirmed Reverse DNS (FCrDNS); if the greeting, PTR record, and forward A record do not match, the connection is rejected.

Key Takeaways

Forward-Confirmed Reverse DNS (FCrDNS) is mandatory for delivery to Google, Yahoo, Microsoft, and corporate MTAs.
The SMTP HELO greeting must be a valid FQDN (e.g., mail1.yourdomain.com), not an IP address or localhost.
A missing or generic PTR record (e.g., 198-51-100-10.static.isp.com) triggers instant spam classification.
171mails automatically provisions matching FCrDNS for all 4 Dedicated IPs on your account.

1. The Forward-Confirmed Reverse DNS (FCrDNS) Triangle

ComponentDNS TypeLookup DirectionExample Value
1. Forward A RecordA RecordHostname → IPmail1.yourdomain.com → 198.51.100.10
2. Reverse PTR RecordPTR RecordIP → Hostname198.51.100.10 → mail1.yourdomain.com
3. SMTP GreetingEHLO BannerMTA Handshake String220 mail1.yourdomain.com ESMTP

2. Verifying FCrDNS from the Command Line

# 1. Check Reverse DNS (PTR)
dig -x 198.51.100.10 +short
# Expected output: mail1.yourdomain.com.

# 2. Check Forward DNS (A)
dig A mail1.yourdomain.com +short
# Expected output: 198.51.100.10

# 3. Test SMTP Greeting
nc -v mail1.yourdomain.com 25
# Expected response: 220 mail1.yourdomain.com ESMTP

3. 171mails Multi-IP FCrDNS Architecture

Every dedicated IPv4 and IPv6 address on 171mails is configured with custom, brand-aligned forward and reverse DNS records, satisfying FCrDNS checks across all global receiving servers.

Frequently Asked Questions

No. PTR records can only be configured by the entity that owns the IP address subnet (your hosting or SMTP relay provider). 171mails configures PTR records for your dedicated IPs directly.

Almost 100% of mailbox providers will reject the connection immediately with error code <code>501 Syntax error in parameters or arguments</code> or <code>550 HELO must be an FQDN</code>.

Yes! Google and Yahoo strictly enforce reverse DNS for IPv6 connections. An IPv6 address without a valid PTR will be rejected outright.
Enterprise Bulk Email Relay

Flawless Forward-Confirmed Reverse DNS (FCrDNS) Out of the Box

Avoid technical DNS rejection codes. 171mails configures matching PTR, HELO greetings, and forward records for all 4 Dedicated IPs.

  • Pre-configured FCrDNS across 4 Dedicated IPs (2 IPv4 + 2 IPv6)
  • 100% compliance with Google & Yahoo 2026 PTR rules
  • 100M+ real-time suppression list scrubbing
  • Test your PTR configuration in our $5 (₹399) sandbox
100K Email Plan
$29 /mo
4 Dedicated IPs Included

Related Questions & Guides

Deliverability, Warmup & Reputation
How to Setup SPF, DKIM & DMARC for Bulk Email (Guide)

Step-by-step tutorial to configure SPF, DKIM (2048-bit), and DMARC for bulk email marketing. Meet Google an...

Deliverability, Warmup & Reputation
IPv4 vs. IPv6 for Bulk Email Deliverability (2026 Analysis)

IPv4 vs IPv6 for bulk email marketing: Which delivers better inbox rates? Discover dual-stack routing, Goog...

Deliverability, Warmup & Reputation
Google & Yahoo Bulk Sender Requirements 2026 (Compliance Guide)

Complete guide to Google & Yahoo bulk sender requirements in 2026. Learn mandatory SPF, DKIM, DMARC, RFC 80...

Deliverability, Warmup & Reputation
How to Stop Bulk Emails Going to Spam (10-Step Fix)

Discover why your bulk emails are going to spam and how to fix it immediately. Step-by-step checklist for D...