Phishing simulation domains
Overview
Security-awareness vendors test an organization’s staff by sending them simulated phishing. The messages come from domains the vendor owns, named to look like everyday services — a secure file share, a document delivery, a password reset. That makes them hard to triage: every signal you would score as phishing (a generic service name, a file-share lure, a per-recipient token in the link path) is present by design.
Recognizing one changes the answer. A link on a simulation vendor’s domain is consistent with an authorized simulation run through that vendor rather than an attack; the domain identifies the vendor’s infrastructure, not which organization commissioned this particular message. Clicking is still unwise, for a different reason: the click is recorded against the recipient. Reporting the message is the expected response to a simulation.
The matching rule
Match on the registrable domain (PSL+1; see datapulse_help(topic="methodology")), and only exactly:
s.securefileshares.comandqa2.securefileshares.comreduce tosecurefileshares.com→ Cofense.eu-securefileshares.comis not Cofense. It was a separate registration (2025-11-12, a different registrar, no Cofense registrant) on unrelated hosting; the DataPulse RDAP crawl of 2026-09-08 shows it inredemption period, and on 2026-10-19 the .com registry’s RDAP answered that the name does not exist. A lookalike of a simulation domain is a reason for more caution, not less — someone chose a name that borrows the vendor’s credibility.securefileshares.com.example.netis a hostname underexample.net. A vendor’s label appearing somewhere in a hostname proves nothing.
Known simulation-vendor domains
Every entry below is established by a public source; nothing is listed by inference. Absence from this list does not mean a domain is not a simulation domain — most vendors do not publish their lists.
Cofense PhishMe
| Registrable domain | Evidence (checked 2026-09-10) |
|---|---|
securefileshares.com | WHOIS Registrant Organization “Cofense, Inc.”; registrar MarkMonitor (IANA 292); created 2011-10-31. Certificate Transparency logs show staging., qa1., qa2., dev., perf., testdrive. and eu. subdomains — an operated product, not a parked name. |
Cofense does not publish its domain list; its customers receive it for allowlisting.
Microsoft Defender for Office 365 — Attack simulation training
Microsoft publishes the URLs Attack simulation training uses, all of the form https://www.<domain>, in Get started using Attack simulation training — Simulations. As retrieved 2026-09-10 the table lists 130 domains under 50 labels:
attemplate — .com
bankmenia — .com, .de, .es, .fr, .it, .org
banknown — .de, .es, .fr, .it, .org
browsersch — .com, .de, .es, .fr, .it, .org
docdeliveryapp — .com, .net
docstoreinternal — .com, .net
doctorican — .de, .es, .fr, .it, .org
doctrical — .com, .de, .es, .fr, .it, .org
doctricant — .com
doctrings — .com, .de, .es, .fr, .it, .org
exportants — .com, .de, .es, .fr, .it, .org
financerta — .com, .de, .es, .fr, .it, .org
financerts — .com, .de, .es, .fr, .it, .org
hardwarecheck — .net
hrsupportint — .com
mcsharepoint — .com
mesharepoint — .com
officence — .com
officenced — .com
officences — .com
officentry — .com
officested — .com
passwordle — .de, .fr, .it, .org
payrolltooling — .com, .net
prizeably — .com, .de, .es, .fr, .it, .org
prizegiveaway — .net
prizegives — .com
prizemons — .com
prizesforall — .com
prizewel — .com
prizewings — .com
resetts — .de, .es, .fr, .it, .org
salarytoolint — .com, .net
securembly — .com, .de, .es, .fr, .it, .org
securetta — .de, .es, .fr, .it
shareholds — .com
sharepointen — .com
sharepointin — .com
sharepointle — .com
sharesbyte — .com
sharession — .com
sharestion — .com
supportin — .de, .es, .fr, .it
supportres — .de, .es, .fr, .it, .org
techidal — .com, .de, .fr, .it
techniel — .de, .es, .fr, .it
templateau — .com
templatent — .com
templatern — .com
windocyte — .com
Only the TLDs shown are listed: bankmenia.net, for example, is not a Microsoft simulation domain.
Not listed
- KnowBe4 assigns phish-link domains per customer account (console: Phishing > Domains) and publishes no public list — see Manage Phish Link Domains.
- Proofpoint Security Awareness (ThreatSim) — Proofpoint’s own safelisting documentation requires a customer login, so its domains could not be confirmed from Proofpoint itself.
Confirming an unlisted candidate
A name that sounds like a simulation domain proves nothing — real phishing uses the same names. To attribute one:
- Registration.
datapulse_live_rdapgives the registrar IANA ID (MarkMonitor is 292), the creation date, the nameservers and the abuse contact. Comparing it with a listed domain of the same vendor (registrar, lock depth, nameservers) shows whether the candidate is kept the same way. - History.
datapulse_dns_rdap_historyshows whether the name has sat at the same registrar for years, anddatapulse_dns_dphistorywhether its nameserver, mail and hosting providers have been stable. Simulation platforms are long-lived; a domain registered last week at a retail registrar is not a vendor’s platform. - Evidence from outside these tools. No DataPulse tool returns the registrant organisation (see
datapulse_help(topic="rdap")on registrant data), and none enumerates the hostnames in Certificate Transparency logs. A WHOIS or RDAP record from another source that names a security-awareness vendor as registrant is strong evidence, and so are CT entries showing environment subdomains (staging.,qa.,dev.), which a vendor platform usually has and a throwaway phishing domain rarely does; both are evidence the analyst brings, not something this server produces.
A vendor attribution rests on a tool result that names it; a domain no result names is unattributed.
What a listed simulation domain means
When the destination is on a listed simulation domain:
- It is consistent with an authorized phishing simulation using that vendor. The domain establishes the vendor; it does not independently establish that the recipient’s organization authorized this message, which is why reporting it through the normal channel is the safe course either way.
- A click is recorded. Simulation links carry a per-recipient token, so a click is recorded against the recipient and commonly assigns training. Microsoft’s FAQ: “Each URL in the simulation email is tied to an individual user.”
- Reporting is what the test measures, through the mail client’s report-phishing button or the organization’s usual channel.
- A listed domain does not make the link safe, and the message is not one to ignore.
Related topics
datapulse_help(topic="methodology")- registrable domains (PSL+1)datapulse_help(topic="rdap")- registration data, lock depth, and what registrant data is unavailabledatapulse_help(topic="lookalike_domains")- names that borrow a brand’s credibility
Generated from the live server (DataPulse MCP v0.9-341-g27163c2) on October 20, 2026. Your AI assistant reads this page by calling datapulse_help(topic="phishing_simulation").