#JA3
Live, measured metrics for the hashtag #JA3 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #ja3
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 06:24 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 06:24 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 06:24 UTCEverything below is measured over the latest 39 public posts (spanning ~47684 hours).
Posting hours (UTC) — busiest: 06:00
Languages: Russian (24) · English (8) · Czech (3) · Polish (2) · Chinese (1) · French (1)
Avg boosts / post: 0.4
Top of the latest posts
be careful when validating your #JA3 implementation against ja3er.com : it returns the wrong value for the elliptic curve x448. the protocol id would be 30, but the site returns 1035 (which is the #openssl NID actually) .. so u don't spend
IP, браузер, TLS: три слоя, на которых палится парсер С чего все началось Хотел простую вещь: отслеживать цену на пару товаров, которые ждал со скидкой. Чтобы не заходить руками каждый день, а получить уведомление, когда подешевело. Думал,
Заморозка по fingerprint: как ТСПУ в июне 2026 ломает соединения по поведению, а не по протоколу Полгода назад я написал здесь разбор «почему VLESS работает» — он собрал 169 тысяч просмотров и под тысячу закладок. Я тогда уверенно заявил: R
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/ja3