Corrections
Tell us we are wrong
Every number on this site is a claim about a published record, and a claim can be wrong: the record can have moved, the source can say something else, or we can simply have read it badly. This page is how that gets fixed — and the log of every time it already has.
Same day, not next quarter
A factual correction with a source behind it is made the day it arrives, and the record’s updated date moves with it. Nothing waits for a release.
The score moves too
Rank is derived by sorting on the security score, so a correction that changes a field can change the score and reorder the register. There is no version of this where we quietly keep the old order.
And it is written down
Every change to a scored field is recorded with what it was, what it became and when — and published in the log. A site that scores others on transparency does not get to edit itself silently.
What we need before a number can move
The model scores the state of the published evidence, not our opinion of a provider. So a correction has to arrive in the same currency: a source we can read. “This is wrong” cannot enter the pipeline; “this is wrong, here is the page that says so” can be acted on the same day.
Reporting a security problem
If you have found a vulnerability in this site — not in a VPN we review — send it through the third form, Something else, with A security problem as its kind. Leave an address if you want to hear back, and we will confirm within two working days.
We do not run a bounty programme and will not pretend otherwise, but we will credit you on this page if you want the credit and will not chase anyone who reports in good faith.
If the vulnerability is in a provider’s service rather than ours, report it to them. If they have no route for that, tell us — the absence of one is itself a fact about that provider.