#dnsprivacy
Live, measured metrics for the hashtag #dnsprivacy from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #dnsprivacy
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 08:31 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 08:31 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 08:31 UTCEverything below is measured over the latest 12 public posts (spanning ~65800 hours).
Posting hours (UTC) — busiest: 16:00
Languages: English (10)
Avg boosts / post: 1.8
Top of the latest posts
We have launched our DNS privacy service early this year (and forgot to make a Mastodon post). This free service is built with a focus on privacy, transparency and reducing reliance on centralized corporate infrastructure. It supports DNS-o
🔍 So, you want to choose a public DNS resolver, huh? Just whip out your crystal ball and predict which of the 29 options won’t sell your data or collapse under a stiff breeze. 🌀 Who knew you needed a PhD in "DNS-ology" to pick one? 😅 htt
a Private DNS setup that ACTUALLY protects you https://apertatube.net/w/1CC5zgeUDP8QGPoEKq5MhY
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/dnsprivacy