What Email Spoofing Is and Why It Matters to You
Email spoofing is when someone sends an email that appears to come from a person or company you trust, but actually comes from someone else. The sender forges the "from" address — the part that shows in your inbox — so the message looks legitimate. You might see an email that claims to be from your bank, your employer, or a friend, but it's actually from a scammer trying to trick you into clicking a link, downloading a file, or sending money.
Spoofing works because email systems were built decades ago without strong verification built in. Anyone with basic technical knowledge can make an email appear to come from almost anywhere. The good news is that modern email providers and domain owners have added tools to block most spoofing before it reaches you, and you can turn those tools on.
The difference between spoofing and phishing is important: phishing is the scam itself (the fake message trying to trick you), and spoofing is the technique used to make the phishing email look real. Stopping spoofing means fewer fake emails get through at all.
Key Takeaways
- Email spoofing happens when a sender forges the "from" address to impersonate someone you trust, and modern email systems can block most of it if the right settings are turned on.
- Three technical standards — SPF, DKIM, and DMARC — tell email servers whether an incoming message really came from the domain it claims to come from.
- Gmail, Outlook, and most business email systems check these standards automatically, but you can see the results yourself by looking at the email headers.
- If you own a domain or manage email for a business, setting up SPF, DKIM, and DMARC records in your domain settings is the most direct way to stop others from spoofing your address.
- When you receive a suspicious email claiming to be from a known sender, checking the actual sender address and looking for authentication badges in your email client can reveal the forgery.
How Email Authentication Standards Block Spoofing
Three technical standards work together to verify that an email really came from the domain it claims to come from. Your email provider checks these standards on every incoming message, though you don't see the work happening.
SPF (Sender Policy Framework) is a list that domain owners publish saying "these servers are allowed to send email from our domain." When an email arrives claiming to be from example.com, the receiving server looks up example.com's SPF record and checks whether the sending server is on the approved list. If it's not, the email fails the SPF check.
DKIM (DomainKeys Identified Mail) adds a digital signature to every email. The sending server signs the message with a private key, and the receiving server verifies the signature using a public key published by the domain. If someone changes even one character in the email after it's signed, the signature breaks and the email fails DKIM.
DMARC (Domain-based Message Authentication, Reporting and Conformance) is the policy layer. A domain owner publishes a DMARC record that says "if an email fails SPF or DKIM, reject it" or "quarantine it" or "just monitor it." DMARC also tells the receiving server where to send reports about emails that fail authentication, so the domain owner knows if someone is trying to spoof their address.
What You See When Authentication Works
In Gmail, Outlook, and most modern email clients, you'll see a small badge or icon next to the sender's name if the email passed authentication checks. Gmail shows a checkmark in a circle next to verified senders. Outlook shows a similar verification badge. These badges mean the email really came from the domain it claims to come from.
If an email claims to be from your bank but has no verification badge, that's a red flag — your bank's domain almost certainly has DKIM and SPF set up, so a real email from them would show the badge. Scammers often spoof addresses from well-known companies, and those companies' authentication standards will catch most of the forgeries.
You can also check the email headers yourself if you want to see the technical details. In Gmail, click the three dots next to the email and select "Show original." In Outlook, click the three dots and select "View message details." Look for lines that say "SPF: pass" or "DKIM: pass" or "DMARC: pass." If you see "fail" on any of these, the email did not come from the domain it claims to come from.
How to Check the Real Sender Address
Scammers often use a display name that looks legitimate while hiding the actual email address. Your email client shows the display name by default, but the real sender address is underneath. Learning to spot the difference is one of the fastest ways to catch spoofing.
In Gmail, hover your mouse over the sender's name and a small popup will show the actual email address in angle brackets. In Outlook, click the sender's name and a card will appear with the full address. If the display name says "Bank of America" but the actual address is something like "bankofamerica-verify@randomdomain.com," that's spoofing — the real Bank of America would send from a domain they own.
Real companies always send from their own domain. If you're unsure, don't click any links in the email. Instead, go to the company's website directly (type the address into your browser yourself, don't click a link in the email) and look for a contact page or phone number. Call or message them through the official channel to ask whether they sent the email.
Setting Up Authentication If You Own a Domain
If you own a website or manage email for a business, you can set up SPF, DKIM, and DMARC records to stop others from spoofing your domain. These records live in your domain's DNS settings, which you access through your domain registrar (GoDaddy, Namecheap, Google Domains) or your web hosting provider.
For SPF, you publish a text record that lists the servers allowed to send email from your domain. If you use Gmail for business, your SPF record might say "v=spf1 include:_spf.google.com ~all," which tells receiving servers that Google's servers are allowed to send on your behalf. Your email provider usually gives you the exact SPF record to add.
DKIM is more complex because it involves generating a public-private key pair. Most email providers (Gmail, Outlook, Mailchimp, etc.) generate the DKIM record for you and tell you exactly what to add to your DNS. You paste the public key into your domain settings, and the provider keeps the private key on their servers to sign outgoing emails.
DMARC is the policy you set after SPF and DKIM are working. A basic DMARC record might say "v=DMARC1; p=quarantine; rua=mailto:admin@yourdomain.com," which tells receiving servers to quarantine emails that fail authentication and send you a daily report. You can start with "p=none" to monitor without blocking, then move to "p=quarantine" or "p=reject" once you're confident legitimate emails won't be blocked.
What to Do When You Receive a Spoofed Email
If you get an email that claims to be from someone you know but looks suspicious, don't click any links or read any attachments. Instead, contact the person or company through a phone number or website you find yourself — not through contact information in the email.
Report the email to your email provider. In Gmail, click the three dots and select "Report phishing." In Outlook, click the three dots and select "Report." These reports help your email provider improve its filters so fewer spoofed emails reach you in the future. You can also forward the email to the real company being impersonated — most companies have a phishing report address like abuse@company.com or security@company.com.
If the email is spoofing your own domain (someone is sending emails that appear to come from your address), contact your email provider's support team and ask them to investigate. They can check the email headers and confirm whether the email actually came from your account or from an outside attacker. If it came from outside, your provider may help you strengthen your authentication settings.
Why Some Spoofed Emails Still Get Through
Even with SPF, DKIM, and DMARC in place, some spoofed emails reach inboxes because not every email server checks these standards, and not every domain has set them up. Older email systems and some smaller providers don't verify authentication. Additionally, a domain owner might set a weak DMARC policy (like "p=none") that monitors spoofing but doesn't block it.
Scammers also use techniques beyond straightforward spoofing. They might register a domain that looks similar to a real one — like "amaz0n.com" instead of "amazon.com" — and set up legitimate authentication on that fake domain. They might also compromise a real email account and send from that account, which passes all authentication checks because the email really did come from that account.
This is why authentication standards are one layer of defense, not the only one. Your email provider also uses machine learning to spot patterns of phishing, and you should always verify unexpected requests by contacting the sender through a channel you know is real.
Frequently Asked Questions
Can I stop spoofing completely?
No, but you can block most of it. SPF, DKIM, and DMARC stop the majority of spoofing attempts, but they don't catch every technique scammers use. Staying alert and verifying unexpected requests through a known contact method is still necessary.
What does it mean if an email fails SPF but passes DKIM?
It means the email came from a server not listed in the domain's SPF record, but the digital signature is valid. This can happen if a domain's SPF record is incomplete or outdated. The email is not necessarily spoofed, but it's worth checking the sender address carefully.
Do I need to set up DMARC if I already have SPF and DKIM?
SPF and DKIM do the verification work, but DMARC tells receiving servers what to do with emails that fail. Without DMARC, a server might accept a spoofed email even if it fails SPF and DKIM. Setting up DMARC with a reject policy is the strongest protection.
Why do some legitimate emails get marked as spoofed?
Usually because the sender's domain doesn't have SPF, DKIM, or DMARC set up correctly, or because the email was forwarded or modified in a way that breaks the digital signature. If you trust the sender, you can add them to your contacts or safe sender list, which tells your email provider to trust future emails from that address.
Can I report a spoofed email to the police?
You can report it to the FBI's Internet Crime Complaint Center (IC3) at ic3.gov if the email is part of a scam that caused you financial loss. For general phishing reports, your email provider and the impersonated company are usually more helpful because they can take when ready action to block the sender.