#certificatetransparency
Live, measured metrics for the hashtag #certificatetransparency from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #certificatetransparency
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-10-04 05:34 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-10-04 05:34 UTCNo related tags with measured usage found for #certificatetransparency.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-10-04 05:34 UTCEverything below is measured over the latest 35 public posts (spanning ~77060 hours).
Posting hours (UTC) — busiest: 08:00
Languages: English (29) · German (4) · French (2)
Avg boosts / post: 3.7
Top of the latest posts
Today I published an update on the #Canonical supported #upki project, which brings browser-grade Public Key Infrastructure to Linux through the efficient #CRLite data format, with the core revocation engine now functional and available to
Certificate Transparency logs hold billions of certificates but searching them is brutal. crt.sh is slow, truncates results, and crashes constantly. We built a better CT search tool at CertKit (free to use). Part 1 of my series explains why
Eric Brandes dropped Part 2 of our CT logs series. The performance gap is staggering. Tiled logs: 100M+ records/day RFC 6962: Low millions (with throttling) Google throttles hard. Cloudflare's Nimbus is decent. Let's Encrypt's tiled logs ab
#certificatetransparency across platforms
every network with a public tag surfaceFollow #certificatetransparency straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.
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/certificatetransparency