Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is Email Spoofing?

Email spoofing forges the sender address on a message. SMTP never verified who you claimed to be, so SPF, DKIM, and DMARC were bolted on afterwards to make forgery detectable.

Illustration for the cybersecurity term Email Spoofing
Home / Blog / Cybersecurity Terms / What Is Email Spoofing?
17 November 2026

What Is Email Spoofing?

What Is Email Spoofing?

Email spoofing is the forgery of a message’s sender address so that it appears to come from somebody else. It requires no compromise of the impersonated organisation and no particular skill: the Simple Mail Transfer Protocol, specified in 1982, simply accepts whatever sender a connecting server claims.

Two different sender fields are involved, and confusing them is the source of most misunderstanding about email authentication. The envelope sender, or MAIL FROM, is used by mail servers for delivery and bounce handling and is never shown to the recipient. The header From is what the mail client displays. Forging either is a matter of typing a different value.

Why It Matters

Spoofing underpins a large share of fraud. A message that genuinely appears to come from the finance director carries authority that no amount of security awareness training fully removes. It is the delivery mechanism for business email compromise, for invoice redirection fraud, and for credential phishing that imitates a supplier or a bank. It is also used to damage reputation, by sending abusive or fraudulent mail that appears to originate from a brand.

The Three Controls

Email authentication was added in layers, and all three parts are needed.

A domain publishing DMARC with p=reject and correct alignment cannot be directly spoofed in the header From by compliant receivers. That is a meaningful win, and it is achievable for most organisations within a few months.

Deployment Without Breaking Mail

The failure mode people fear is legitimate mail being rejected, usually from marketing platforms, payroll systems, ticketing tools, or a line-of-business application that nobody remembers configuring. The standard approach avoids this:

  1. Publish SPF and DKIM for every legitimate sending source you can identify.
  2. Publish DMARC at p=none with an rua address, and collect aggregate reports for several weeks.
  3. Work through the reports to find senders you did not know about. There are always some.
  4. Move to p=quarantine, then to p=reject, using the pct tag to phase the change if the volume justifies it.

The NCSC operates Mail Check, a free service for UK public sector organisations that monitors SPF, DKIM, DMARC, and TLS configuration and has been central to the gov.uk estate reaching reject policies. The commercial equivalents do much the same job.

What Authentication Does Not Solve

DMARC stops exact-domain forgery. It does nothing about:

Process controls therefore carry real weight: out-of-band verification of payment detail changes, dual authorisation for bank transfers, and external sender banners that are specific enough to be noticed rather than ignored.

We test both the technical configuration and the human process in our social engineering services, because a domain with a reject policy and no payment verification procedure is still an easy target.

FAQ – Frequently Asked Questions

Does DMARC Stop All Spoofing?

It stops forgery of your exact domain in the visible From header, which is a substantial win. It does not stop lookalike domains, display name abuse from free webmail accounts, or mail sent from a genuinely compromised supplier mailbox. Treat DMARC as closing one specific and very common attack, then address the remainder with monitoring, gateway rules, and payment verification processes.

Why Do I Need Both SPF and DKIM?

They fail in different circumstances. SPF validates the sending server against a published list but breaks when mail is forwarded, and it checks the envelope sender rather than the visible address. DKIM signs the message so it survives forwarding and proves integrity, but says nothing about the displayed domain by itself. DMARC requires at least one of them to pass and to align with the From header.

Is It Safe to Move Straight to p=reject?

Not usually. Most organisations have sending sources nobody has documented: marketing tools, payroll, ticketing systems, scanners, and old applications. Publishing reject before finding them causes legitimate mail to disappear. Start at p=none with aggregate reporting, spend a few weeks identifying every sender, then progress through quarantine to reject.

How Do I Tell Whether a Message Was Spoofed?

Look at the full message headers rather than the displayed name. The Authentication-Results header records the SPF, DKIM, and DMARC outcomes, and the Received chain shows the path the message took. A failed DMARC result on a domain with a reject policy is conclusive. Your mail gateway should record these results and make them searchable for investigations.

Related Terms

You May Be Interested In These

What Is Objection?

Cybersecurity Terms

17 November 2026

What Is Objection?

Read More
What Is DNS over TLS?

Cybersecurity Terms

17 November 2026

What Is DNS over TLS?

Read More