How the message looks
450 4.7.1 Client host rejected: cannot find your hostname, [203.0.113.5] 450 4.7.1 Client host rejected: cannot find your reverse hostname, [203.0.113.5] 450 4.7.1 <mail.example.com>: Helo command rejected: Host not found

What the receiver actually checks

Behind this message sits a three-step check known as forward-confirmed reverse DNS (FCrDNS):

1. 203.0.113.5 → PTR → mail.yourdomain.com (must exist) 2. mail.yourdomain.com → A → 203.0.113.5 (must lead back) 3. the server's HELO name matches step 1 (should match)

If step 1 already fails you get “cannot find your hostname”. If step 2 fails, Postfix says “cannot find your reverse hostname” — the PTR exists but points to a name that does not resolve back to the same IP.

Why this is temporary

The 4 class is deliberate: DNS outages pass, and a receiver does not want to discard mail permanently just because a zone is briefly unreachable. In practice this means you have time — the sending side typically retries for several days. Set the PTR within that window and the mail goes through on the next attempt.

Who sets the record

The PTR is not managed by your DNS provider but by whoever owns the IP block — your host or ISP. On servers with a dedicated IP it is usually in the customer panel under “Reverse DNS” or “rDNS”. Without a dedicated IP, for instance behind shared NAT, no suitable PTR can be set; the route then goes through a provider smarthost or relay.

dig +short -x 203.0.113.5 # query the PTR dig +short mail.yourdomain.com # must return the same IP

One thing to watch: one PTR per IP. Multiple PTR records on the same address are treated as invalid by many receivers.

Find the cause in the actual message

Send or forward the affected email to hello@analyzemy.email. For that exact message the report shows which IP sent it, how SPF, DKIM and DMARC turned out, and where the chain breaks.

Analyze your email now

Last updated: · All error messages