#spamhaus
Live, measured metrics for the hashtag #spamhaus from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #spamhaus
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-29 19:39 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-29 19:39 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-29 19:39 UTCEverything below is measured over the latest 40 public posts (spanning ~10137 hours).
Posting hours (UTC) — busiest: 13:00
Languages: English (25) · German (5) · Spanish (2) · French (2) · Chinese (1) · Russian (1)
Avg boosts / post: 1
Top of the latest posts
tfw you can't get the verification code sent by your health insurance company to your email because the IP address it's coming from is listed in Spamhaus AND the email they're sending violates their enforcing DMARC policy. *sigh* #infosec #
The IPv4 address from my mail server keeps getting added to the Spamhaus block list. They won't tell me why, but at least they provide a timestamp of the report (seemingly to within a 5 minute window). The only things in my logs around that
Third time @spamhaus is blocking my foss projects mail server for vague unspecified reasons ("reputation", "neighborhood", "hosting providers", "dns servers") At this point @spamhaus you're the malicious party on the internet. If you have s
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/spamhaus