Fraudox is a brand protection service that ends in removal. Monitoring watches the surfaces impersonation moves between - domains, social accounts, app stores and marketplaces, and your own content - a person verifies every finding, and the takedown side files it with the host, registrar, platform or app store that will act. Standalone takedowns work the same way for a single link, with no monitoring attached.
Impersonation does not stay on one surface. The same actor who registers a lookalike domain also opens the matching social account, and republishes the app after it is pulled. These are the four surfaces we watch and file on.
Credential-harvesting pages, cloned sites and the lookalike domains registered to carry them.
Apps published under your name, and merchants selling under it. Both run on dispute processes of their own.
Your own work reposted, resold or leaked. This is the copyright track, and it does not require a trademark.
The same four beats whether the finding came from our monitoring, from your detection stack, or from you sending us a link.
Monitoring covers the four surfaces above: new registrations, new impersonation assets, and everything we have already removed for you. Your own detection feed can pipe in via API instead, or as well.
A person confirms the finding is real abuse rather than a false positive, and works out which host, registrar, platform or app store will actually act on it.
The case goes through the takedown workflow: evidence assembled once and reused, filed with the party that can act, escalated when it goes quiet.
Removal is confirmed before it counts against your plan, and the target goes back on the monitored list for the next attempt. That is the part an alerting tool cannot do.
Most brand protection stops at the alert. Fraudox is measured on removals it can confirm, and bills on them.
A tool that tells you about a lookalike domain has moved the work to your legal team, not done it. Every finding here is carried through filing and escalation until the host, registrar or platform acts.
Findings are verified by hand before anything is filed. That is slower than an automated alert feed and it is the reason the filings land: an abuse desk that receives false positives stops reading your reports.
Trademark certificates, WHOIS records and letters of authorization are collected on your first case and reused on every one after it, including the re-files when something comes back.
A takedown counts against your plan when removal is confirmed, and not before. Detection that finds nothing costs nothing.
Nothing about the single-case route has changed. Send one link, provide the documents that platform asks for, and pay only if the target comes down - no monitoring, no plan, no conversation with sales. Most people arrive that way. Monitoring is what you add when the same actor keeps coming back.
See the six takedown servicesMonitoring and filing run on the same channel list: registrars, hosts, CDNs, social networks, app stores, marketplaces and messaging platforms. The monitoring page covers what is watched on each; the platforms page covers who each report goes to and how it escalates.
Monitoring, verification and removal, across four surfaces: domains and websites, social media and impersonation, apps and marketplaces, and your own content. Monitoring watches for new abuse and for anything we have already removed coming back; a person verifies each finding; and the takedown side files it with the host, registrar, platform or app store that will act on it.
Most brand protection tools end at the alert, and leave the filing to you. Fraudox is measured on removals: the finding is verified, filed, escalated and confirmed, and only a confirmed removal counts against your plan. The output is content that is gone, not a count of alerts delivered.
Yes, and nothing about it has changed. Send one link, provide the documents that platform asks for, and pay only if the target comes down. Monitoring is what you add when the same actor keeps coming back, or when you want the next attempt caught before your customers see it.
Not for everything. The copyright track - your own work reposted or resold - runs on DMCA notices and is open to an individual creator with no trademark at all. Impersonation and counterfeit tracks are stronger with a trademark, and we tell you which documents a given platform will ask for before you spend time gathering them.
No. Point it at us instead: findings from a SIEM, a SOAR, in-house scripts or a CSV export can feed in via API, and we take over verification, filing and escalation. Our own monitoring is there for teams that do not have a detection stack, and it is aimed specifically at the abuse types we can remove.
Every case is tracked in your dashboard, whether you submitted it yourself or monitoring found it, and you see each action taken on it there. A removal is confirmed before it counts against your plan, and the API returns case state for teams that want results inside their own tooling.
Social media & impersonation
Accounts and pages built to pass as you or your staff, on every network that runs an impersonation queue.