Evidence & validation
Evidence you can inspect.
Two different things live on this page: the validation record for the platform itself, and the measured figures behind the claims made across this site.
What you receive when we find one.
This is a complete finding report, filled with synthetic data. Nothing here is a real customer or a real detection — it shows the shape and the depth of what lands in your inbox.
Where the 83 seconds actually falls
Distribution of the gap between a certificate entering a Certificate Transparency log and our pipeline reading it. Measured on 19 August 2026 over a 150-second live run.
Certificates
| Seconds | Certificates | % |
|---|---|---|
| 60–70 Seconds | 157 | %2.3 |
| 70–80 Seconds | 2,453 | %35.8 |
| 80–90 Seconds | 2,304 | %33.6 |
| 90–100 Seconds | 918 | %13.4 |
| 100–110 Seconds | 379 | %5.5 |
| 110–120 Seconds | 220 | %3.2 |
| 120–130 Seconds | 111 | %1.6 |
| 130–140 Seconds | 85 | %1.2 |
| 140–150 Seconds | 70 | %1.0 |
| 150–160 Seconds | 67 | %1.0 |
| 160–170 Seconds | 57 | %0.8 |
| 170–180 Seconds | 21 | %0.3 |
| 180–190 Seconds | 7 | %0.1 |
| 190–200 Seconds | 7 | %0.1 |
| 200–210 Seconds | 2 | %0.0 |
Sample: 6,858 certificates · 6,858 of 6,858 timestamps readable · median 83 s · p90 108 s. This is not the time to find a fake site — only the gap between the log's own timestamp and our reading of it.
Measured figures behind the claims.
Each figure below comes from a run that was recorded, with its date. Nothing here is extrapolated into a rate or a guarantee.
| Figure | Value | Measured | What it does not mean |
|---|---|---|---|
| Active Certificate Transparency logs | 9 | 19 Aug 2026 | Not a claim of complete log coverage |
| Automated checks passed | 284 / 284 | 19 Aug 2026 | Covers the codebase's own test suite, not production behaviour under load |
| Runtime application dependencies | 0 | 19 Aug 2026 | Applies to the application runtime, not to the hosting platform |
| Certificates read in one 30-second local run | 1,174 | 19 Aug 2026 | A single measured run, not a sustained throughput rate |
| Median time from CT log entry to our pipeline | 83 s | 19 Aug 2026 | Not the time to find a fake site — only the gap between the log's own timestamp and our reading of it |
What we have not measured.
These are published as unknown rather than estimated.
- Detection coverage as a percentage of all impersonating domains.
- Production uptime.
- False-positive rate across a labelled dataset.