tls
for security engineers
Why this scored 5
every term, weightedIts fastest-moving item, measured against the pace of its own source
Whether that velocity is itself speeding up, as a per-hour rate
How many independent communities its own items come from
Decays to zero over 14 days, counted from when we first saw it
Subtracted once something is big and old — sized by its biggest item, aged from when we first saw it
Weights are hand-tuned, not learned — we're calibrating them against realized trends as history accumulates. On an entity's first sighting there's no previous reading to compare against, so acceleration starts from a neutral prior rather than a measurement, and velocity falls back to engagement over its whole lifetime until a second reading exists. Full methodology
Signal history
7-day window (free)The evidence
The live items this entity's score aggregates — every community independently talking about it right now. This is the corroboration, shown, not claimed.
- 118
GRO Hid My TLS Handshake's Real Packet Split, Even Over a Real Network
GRO alters TLS handshake packet splitting, affecting network reliability. · for security engineers
devtoSteadysecurity31d ago - 218
Only 10 of the top 1000 sites hide the hostname you are visiting. I built the tool that counts.
Tool shows only 10 of top sites hide hostname, exposing privacy risk. · for security engineers, privacy researchers
devtoSteadysecurity41d ago - 312
TLS Certificate Validation on Linux
TLS certificate · for security engineers
lobstersSteadysecurity103d ago