#nsec3
Live, measured metrics for the hashtag #nsec3 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #nsec3
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:51 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 12:51 UTCNo related tags with measured usage found for #nsec3.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 12:51 UTCEverything below is measured over the latest 11 public posts (spanning ~28509 hours).
Posting hours (UTC)
Languages: English (10) · Russian (1)
Avg boosts / post: 2.5
Top of the latest posts
(living doc, updated regularly - if you prefer a low-edit post to boost, use https://infosec.exchange/@tychotithonus/111926621712441626) Looks like DNS-OARC coordinated fixes in advance, but no centralized analysis at first other than the a
DNSSEC validation на Go: написал свой validator и не до конца сошёл с ума Я пилю VantageDNS, privacy-focused recursive DNS-резолвер с фильтрацией. Edge-фронт на Go, 10 нод по миру, миекговский miekg/dns под капотом. На каком-то этапе у меня
@rmbolger @bortzmeyer maybe, but setting things up is horribly complicated. It takes way too many steps to set up a decent domain name zone. (Only email is worse and that includes DNS tricks, too). Today as I bought a fresh name, I was scra
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/nsec3