EFF Cover Your Tracks — Learn

---

What EFF Cover Your Tracks — Learn actually does

The methodology behind the entropy figure the test reports, plus the aggregate results, written to be checked rather than merely cited.

What can and cannot be measured about EFF Cover Your Tracks — Learn

This entry has no repository, so none of the usual repository fields exist for it — no push date, no release tag, no archive flag, no licence identifier. Its state comes from one measurement only: the register requested the address and recorded what came back. Anything in the range 200 to 399 makes a non-repository entry ACTIVE, and that clause is the one the first edition of the rubric did not have at all, which is why dataset entries carried no state under it.

Read that for exactly what it is. It says the thing is reachable. It does not say the page still works correctly, because no HTTP status can carry that. Where a stronger signal exists — a repository, a version, a dated revision — this register prefers it, and where one does not, it prints the weaker signal and names it as weak rather than dressing it up.

Where EFF Cover Your Tracks — Learn sits in this catalogue

EFF Cover Your Tracks — Learn is filed in section 08, datasets, leaderboards & public statistics, whose scope is this: Published distributions and population data. The only place in this catalogue where a percentage means anything, because someone else measured it and says how. An entry sits in exactly one section here. Where a project could defensibly go in two, it is placed where a reader would look for it first rather than where it fits most tidily, and that is an editorial decision rather than a measured one.

Filed beside it in the same section: AmIUnique global statistics (ACTIVE), tlsfingerprint.io (ACTIVE), JA4 Database (ACTIVE). Comparing an entry against its own section-mates is more informative than comparing it against the catalogue as a whole, because everything in a section is answering roughly the same question and the differences left over are the ones that matter.

There is no licence field, because there is no source to licence — this is a dataset rather than a code repository. It is grouped instead with every other entry the rubric marks ACTIVE, which is the axis that actually distinguishes entries of this kind from one another.

What to settle before you adopt EFF Cover Your Tracks — Learn

This is the document to read before quoting any bits-of-entropy number anywhere, because it defines what the number is relative to. A published method is what separates this from the scanners that print a score and explain nothing.