#tls12
Live, measured metrics for the hashtag #tls12 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #tls12
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-27 09:30 UTC1 uses by 1 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-27 09:30 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 09:30 UTCEverything below is measured over the latest 8 public posts (spanning ~56752 hours).
Posting hours (UTC)
Languages: English (5) · German (2) · Dutch (1)
Avg boosts / post: 1
Top of the latest posts
I'm not someone who keeps reposting Microsoft blogs and updates. At least not all of them. But this one caught my eye! https://techcommunity.microsoft.com/blog/azuresqlblog/azure-sql-is-retiring-the-%E2%80%9Cno-minimum-tls%E2%80%9D-mintls-n
Just stumbled over «The Illustrated TLS 1.2 Connection» (again). You can easily see the different messages and hover over the byte ranges to get a short explanation. Or click on the «Annotations» button to see details about each of the fiel
Scheint nicht die Ursache zu sein, auf einem Windows 2016 läuft die Kommunikation trotzdem, obwohl der auch max. #TLS12 unterstützt. Ist wohl irgendwas an diesem einen Client.
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/tls12