LeakTrace Core
Zero-access security intelligence, read where the attack begins and delivered inside the products partners already sell.
LeakTrace Core is the LeakTrace reading engine, offered as a metered API. Partners build their own products on it, under their own client relationship and their own compliance.
Where the attack begins
LeakTrace never accesses a system. Every reading is made from beyond the firm's walls: the records it publishes and the names registered around it.
Attackers read businesses with AI agents. The layer puts an agent on the other side, at the attacker's speed.
Where an attack uses a look-alike address an attacker registered from your name, we see it first.
A record carries a reference and the SHA-256 fingerprint of its document. Anyone can check both at getleaktrace.com/verify/ without trusting us.
A partner's product calls the layer for each firm it serves. The partner keeps the client, the brand and the relationship.
Partners who already hold the client
Cyber-insurance brokers and carriers
A dated reading of the applicant at quote time and at renewal.
Managed service providers
A dated reading of each prospect before the first call and of each client after it.
Payment and payee-verification platforms
A reading of the payee's domain before money moves to new details.
Law and accounting networks
A reading of each member firm, on the network's own schedule.
Security vendors
The external layer inside the vendor's own product, under the vendor's name.
Private equity operating partners
A dated reading of each portfolio company, read with its own consent, on one portfolio view with a record for each quarter.
What a partner gets
- Readings by domain in three depths: the first stage, the full reading and the dated record.
- Each reading as JSON: the mail records as published, look-alike domains worth a look, the certificate, website software and the date of the reading.
- The record adds a one-page PDF with a reference and its SHA-256 fingerprint, checkable at getleaktrace.com/verify/.
- A sandbox key that answers the demonstration records only, so a build starts before a block is bought.
- Metered billing against a prepaid block, with a ledger of every reading and the price it was charged at.
Three depths
The mail records, the certificate, look-alike registrations and their mail.
Read with 46 techniques in the first stage and up to 350 look-alike addresses an attacker could register from the firm's name, checked by DNS. Breach data, searches and look-alike pages wait for the full reading.
The full reading's mail, certificate, website-software and breach rows with their evidence, and look-alike domains worth a look, the paid-only parts left out.
Read with 52 techniques, 11 routes to the firm's money, clients, accounts and name and up to 350 look-alike addresses an attacker could register from the firm's name.
The full-depth reading the firm itself consents to, issued as three documents and a dated record of the assessment, with a reference and fingerprint.
Read with the firm's consent, with 75 techniques and 16 routes: the ports on up to 8 hosts, 26 private-file addresses, up to 30 of its own pages and up to 8 domains it owns.
Up to 350 look-alike addresses an attacker could register from your client's name, checked on each reading.
52 techniques attackers use against firms like yours, each checked externally on every reading.
11 routes to your money, your clients, your accounts and your name, checked end to end on each reading.
In our view, attackers run AI agents in swarms: many at once, each trying the combinations of these routes against any firm it can read. We read for the combinations first.
Metered per reading, in prepaid blocks. The figures are in the agreement. Read the agreement.
The partner's own compliance
- Its own compliance: the anti-spam and privacy laws of its own market. Where the partner reads a firm it has no relationship with, the firm's consent comes first.
- No cold use: a reading never opens an unsolicited message to the firm read.
- No resale of raw readings beyond the partner's own product.
- Customer secrecy: a partner never asks the layer, or tells anyone, whether a firm buys from LeakTrace.
The limits, said once
- A reading reveals nothing about who buys from LeakTrace. Every firm is read fresh, the same way.
- No cold use, by us or by a partner.
- Where a partner asks for a look-alike to be taken down, the registrar decides.
- Every finding carries its evidence. The way we find it stays with us.
Request a sandbox key
Security has always faced inward. LeakTrace is the AI layer that faces the attacker.