SSQ.AISSQ.AI
English
help!

Phishing & Impersonation Analysis

Where impersonation connects, and how far it reaches

We find impersonation that uses your name, including the cases that have not yet come to light.

We analyse what infrastructure lies behind impersonation that has surfaced, such as fake sites, emails, texts and look-alike domains, and also look at what to improve in your domain's settings.

What is behind the sites and texts impersonating us, and how far have they spread?

The domains and servers involved, impersonation not yet reported, the evidence to use when asking for takedowns, and what to do first.

Expert reviewed

SPREAD More on the same infrastructure SEEN Reported text Look-alike domain INFRA Shared server Another fake site Fake login page Domain to check Unrelated site Relevant Needs checking Not relevant
From a reported impersonation text we follow the look-alike domain to the server behind it, find other impersonation on the same infrastructure, and set aside what is unrelated.

When it fits

  • Fake sites or texts in your name are going around

    If customers or staff tell you fake sites or texts in your name are going around, we check what they connect to and how far they have spread.

  • A payment request went out in your CEO's name

    If a partner received an email in your CEO's name asking for a payment, we look at which domains and sending infrastructure were used, and whether there is room for it to happen again.

  • Domains resembling your name have appeared

    When a domain resembling your name has just been registered, it is worth checking before it is ever used against you.

  • Impersonation keeps coming back

    Impersonation keeps coming back, and new cases need watching for on a regular basis.

The SAFE SQUARE approach

The whole shared infrastructure

We find impersonation that looks different on the surface but is connected behind it, so scattered cases show up as one operation.

Outside, and on your side

Alongside the impersonation infrastructure outside, we look at the settings on your side too, to see whether mail forging your domain would be filtered out.

Evidence for takedown requests

We set out the connections and timing with the evidence, ready to use when you ask for an impersonating site to be blocked or removed.

What we look at

Impersonation takes a different shape every time; below are things we often look at.

Impersonation that has surfaced

  • Impersonating websites
  • Impersonating emails and texts
  • Messages using the names of your executives or staff
  • Impersonating apps and social media accounts

Infrastructure behind it

  • Domains resembling your company name
  • Servers hosting the impersonating sites
  • Infrastructure sending the emails and texts
  • Other impersonation on the same infrastructure

Spread and your own settings

  • When it first appeared and how far it has spread
  • Your name, logo and pages copied for the impersonation
  • Sender verification settings on your domain (SPF, DKIM, DMARC)

How it runs

  1. Set the targets

    Based on the company and brands to look at, the executives' and staff names to watch for and any impersonation already reported, we settle the scope and how it will run.

  2. Follow the infrastructure

    From the impersonation that has surfaced we follow the domains, servers and sending infrastructure, and check for other impersonation on the same infrastructure.

  3. Expert review

    Analysts review the connections and timing, and separate what is confirmed from what still needs checking and what is unrelated.

  4. Report

    We explain how things connect and how far they have spread, what to improve in your domain's settings, and what to act on first.

One reported case is followed in depth as an investigation; where impersonation keeps recurring, it runs as monitoring. Which form it takes is decided with you. See the three ways to run it

What you receive

The infrastructure and how it connects

How the domains, servers and sending infrastructure used for the impersonation connect to one another, with the evidence.

How far it has spread

Other impersonation found on the same infrastructure and when it appeared.

What to improve in your domain's settings

What is missing or weak in the settings that verify mail senders (SPF, DKIM, DMARC).

What to act on first

Based on the likely impact, what to do first: alerting customers and staff, requesting takedowns, tightening your domain's settings.

Phishing is covered in three places. This page deals with the impersonation infrastructure outside and your domain's settings; Security Awareness Training covers phishing drills and the habit of reporting; and Objective-Based Penetration Testing & Red Teaming uses phishing as one step of an attack scenario.

A sample analysis resultFictional example
Starting point

An impersonating text in your name: ‘your points are about to expire’

One text reported by a customer

What we foundFindingEvidence
The look-alike domain in the textImpersonationYour company name with one letter added, registered three days earlier, with a copy of your login page.
Four more domains on the same serverImpersonationSame server, same certificate details, all mimicking your name; two of them had not been reported.
Two domains with similar namesUnrelatedSimilar names, but long-running sites of other companies on separate infrastructure.
Sender verification on your domainNeeds workPart of the setup is missing, so receiving servers would struggle to filter out mail forging your domain.
What to do first
Put out a notice to customers, and send the connections and registration dates as evidence when requesting that the five impersonating domains be blocked or removed. Then complete the sender verification settings on your domain.
  1. Tell us what worries you, or what you want checked. A few lines are enough.

  2. We reply with a proposed scope, schedule and cost, and settle them with you.

  3. Once agreed, the work begins. Results and next steps come to you as it runs.