Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated
Email spoofing forges the sender field to make a message appear to come from a trusted address. IETF's RFC 5321 explains that SMTP, the protocol used to send and receive email, allows a person with ordinary technical knowledge to construct a message that appears to originate from somewhere else.
How does email spoofing work?
The sender field in a letter can carry any name the writer chooses. A postal service does not verify whether that name is genuine. The same gap exists in email.
IETF's RFC 7208 states that email can be forged in several ways, and that existing protocols do not restrict how the MAIL FROM field is used. Japan's Ministry of Internal Affairs and Communications explains that targeted attack emails sometimes display a legitimate-looking domain in the sender field. Verifying whether a message actually came from an authorized sender requires checking the sender authentication records on the domain. For the technical setup and configuration details, see the email authentication page.
Why does email spoofing matter?
When the displayed sender cannot be trusted, messages that appear to come from a business partner or a manager cannot be taken at face value. IPA explains that business email compromise uses impersonation and other techniques to deceive recipients in a carefully crafted way. A spoofed message can be indistinguishable from a genuine one on the receiving side.
SPF is a framework defined in RFC 7208. The domain owner publishes a list of servers authorized to send mail from that domain, allowing the receiving side to check whether the sending server is on that list. Reducing the use of your domain in spoofed messages requires the sending side to configure SPF, DKIM, and DMARC. On the receiving side, any request to change payment details should be confirmed through a channel other than email.
The free URL check shows how your domain's authentication records appear from outside. To discuss how to set up both the sending and receiving sides, contact us.
Related terms
- SPF, DKIM, DMARC: three sender authentication records that together reduce email impersonation.
- Phishing: a broad term for techniques that use fake messages or sites to steal credentials.
- Business email compromise (BEC): a fraud that impersonates executives or partners to redirect payments to a fake account.
- Spear phishing: a targeted fake email crafted to deceive a specific person or organization.
Frequently asked questions
If the sender address looks correct, is the email genuine?
Not necessarily. RFC 7208 states that email can be forged. For requests such as changing a payment destination, verify by a method other than email.
How do you reduce impersonation of your own domain?
Configure sender authentication records — SPF, DKIM, and DMARC — on your domain. Start by checking the current state of those records.
Next step
For the setup and configuration of sender authentication, see the email authentication page. The free URL check shows how your domain's authentication records appear from outside. To discuss your sending and receiving defenses, contact us.
Frequently asked questions
If the sender address looks correct, is the email genuine?
Not necessarily. RFC 7208 states that email can be forged. For requests such as changing a payment destination, verify by a method other than email.
How do you reduce impersonation of your own domain?
Configure sender authentication records — SPF, DKIM, and DMARC — on your domain. Start by checking the current state of those records.