Email goes to spam: what to check before blaming one record
Passing one DNS authentication check does not guarantee inbox placement. Receiving systems evaluate a broader set of technical and behavioural signals, which is why deliverability work needs evidence from message headers, sending logs, bounces, and the actual sending program.
Verify authentication for the domain the recipient sees
Inspect SPF, DKIM, and DMARC results in a delivered test message. Alignment matters; a third-party sender can technically sign a message while still failing the policy expected for the visible From domain.
Check server identity and reputation
For direct SMTP sending, forward DNS, reverse DNS, hostname, TLS, and IP reputation can affect trust. Shared sending services also have reputation systems and rules that customers do not control individually.
Separate transactional mail from bulk behaviour
Password resets and invoices should not depend on the same poorly maintained list or compromised website that sends bulk messages. Use permission-based lists, process bounces and complaints, and control compromised accounts quickly.
Test multiple recipients and read the evidence
One mailbox placing a message in spam is useful but not universal. Test representative providers, inspect authentication headers, and compare message type, links, content, volume, and sending history before making broad changes.