#XSLeak
Live, measured metrics for the hashtag #XSLeak from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #xsleak
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 06:59 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 06:59 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 06:59 UTCEverything below is measured over the latest 2 public posts (spanning ~27223 hours).
Posting hours (UTC)
Languages: English (2)
Avg boosts / post: 0
Top of the latest posts
#Development #Techniques Modern solutions against cross-site attacks · “If you want to improve security you have to move.” https://ilo.im/1613tf _____ #Security #Vulnerability #XsLeak #HttpHeaders #COOP #CORP #WebAPIs #XMLHttpRequest #Brows
#Slack contains an #XSLeak vulnerability that de-anonymizes users Source https://www.usenix.org/conference/usenixsecurity19/presentation/staicu Flawed Workaround https://bugs.chromium.org/p/chromium/issues/detail?id=1259077
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/xsleak