#websec

Live, measured metrics for the hashtag #websec from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.

hashtag.org network · sponsored

Own #websec

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.

$520.70/ year · 6-character #name
Claim #websec — $520.70/yr→Buy on hashtag.space (web3)
card via hashtag.org · tokens via hashtag.space
0
Uses / 7 days
Mastodon
0
Accounts / 7 days
Mastodon
40
Recent posts
Mastodon
~0/hr
Recent pace
Mastodon · last 40
0.3
Avg reactions / post
Mastodon · last 40
—
Reddit posts / month
Reddit search
—
Open-web mentions
hashtag.org Firehose

Day-by-day usage

measured · fosstodon.org (Mastodon public tags API) · fetched 2026-11-09 10:18 UTC
0
11-03
0
11-04
0
11-05
0
11-06
0
11-07
0
11-08
0
11-09

0 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-11-09 10:18 UTC
#websecurity
8 uses · 7 accounts / 7d
#WebSecurityServiceProvider
0 uses · 0 accounts / 7d
#websecurityappliance
0 uses · 0 accounts / 7d
#websecurityprofessional
0 uses · 0 accounts / 7d
#websecuritytipfeb2023
0 uses · 0 accounts / 7d
#websecilla
0 uses · 0 accounts / 7d
#websecacademy
0 uses · 0 accounts / 7d
#websecuritytools
0 uses · 0 accounts / 7d
#websecuritymaster
0 uses · 0 accounts / 7d
#websecurityupdate
0 uses · 0 accounts / 7d
#WebSecurityAcademy
0 uses · 0 accounts / 7d
#websecrets
0 uses · 0 accounts / 7d

Live pulse

measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-11-09 10:18 UTC

Everything below is measured over the latest 40 public posts (spanning ~8339 hours).

Posting hours (UTC) — busiest: 09:00

00:0012:0023:00

Languages: Polish (32) · English (6) · Italian (1) · French (1)

Avg boosts / post: 0.6

Top of the latest posts

  • Dear #Firefox, please don't nag users that they should enable the integrated Password Manager when they in fact use one (KeePassXC in my case). I would even suggest the opposite: please warn people when they DO use the integrated password m

    Hex@hexmasteen@chaos.social♥ 9↻ 22026-09-28 09:40 UTCView post →

  • @calx THE ONLY FUNNY THING IS CONVERSATION... BUT HONESTLY THER'S NOTHING FUNNY WITH SITUATIONS LIKE THAT. #infosec #appsec #cybersecurity #selfhosted #php #websec #0day #vulnerability #cve

    FUNFACTOR1@FUNFACTOR1@infosec.exchange♥ 1↻ 12026-08-14 14:48 UTCView post →

  • If you're writing a tiny self-hosted web app for offensive security purposes or for application testing purposes, do you care if the web server/framework checks if there's a Host: header and that it matches the host/IP the HTTP server is li

    postmodern@postmodern@infosec.exchange♥ 1↻ 12026-01-13 01:29 UTCView post →

#websec across platforms

every network with a public tag surface

Follow #websec 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.

X (Twitter) ↗Instagram ↗TikTok ↗Facebook ↗LinkedIn ↗YouTube ↗Threads ↗Bluesky ↗Mastodon ↗Reddit ↗Pinterest ↗Tumblr ↗

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/websec