#nam3l3ss
Live, measured metrics for the hashtag #nam3l3ss from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #nam3l3ss
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-30 15:39 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-30 15:39 UTCNo related tags with measured usage found for #nam3l3ss.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-30 15:39 UTCEverything below is measured over the latest 6 public posts (spanning ~1014 hours).
Posting hours (UTC)
Languages: English (4) · German (2)
Avg boosts / post: 1.5
Top of the latest posts
Diese Nachricht stammt von vor knapp 6 Wochen. Das Problem scheint aber immer noch akut zu sein, wenn ich hier nach #Nam3L3ss suche: https://infosec.exchange/@PogoWasRight/113702962047983818 Amazon, UBS und Firmenich von Breach betroffen -
As an update on database leaks by #"Nam3L3ss::" He posted another 133 databases today -- all are from the Clop exploitation of a MOVEit vulnerability in May 2023, and all of these particular databases were stolen from Delta Dental. In Decem
In November 2024, a BreachForums user called "Nam3L3ss" dumped more than 100 databases on BreachForums. The databases were cleaned-up databases from the Clop MOVEit breach of 2023. He plans to leak even more databases in the coming weeks an
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/nam3l3ss