22 Oct 20265 minutes read
Waseem OsmanDMARC PractitionerStop a Phishing Email Generator from Spoofing Your Domain

Phishing email overview:
- A spoofed email that reaches inboxes points to missing DMARC enforcement, not attacker skill.
- SPF checks a different domain from the one recipients see, so it can't stop a forged "From" header.
- Only p=reject blocks spoofed email. A p=quarantine policy still delivers it to Spam or Junk.
- A weaker
sp=tag can leave subdomains exposed even when the root domain is at p=reject.
Attackers no longer need technical skill to impersonate a brand. A phishing email generator gives anyone the means to send messages that display a trusted domain. Many organizations still haven’t enforced the email authentication controls that stop those messages from reaching inboxes.
When a spoofed email carrying your domain lands in a customer’s or supplier’s inbox, it doesn’t prove the attacker is sophisticated. It shows that your domain isn’t at full DMARC enforcement.
This article explains how these tools abuse authentication weaknesses, which controls stop them, and four checks security and IT teams can run across their domains.
How a Phishing Email Generator Works
A phishing email generator does two jobs. It builds a convincing message, and it sends that message so it appears to come from a trusted organization.
The technique a phishing kit relies on for that second job is header spoofing. The tool sets the visible “From” header to your domain while sending from infrastructure you don't control. Receiving servers only reject the message if your DMARC policy tells them to.
Why a Phishing Email Generator Gets Past SPF
SPF confirms that a message came from a server authorized to send for the domain. It doesn’t check the “From” header the recipient sees. A phishing kit can use a domain that passes SPF for the attacker’s own server while displaying your domain in the “From” header.
The result is an SPF pass for the wrong domain. This is why header spoofing succeeds against domains that rely on SPF without DMARC enforcement.
DKIM and DMARC close that opening:
- DKIM adds a cryptographic signature. An attacker can’t produce a valid signature for your domain without your private key. DKIM signatures usually survive forwarding, although they fail when an intermediary modifies the message.
- DMARC requires that the domain authenticated by SPF or DKIM aligns with the “From” header domain. At p=reject, it tells receiving servers to reject messages that fail this check.
With both in place, header spoofing of your exact domain fails. The attacker must either accept rejection or move to a domain they control, such as a lookalike domain.
Four Checks That Show Whether Your Domain Can Be Spoofed
Run each check across every domain your company owns, including domains that don’t send email.
1. Confirm the Policy Is p=reject
A p=none policy only monitors. It generates reports but doesn’t ask receivers to block anything. A p=quarantine policy sends failing messages to Spam or Junk, where recipients can still find and open them.
Only p=reject blocks unauthenticated email from reaching the recipient. Use the DMARC record checker to confirm the policy published on each domain.
2. Check That Subdomain Policy Doesn’t Weaken Protection
Subdomains inherit the p= policy when the sp= tag is absent. The risk comes from a record that explicitly sets a weaker subdomain policy, such as sp=none.
A domain at p=reject with sp=none leaves subdomains like invoices.example.com open to header spoofing.
3. Make Sure Every Legitimate Sender Signs With DKIM
Third-party platforms such as HR systems, ticketing tools, and marketing platforms should sign email with a DKIM key. Senders that rely on SPF alignment alone fail DMARC when their email is forwarded.
4. Review Aggregate Reports for Unknown Sources
Aggregate reports list every source sending email with your domain, along with authentication results. Receivers send these reports at every policy level, including p=reject, so you keep visibility into spoofing attempts after enforcement.
Unknown sources fall into two groups: unapproved internal tools and active abuse. Business units adopting SaaS tools without IT approval often appear here first. Reviewing raw XML reports manually across dozens of domains takes time that stretched security teams rarely have.
Documenting Enforcement for Audit and Risk Teams
Audit committees and boards increasingly expect proof that email authentication controls work, not only that they exist. Evidence that holds up in an audit includes:
- p=reject published on every domain, including domains that don’t send email
- DKIM signing configured for all authorized third-party senders
- Aggregate reports reviewed on a defined schedule, with a named owner
How Sendmarc Can Help
Moving every domain to p=reject is rarely blocked by the protocol itself. It stalls because teams can’t see every sender, departments add tools without approval, and security staff lack the time to analyze reports across regions and brands. Sendmarc removes that burden so attackers can’t use your domain.
DMARC Management identifies every legitimate and unauthorized source sending email on your behalf, across root domains, subdomains, and inactive domains. Sendmarc’s implementation team takes your organization from p=none to p=reject in stages, so billing, notification, and marketing email keep reaching inboxes.
Protection doesn’t stop at enforcement. Continuous monitoring and optimization keep authentication current as vendors, domains, and teams change. Lookalike Domain Defense monitors newly registered domains that resemble yours, covering the vector attackers turn to once header spoofing is blocked.
For risk and compliance teams, Sendmarc provides reporting on authentication status by domain and a DMARC compliance certificate as verifiable proof of enforcement. That gives audit committees and boards credible evidence without adding manual work for IT.
Explore DMARC Management and Lookalike Domain Defense to see how Sendmarc takes every domain to p=reject and monitors for the lookalike domains attackers use when spoofing fails.


