#dns64
Live, measured metrics for the hashtag #dns64 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #dns64
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 08:15 UTC1 uses by 1 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 08:15 UTCNo related tags with measured usage found for #dns64.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 08:15 UTCEverything below is measured over the latest 40 public posts (spanning ~31470 hours).
Posting hours (UTC) — busiest: 04:00
Languages: English (30) · German (4) · Dutch (2) · French (1)
Avg boosts / post: 1.2
Top of the latest posts
Installed our new router box yesterday and switched our LAN from dual-stack to #IPv6 only with #DNS64 + #NAT64 Did quite a lot of this one-handed, as Alonso fell asleep on my arm. 🐶💤
Introductory post: this is my public sub-account for #IPv6 content; my main account is linked in my profile. I support the complete roll-out of IPv6, including intermediate efforts like dual-stack support and #NAT64 #DNS64 #CLAT, with the u
I've been playing with an IPv6 only network today. No DNS64/NAT64 like the last time I tried this experiment. Full cold turkey. Most of the services we rely on at home work ok, with one or two exceptions (IT technical stuff Mrs P will never
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/dns64