#recon
Live, measured metrics for the hashtag #recon from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #recon
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 12:38 UTC1 uses by 1 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 12:38 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 12:38 UTCEverything below is measured over the latest 40 public posts (spanning ~8916 hours).
Posting hours (UTC) — busiest: 15:00
Languages: English (36) · Russian (4)
Avg boosts / post: 0.9
Top of the latest posts
Plum, for Proactive Land Uncovering & Monitoring, is an orchestration tool to learn, monitor, and document an exposure surface. It coordinates work between scanning agents, keeps historical results, and makes observations searchable over ti
Hey infosec folks 👋 I built RYN27 — a free, open-source CLI recon tool written in Python. MIT licensed — fork it, contribute, do whatever you want with it. I’d love feedback from people who actually do this work. What it does: 🔍 WHOIS · F
I'm hooked. Definitely more versatile than my #flipperzero overall, though not out of the box. Looking forward to getting a wide variety of modules. https://www.digikey.ca/en/supplier-centers/m5stack https://www.mouser.ca/manufacturer/m5sta
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/recon