#rfc9432
Live, measured metrics for the hashtag #rfc9432 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #rfc9432
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-28 10:07 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-28 10:07 UTCNo related tags with measured usage found for #rfc9432.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 10:07 UTCEverything below is measured over the latest 2 public posts (spanning ~0.3 hours).
Posting hours (UTC)
Languages: English (2)
Avg boosts / post: 0.5
Used together with
Top of the latest posts
@shaft OK. So I believe it is legitimate to consider TXT multi-strings concatenation makes sense for SPF records in #rfc7208 and “tokenization” is more appropriate for catalog zones in #rfc9432.
#dns question about multi-string TXT records: #rfc7208 section 3.3 says they shall be concatenated w/o space. Is this applicable only to #spf records? Looking at #rfc9432 (catalog zones) section 4.3.2.1 the group example "operator-y" "bar"
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/rfc9432