#portscan
Live, measured metrics for the hashtag #portscan from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #portscan
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-09-27 13:12 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-09-27 13:12 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-09-27 13:12 UTCEverything below is measured over the latest 20 public posts (spanning ~66757 hours).
Posting hours (UTC) — busiest: 13:00
Languages: English (19)
Avg boosts / post: 0.9
Top of the latest posts
Monitored SIEM: We're seeing some unusual port scanning activity Sys Admin: It's me, hi, I'm the problem, it's me #sysadmin #security #networksecurity #nmap #portscan #firewall
TIL The FreeBSD kernel auto-tarpits (for want of a better word) portscans on your host as soon as they attempt to connect to a closed port. If you see the following in your logs, that’s what’s happening. "kernel: Limiting closed port RST re
someone's bot net is giving it a go #sysadmin #crowdsec #botnet #portscan
What “portscan” means
WikipediaA port scanner is an application designed to probe a server or host for open ports. Such an application may be used by administrators to verify security policies of their networks and by attackers to identify network services running on a host and exploit vulnerabilities.
“Port scanner” on Wikipedia (CC BY-SA) →#portscan across platforms
every network with a public tag surfaceFollow #portscan 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/portscan