certificate authority
for security engineers, devops
Why this scored 16
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
Outlook
low confidence · estimate, not a guarantee7-day
~0
range 0–13
14-day
~0
range 0–16
30-day
~0
range 0–21
Signal history
7-day window (free)projected trajectory (estimate, not a guarantee)
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.
- 130
I’ve factored the RSA keys of a Certificate Authority…from the 90s
Revealed 1990s CA RSA keys expose legacy trust weaknesses in current TLS ecosystems. · for security engineers, PKI admins
lobstersSteady 2 · certificate authoritysecurity3d ago - 216
I've factored the RSA keys of a Certificate Authority from the 90s
Legacy CA keys can be broken, exposing older TLS certificates to compromise. · for security engineers, devops
hackernewsSteadysecurity3d ago