#dnsperf
Live, measured metrics for the hashtag #dnsperf from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #dnsperf
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.online (Mastodon public tags API) · fetched 2026-10-19 23:17 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.online (Mastodon public search API) · fetched 2026-10-19 23:17 UTCNo related tags with measured usage found for #dnsperf.
Live pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-10-19 23:17 UTCEverything below is measured over the latest 17 public posts (spanning ~32710 hours).
Posting hours (UTC) — busiest: 09:00
Languages: English (17)
Avg boosts / post: 2.8
Top of the latest posts
#dnsperf v2.13.0 released! Added new option `-O tls-sni=...` to set TLS SNI @dnsoarc #DNS #TLS #SNI #DOT #DOH #Performance #Testing #OpenSource https://github.com/DNS-OARC/dnsperf/releases/tag/v2.13.0
#dnsperf v2.16.0 released! - TLS session resumption and `SSLKEYLOGFILE` support added for DNS-over-TLS and DNS-over-HTTPS, work contributed by Ranya Sharma (PCH) and Sara Dickinson (Sinodun IT) #DNS #Performance #Testing #OpenSource https:/
Last Wednesday, @dnsoarc released #dnsperf v2.15.1, bringing a fix for DNS-over-HTTPS response handling along with updates to QTYPE support and CI improvements. #dnsperf v2.15.1 released! - Fixed receiving DNS-over-HTTPS responses, incorrec
#dnsperf across platforms
every network with a public tag surfaceFollow #dnsperf 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/dnsperf