#dnshistory
Live, measured metrics for the hashtag #dnshistory from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #dnshistory
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-29 20:58 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-29 20:58 UTCNo related tags with measured usage found for #dnshistory.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-29 20:58 UTCEverything below is measured over the latest 11 public posts (spanning ~29531 hours).
Posting hours (UTC)
Languages: English (11)
Avg boosts / post: 0.9
Top of the latest posts
Less than a year later https://dnshistory.org/ now has data on 3 billion domains. I'm gonna need a bigger disk 😁 . #DNShistory #domain #domains
Looking at #Cloudflare stats they've blocked around 2.4 million requests in the past 24hrs on my #DNSHistory site. Not sure I'll be turning under attack mode off any time soon 🙄.
I enabled CAA record support on @DNSHistory last night. I thought it would be interesting to see how usage changes over time but they seem a little misunderstood 😬 . You've got those with sequential flags. https://dnshistory.org/dns-record
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/dnshistory