Hypothetical scenario — illustrative, not a customer story
How it could unfold
- A message from the lookalike domain asks a client to update bank details.
- The message copies the agency's signature.
- The client pays to the new account.
- The agency finds out when the real invoice is chased.
Warning signs visible from outside
- A newly registered domain resembling the agency name.
- DMARC not enforcing on the agency domain.
What PixelPrivate would have shown you
Possible lookalike domain
A registered domain resembles the agency domain, shown for review. We cannot prove intent.
DMARC policy is not enforcing
Mail from the genuine domain could also be spoofed.
What you would do
- Review the lookalike and tell clients how bank changes are announced.
- Enforce DMARC.
- Report the domain to the registrar and consider registering variants.
Honest limits
PixelPrivate can show the exposures listed above. It cannot guarantee that an incident would not happen, and it cannot see anything outside its checks. PixelPrivate does not detect intrusions or fraud. This scenario describes no real company, person, quote or statistic.
