PTR lookup
Query in-addr.arpa for the PTR hostname assigned to your sending IP.
Free tools
Enter your outbound SMTP IPv4 address to look up PTR reverse DNS, verify forward-confirmed rDNS (FCrDNS), and optionally check HELO/EHLO hostname alignment.
PTR lookup, forward-confirmed rDNS (FCrDNS), and optional HELO/EHLO alignment for outbound SMTP IPs.
Capabilities
Missing or misaligned PTR records are a common cause of deferrals and spam-score hits on strict receivers.
Query in-addr.arpa for the PTR hostname assigned to your sending IP.
Confirm the PTR hostname forward-resolves back to the same IPv4 address.
Show forward DNS answers for each PTR hostname.
Optional HELO/EHLO hostname check against PTR for SMTP identity consistency.
Flag multiple PTR records on one IP — often discouraged for mail servers.
Image captcha, session verification, and per-IP rate limits for public use.
How to use
Use the IPv4 address your SMTP server connects from — not your domain.
Paste the EHLO/HELO hostname from SMTP diagnostics or provider docs.
Complete the image challenge before running the lookup.
PTR must exist and forward-resolve to your IP for FCrDNS pass.
Request PTR updates from your host/ISP if misaligned, then re-check.
Reverse DNS maps an IP address to a hostname via PTR records in in-addr.arpa (IPv4). Mail receivers often check that your sending IP has a PTR record and that the hostname forward-resolves back to the same IP — forward-confirmed reverse DNS (FCrDNS).
Your SMTP HELO/EHLO hostname should align with the PTR name. Mismatches can increase spam scores or cause connection issues with strict providers.
PTR is controlled by whoever owns the IP block — typically your VPS host, dedicated server provider, or ISP. You cannot set PTR in your domain DNS unless you own the IP range.
When moving providers, request PTR updates before sending production mail from a new IP.
IPv4 only in this checker. It does not open SMTP connections or verify banner/STARTTLS on the host.
FCrDNS for IPv6 uses ip6.arpa — not covered here; use your provider’s IPv6 rDNS tools.
For regulatory context on commercial email in the United States, see the FTC CAN-SPAM compliance guide.
Delivery note: MailFleet helps users manage campaigns through their own sending providers. Delivery outcomes depend on sender reputation, DNS authentication, content quality, recipient engagement, list quality, provider rules, and mailbox filtering systems.
Your hosting provider, ISP, or email provider for dedicated IPs. Request PTR changes through their support panel or ticket system.
Get started
SMTP diagnostics, provider profiles, and campaign logs — confirm IP and hostname alignment before send.
Available on
Same desktop experience across every platform — one workflow for your entire team.