#rfc9460
Live, measured metrics for the hashtag #rfc9460 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #rfc9460
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 14:49 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 14:49 UTCNo related tags with measured usage found for #rfc9460.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-29 14:49 UTCEverything below is measured over the latest 7 public posts (spanning ~16240 hours).
Posting hours (UTC)
Languages: English (7)
Avg boosts / post: 10
Top of the latest posts
Woohoo! #IETF #RFC9460 has been published: "Service Binding and Parameter Specification via the #DNS (#SVCB and #HTTPS Resource Records)". https://www.rfc-editor.org/rfc/rfc9460.html Thank you to everyone has supported and contributed to th
We now publish DNS HTTPS IP hint records for all #OpenStreetMap web services per #RFC9460 Why? Small incremental improvement to performance and privacy. Our DNS handles over 2,000 requests per second. DNS HTTPS query is our 2nd most common
Hey, so #RFC9460 HTTPS/SVCB records are neat, right? They... - speed up your time-to-first-packet (by basically stuffing the Alt-Svc HTTP header / ALPN TLS extension into the #DNS); - let you do redirection on the zone apex without using CN
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/rfc9460