#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 · fosstodon.org (Mastodon public tags API) · fetched 2026-07-27 09: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 · fosstodon.org (Mastodon public search API) · fetched 2026-07-27 09:25 UTCNo related tags with measured usage found for #dnsperf.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 09:25 UTCEverything below is measured over the latest 16 public posts (spanning ~30169 hours).
Posting hours (UTC) — busiest: 09:00
Languages: English (16)
Avg boosts / post: 3.3
Top of the latest posts
#dnsperf v2.15.0 released! New features: - statistics on unexpected DNS message IDs - datafiles now support RFC1035 `\DDD` encoding - Thanks to @iscdotorg, `dnsperf` statistics as JSON now available! plus a few bug fixes, see release notes
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 v2.15.1 released! - Fixed receiving DNS-over-HTTPS responses, incorrect handling in callbacks - Update known QTYPE table - Updates to CI #DNS #Performance #Testing #OpenSource https://codeberg.org/DNS-OARC/dnsperf/releases/tag/v2.1
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