#dehashed
Live, measured metrics for the hashtag #dehashed from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #dehashed
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 09:48 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 09:48 UTCNo related tags with measured usage found for #dehashed.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 09:48 UTCEverything below is measured over the latest 2 public posts (spanning ~864 hours).
Posting hours (UTC)
Languages: English (2)
Avg boosts / post: 30
Top of the latest posts
30 cybersecurity search engines for researchers: 1. Dehashed — View leaked credentials. 2. SecurityTrails — Extensive DNS data. 3. DorkSearch — Really fast Google dorking. 4. ExploitDB — Archive of various exploits. 5. ZoomEye — Gather info
One of my favourite tools for an engagement is #dehashed. They essentially offer a service to search leaks and get creds. Here's a quick one liner to take the JSON output from their tool and generate a creds list for whatever purposes you m
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/dehashed