PTR / reverse DNS
A DNS record that maps an IP address back to a hostname — providers expect sending IPs to have valid reverse DNS.
Say it out loud
“The sending server's address has to resolve back to a real name. On a shared platform this is theirs, not ours.”
A PTR record lets a receiver look up an IP address and get a hostname back. Gmail and others expect sending IPs to have one, and expect it to agree with the forward lookup. On shared platform IPs the platform owns this entirely; on a dedicated IP it becomes somebody's job, and that somebody may be you.
The IP resolves back to a name. That is the PTR.
And the name resolves forward to the same IP. One direction is not enough — both, or it fails.
Your platform
Klaviyo, Mailchimp and friends do this automatically.
What goes wrong
Taking a dedicated IP and never setting the PTR, because it is configured at the hosting provider rather than in your normal DNS panel and nobody thinks to look there.
The dated rule behind this
A definition is not a citation. These are the pages with the primary source, the date it was published, and what to do about it.
See also
Where this sits
Stop 3, it leaves your building. Your platform hands the message to a mail server, which stamps it with proof of who sent it.