#DNAME
Live, measured metrics for the hashtag #DNAME from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #dname
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 13:29 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 13:29 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 13:29 UTCEverything below is measured over the latest 3 public posts (spanning ~18744 hours).
Posting hours (UTC)
Languages: English (3)
Avg boosts / post: 0.7
Used together with
Top of the latest posts
Unfortunately, our #DNS provider #Transip does not allow #DNAME records, so the practical use for us (community at https://dewar.nl) is zero (unless we migrate to another provider that supports them, but maybe too much hassle there). I cont
TIL about #DNS #DNAME records, which are like CNAME records, but then allow forwarding an entire DNS subtree to another name or domain. This seems perfect for forwarding #DKIM records, e.g. have _domainkey.example.com forward to _domainkey.
#TIL .台湾 is a #DNAME for .台灣 ie Taiwan in simplified Chinese is a DNAME for Taiwan in traditional Chinese. Funny the simplified version exists though as Taiwan uses the traditional one Anyway, nice example of DNAME #DNS https://piaille.fr/@
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/dname