#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.

hashtag.org network · sponsored

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.

$240.06/ year · 7-character #name
Claim #dnsperf$240.06/yr
Annual, renews each year
Buy on hashtag.space (web3)
one-timepay once, yours for life
card via hashtag.org · tokens via hashtag.space
0
Uses / 7 days
Mastodon
0
Accounts / 7 days
Mastodon
16
Recent posts
Mastodon
~0/hr
Recent pace
Mastodon · last 16
0.1
Avg reactions / post
Mastodon · last 16

Day-by-day usage

measured · fosstodon.org (Mastodon public tags API) · fetched 2026-07-27 09:25 UTC
0
07-21
0
07-22
0
07-23
0
07-24
0
07-25
0
07-26
0
07-27

0 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 UTC

No related tags with measured usage found for #dnsperf.

Live pulse

measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 09:25 UTC

Everything below is measured over the latest 16 public posts (spanning ~30169 hours).

Posting hours (UTC) — busiest: 09:00

00:0012:0023: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

    Jerry Lundström@[email protected]142026-01-19 10:24 UTCView post →
  • 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

    DNS-OARC@[email protected]022026-04-21 15:39 UTCView post →
  • #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

    Jerry Lundström@[email protected]012026-04-15 12:42 UTCView post →

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