#tls1_0
Live, measured metrics for the hashtag #tls1_0 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #tls1_0
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 · mastodon.social (Mastodon public tags API) · fetched 2026-07-29 02:25 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.social (Mastodon public search API) · fetched 2026-07-29 02:25 UTCNo related tags with measured usage found for #tls1_0.
Live pulse
measured · mastodon.social (Mastodon tag timeline) · fetched 2026-07-29 02:25 UTCEverything below is measured over the latest 3 public posts (spanning ~60218 hours).
Posting hours (UTC)
Languages: English (2) · German (1)
Avg boosts / post: 0.3
Top of the latest posts
@rysiek The WebUI of my Switch only supports #tls1_0. For this reason I disabled #https , because http sites are easier to access via #firefox then unsafe encrypted sites. 😎
Had to tell a customer yesterday that their new electronic postage machine was too insecure to connect to the network. This is since it ran #tls1_0 and had no way of using anything else. And it also runs on #windowsce 5.0 #msp #infosec #tls
This is it, less than a week 👌 🎉 https://www.pcisecuritystandards.org/ #ByeBye #SSL #TLS1_0
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/tls1_0