Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
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.

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.
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.
Email authentication was added in layers, and all three parts are needed.
From header through a concept called alignment, and tells receivers what to do when checks fail: none, quarantine, or reject. It also provides aggregate reports showing who is sending mail as your domain.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.
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:
p=none with an rua address, and collect aggregate reports for several weeks.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.
DMARC stops exact-domain forgery. It does nothing about:
privla-security.co.uk passes its own SPF, DKIM, and DMARC perfectly well. Defences here are domain monitoring, registrar-level brand protection, and gateway rules for newly registered and visually similar domains.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.
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.
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.
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.
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.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.