Skip to main content
PhishEye

About PhishEye

We focus on abusive domains, pages, and channels that impersonate your brand or harvest trust—and the workflows to find them, package evidence, and drive enforcement.

Company

PhishEye Ltd trades as PhishEye. We are incorporated in England and Wales with our registered office at 17 Hanover Square, London W1S 1BN, United Kingdom. We build software for security, fraud, and brand teams who need a single operational picture: prioritised queues, defensible evidence, and tracked outcomes across registrars, hosts, and platforms.

Why we started PhishEye

The company was founded in the United Kingdom by operators who had repeatedly bridged the gap between generic security tooling and what abuse desks actually accept: stable identifiers, clear harm narratives, and follow-ups that do not fall through the cracks when infrastructure rotates. PhishEye exists to make that discipline repeatable—not to promise impossible detection rates or instant takedowns, but to give teams a system that holds up when leadership asks what happened and what changed.

How we work with customers

We ship software first. Where your bottleneck is capacity, time zones, or provider language, we can layer managed support on top—scoped in your order so expectations on timelines and coverage match reality.

  • Prioritised work queues tied to evidence you can defend internally and externally
  • Workflows aligned to registrar, host, and platform abuse channels—not only dashboards
  • Honest positioning on automation: where it accelerates filings and where humans must stay in the loop

Leadership & team

PhishEye is built in London by a cross-functional team spanning product engineering, security research, and customer delivery. Day-to-day leadership sits with the founding operators of PhishEye Ltd. We do not publish individual names or photographs on this page until those bios are finalised for public release; if you need them for diligence, procurement, or press, email us with your deadline.

Long-form guides and blog posts on this site carry named bylines and job titles for transparency; see each article for author attribution. Follow company updates on LinkedIn.

Contact

For security practices, subprocessors, and incident reporting, see Trust and our Privacy policy.