Lookalike spelling
The domain contains a substituted character, extra word, unexpected subdomain, or unfamiliar top-level domain.
Domain Spoofing Awareness
How to Recognize and Report Domain Spoofing
Domain spoofing makes a message or destination appear associated with a trusted domain, either by forging sender information or using a deceptive lookalike name.
Use this guide to turn the threat into a clear employee decision, a safe practice scenario, and a reporting step your organization can support.
Plain-English definition • Warning signs • Safe simulation ideas • Reporting practice
01Understand the threat
Domain Spoofing: a practical definition
Domain spoofing makes a message or destination appear associated with a trusted domain, either by forging sender information or using a deceptive lookalike name.
Some forms involve an exact forged domain while others use lookalike characters, added words, or alternate endings. Employee awareness is one layer; domain authentication and mail controls are separate technical responsibilities.
Source: CISA Phishing Guidance
02Recognition clues
Warning signs employees can check in a domain spoofing message
No single clue proves that a message is malicious. Teach employees to combine the request, sender, business context, destination, and available verification route before acting.
Reply-path difference
The visible sender and the address used for replies point to different organizations without a clear business reason.
Request-context mismatch
The message asks for an action the trusted organization would not normally initiate by email or through that sender.
03Safe response
Move from suspicion to a supported next step
| Moment | Employee action | Program preparation |
|---|---|---|
| Before acting | Use a saved site, known contact, or approved directory rather than typing or following the domain presented in the suspicious message. | Publish the authentic contact, application, or reporting route somewhere employees can reach without using the message. |
| When uncertain | Pause the request and report it through the approved channel with enough context for review. | Explain what the response team needs and how employees will know that their report was received. |
| After an interaction | Stop, contact the responsible team promptly, and describe the action taken without hiding the mistake. | Provide a well-known response route and avoid communications that discourage early reporting. |
Source: NIST: Recognizing, verifying, and reporting phishing
04Practice safely
Domain Spoofing simulation and discussion ideas
Choose one learning objective per exercise. Use fictional people, organizations, accounts, payments, documents, and events, and test the reporting route before sending to employees.
Lookalike comparison
Compare invented domains and ask employees to identify the known route they would use instead.
Supplier request
Practice verifying a fictional vendor message whose sender uses an added word or alternate domain ending.
Display-name contrast
Show why a trusted visible name and a plausible-looking domain still need business-context verification.
05Campaign workflow
Build the exercise around a decision employees can repeat
- 1
Define the behavior
Write down the domain spoofing clue being practiced, the expected action, the authorized audience, and the owner of follow-up.
- 2
Confirm the real process
Test the independent verification route, message-reporting option, response handoff, and employee support path from a representative account.
- 3
Pilot the scenario
Check delivery, links, landing content, accessibility, event records, automated inspection, stop conditions, and the explanation employees will receive.
- 4
Review in context
Reconcile intended recipients, successful deliveries, unique employee events, verified reports, response handling, and completed follow-up before drawing conclusions.
Source: NIST SP 800-50 Rev. 1: Building a Cybersecurity and Privacy Learning Program
06Useful measurement
Evaluate recognition, reporting, and the surrounding process
Record actual counts and denominators for delivery, unique recipient events, reports, and follow-up. Separate automated email inspection and repeat events where the available evidence supports doing so.
A domain spoofing exercise samples one scenario under one set of conditions. It does not establish an employee's intent, overall security awareness, or likelihood of responding the same way to a real attack.
Use findings to improve the real workflow: clearer verification instructions, easier reporting, faster response handling, better role-specific training, or a business control that reduces reliance on email alone.
Common questions
Common questions about Phishmake's features, onboarding, and support, answered to help you get started with confidence.
Can training prevent domain spoofing?
Training can help employees verify suspicious requests, but it does not replace SPF, DKIM, DMARC, secure configuration, or other email controls. Assign technical controls to the appropriate owners.
What is a lookalike domain?
It is a domain chosen to resemble a trusted one through spelling, characters, added words, subdomains, or a different ending. The exact domain and the business context both matter.
Can domain spoofing be used in a phishing simulation?
It can be practiced when the scenario is authorized, proportionate, and tied to a real reporting or verification process. Use domains and destinations reserved for the authorized exercise. Do not register or imitate a real third party in a way that could confuse customers, receive genuine mail, or create trademark and trust risks.
How should domain spoofing simulation results be measured?
Review successful delivery, unique employee events, reports, response handling, and completed follow-up. Include scenario difficulty and operating context, and do not treat a click or report as a complete measure of employee risk.
Sources & further reading
Published by Phishmake · Updated
Keep building your program
All resourcesPut it into practice
Turn domain spoofing awareness into a repeatable response.
Use Phishmake to run controlled employee simulations, review campaign activity, assign relevant training, and keep follow-up records in one workflow.