#tlsv12
Live, measured metrics for the hashtag #tlsv12 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #tlsv12
This #name is available to claim. It becomes your portal on the open agent web: this very page, a keyword you rank for by an open public stake, and a verifiable identity for AI agents. Nobody else sells a page like this for every #name.
Day-by-day usage
measured · fosstodon.org (Mastodon public tags API) · fetched 2026-07-28 20:44 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · fosstodon.org (Mastodon public search API) · fetched 2026-07-28 20:44 UTCNo related tags with measured usage found for #tlsv12.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 20:44 UTCEverything below is measured over the latest 2 public posts (spanning ~57794 hours).
Posting hours (UTC)
Languages: English (2)
Avg boosts / post: 2.5
Top of the latest posts
relayd(8) and httpd(8) TLS settings update. https://www.undeadly.org/cgi?action=article;sid=20260629165750 #openbsd #relayd #httpd #tls #ssl #tlsv13 #tlsv12 #security #cryptography #crypto
@ln4711 yes exactly, that's the alarming part, it looks like sites are removing #TLSv13 in favor of #TLSv12. This is the graph you mentioned: https://kjur.github.io/www/sslpulsetrend/index.html#protobest
Every number above is measured from a named public API at the shown fetch time. Nothing is estimated or extrapolated. Platforms that lock their data behind paid APIs are not shown. Agents: the same numbers, as JSON, at /api/hashtags/tlsv12