#modsec
Live, measured metrics for the hashtag #modsec from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #modsec
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 · mastodon.online (Mastodon public tags API) · fetched 2026-11-07 21:45 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.online (Mastodon public search API) · fetched 2026-11-07 21:45 UTCLive pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-11-07 21:45 UTCEverything below is measured over the latest 2 public posts (spanning ~11521 hours).
Posting hours (UTC)
Languages: English (2)
Avg boosts / post: 0
Used together with
Top of the latest posts
Does anyone have knowledge of a custom CRS ModSec ruleset for Mediawiki? Or perhaps have put together their own small plugin? We just discovered a few valid rules were blocking legit wiki edits on one of our coded oriented wikis. #modsec #o
Ran into a random #WordPress issue today. Ok, isn't really WordPress's fault, but a #modsec false positive. In trying to protect from #SQL injections, our firewall sees WordPress posts as dangerous. So every once in a while, a professor ass
#modsec across platforms
every network with a public tag surfaceFollow #modsec straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.
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/modsec