#rfc7208

Live, measured metrics for the hashtag #rfc7208 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 #rfc7208

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 #rfc7208 — $240.06/yr→Buy on hashtag.space (web3)
card via hashtag.org · tokens via hashtag.space
0
Uses / 7 days
Mastodon
0
Accounts / 7 days
Mastodon
3
Recent posts
Mastodon
~0/hr
Recent pace
Mastodon · last 3
0
Avg reactions / post
Mastodon · last 3

Day-by-day usage

measured · mastodon.social (Mastodon public tags API) · fetched 2026-07-28 08:35 UTC
0
07-22
0
07-23
0
07-24
0
07-25
0
07-26
0
07-27
0
07-28

0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.

Related hashtags

measured · mastodon.social (Mastodon public search API) · fetched 2026-07-28 08:35 UTC

No related tags with measured usage found for #rfc7208.

Live pulse

measured · mastodon.social (Mastodon tag timeline) · fetched 2026-07-28 08:35 UTC

Everything below is measured over the latest 3 public posts (spanning ~9984 hours).

Posting hours (UTC)

00:0012:0023:00

Languages: English (3)

Avg boosts / post: 0.3

Top of the latest posts

  • 🚨 We’re updating how we handle SPF records! In alignment with RFC 7208 recommendations, we are discontinuing support for the dedicated SPF record type (RR type 99). Going forward, all SPF records should be defined exclusively as TXT record

    Trusty@[email protected]♥ 0↻ 02025-08-11 13:27 UTCView post →

  • @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.

    Guillaume-Jean Herbiet@[email protected]♥ 0↻ 02024-06-21 14:03 UTCView post →

  • #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"

    Guillaume-Jean Herbiet@[email protected]♥ 0↻ 12024-06-21 13: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/rfc7208