Email spoofing

Email spoofing is falsifying an email's sender information so that it appears to come from a person or domain that did not send it.

The sender you see is not the whole message

An email has several identities: the display name, the address in the visible From field, the envelope sender used during delivery, and sometimes a separate Reply-To address. They can differ for legitimate reasons, such as a mailing service handling messages for a company. Attackers can also exploit those differences.

Display-name spoofing copies the name you recognize. Exact-domain spoofing goes further by claiming the real domain in the sender address. Sending from a lookalike domain is another way to impersonate someone, but uses a different domain.

What the authentication results mean

For ordinary mail, SPF checks whether the sending server is authorized for the envelope-sender domain. Messages with an empty envelope sender use the server’s HELO identity instead. DKIM verifies a signature associated with a signing domain. Neither result alone tells you that the visible From domain is authentic.

DMARC adds alignment: at least one passing SPF or DKIM result must align with the visible From domain. Its policy tells receivers how the domain owner wants failures handled; a monitoring policy is not a request to reject them. Receivers also apply their own handling rules.

A 2024 FBI, State Department, and NSA advisory showed North Korean spearphishing messages with passing SPF and DKIM checks but failing DMARC alignment. Some also directed replies to a different address. The press-inquiry article explains why an ordinary-looking request for comment can still need verification.

Mail sent through a compromised genuine account may pass authentication. A pass therefore does not prove that the person named in the message approved it, or that its request is safe. Keep sender authentication and business approval as separate decisions.

Sources

See it in practice