#netsec
Live, measured metrics for the hashtag #netsec from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #netsec
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 08:02 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 08:02 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 08:02 UTCEverything below is measured over the latest 40 public posts (spanning ~4809 hours).
Posting hours (UTC) — busiest: 14:00
Languages: English (35) · German (4) · Polish (1)
Avg boosts / post: 1.3
Top of the latest posts
Residential proxies are a curse. Criminals use them as botnet for DDOS attacks. AI companies pay them to scrape the web for training data in a way that's nigh impossible to block or throttle. Ipidea operated one of the largest residential p
👉️ IPv4 address brokers are a critical chokepoint for bulletproof hosters 👉️ Carrier and broker responses to SBL listings reveal a lot about their intentions 👉️ Clustering internet badness at specific facilitators makes them attractive t
Tested fail2ban on NixOS with nftables. IPv4 bans land in nftables correctly, but IPv6 addresses accepted by fail2ban-client never reach the firewall unless a separate IPv6 nftables action is configured. Has anyone else seen this? #Fail2Ban
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/netsec