For MSPs and MSSPs
Domain impersonation is the gap in most managed security stacks: it happens entirely outside the client perimeter, so EDR, email security, and patching never see it. This page is the honest version of what we can and cannot do for a provider today.
Start with your own brand
IT and security providers are themselves heavily typosquatted — an attacker impersonating you reaches every client you serve at once, with your credibility attached. Before evaluating this for clients, run a free check on your own domain. It takes a minute, needs no account to see the result, and it is the same scan your clients would get.
What Scale gives you today — €599/month
- 10 protected root domains and 10 team seats on Scale
- Real-time Certificate Transparency monitoring plus daily newly-registered-domain checks
- Sandboxed crawl with screenshot, DOM-similarity score, and a scored verdict per finding
- Full Agent API access and the MCP server, so your own tooling and agents can drive it
- Audit-log export and one-year evidence retention
- Data Processing Addendum included; EU-hosted in Frankfurt
See the full tier breakdown on the pricing page.
What is not built yet
Most vendors would leave this section out. We would rather you find out here than three weeks into an evaluation:
- White-label reporting — Reports and evidence packs carry impersona.io branding.
- Multi-tenant client workspaces — One workspace per account — no per-client isolation or separate client logins.
- A partner margin or reseller tier — Scale is the same published price for everyone today.
These are on the list precisely because providers ask for them. Which one matters most to you decides which one we build first, so tell us rather than assuming we know.
Why this fits a provider stack
- Evidence, not alerts. Every finding carries a screenshot, DNS and certificate records, and timestamps — the material a client incident report actually needs.
- API- and agent-first. Full Agent API and MCP access mean it plugs into your existing automation instead of adding another console for your analysts to check.
- EU-hosted with a DPA. When a client asks where their data lives, the answer is Frankfurt and there is paperwork to back it.
- Self-serve. No sales cycle to get started — run the free check, then subscribe when it has proved itself.
Talk to us
If you place several clients, need volume terms, or one of the unbuilt items above is a blocker, email info@impersona.io. A real conversation beats a partner tier we have not tested on anyone.
Questions
- Can I monitor domains for multiple clients under one account?
- Yes, within the Scale plan’s limit of 10 protected root domains and 10 team seats. Each protected domain is monitored independently with its own alerts and evidence. What does not exist yet is per-client isolation — there is one workspace, so anyone with a seat sees every domain in it.
- Do you offer white-label reports?
- Not yet, and we would rather say so than let you find out during a client QBR. Reports and evidence packs carry impersona.io branding today. If white-label output is what would make this work for your practice, tell us — it is the most-requested thing we have not built, and demand decides the order.
- Is there a partner margin or reseller price?
- No formal partner programme yet. Scale is the same published price for everyone. If you are placing several clients and want to discuss terms, contact us directly — we would rather have a real conversation than publish a tier we have not tested.
- Can my own tooling drive it?
- Yes. Scale includes full Agent API access and the MCP server, so your automation — or your team’s AI agents — can read the threat picture, pull evidence for a specific finding, and track remediation cases without anyone opening a dashboard.
- Where is client data stored?
- The EU (Frankfurt, Germany). A Data Processing Addendum is included on Scale, which matters when your own clients ask where their monitoring data lives.
- What happens when a client needs more than 10 domains?
- Contact us. Per-domain overage pricing is not published yet because we have not set it with real data; we will quote it rather than invent a number on a pricing page.