#abuseipdb

Live, measured metrics for the hashtag #abuseipdb 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 #abuseipdb

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.

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

Day-by-day usage

measured · mastodon.online (Mastodon public tags API) · fetched 2026-09-29 01:41 UTC
0
09-23
0
09-24
0
09-25
0
09-26
0
09-27
0
09-28
0
09-29

0 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-09-29 01:41 UTC

No related tags with measured usage found for #abuseipdb.

Live pulse

measured · mastodon.online (Mastodon tag timeline) · fetched 2026-09-29 01:41 UTC

Everything below is measured over the latest 21 public posts (spanning ~37649 hours).

Posting hours (UTC) — busiest: 06:00

00:0012:0023:00

Languages: English (14) · German (3) · Russian (1) · French (1)

Avg boosts / post: 1.1

Top of the latest posts

  • A NL-based scanner is sweeping #Reticulum using many IPs across a range to touch public RNS transport node on #port4242 . It is drive-by port-scanning, not peering, with up to 5 ephemeral inbound flows, a few hundred bytes each, no sustaine

    adingbatponder :nixos: 👾@[email protected]♥ 0↻ 42026-09-11 10:40 UTCView post →
  • Using #suricata #IDS and #abuseipdb with manual checks using #claudecode to identify IP addresses that are attacking my reverse proxy device. I block in #nftables the IPs that tick all three boxes: 1. suricata reports attack, 2. claude code

    adingbatponder :nixos: 👾@[email protected]♥ 0↻ 12026-07-18 19:02 UTCView post →
  • #AbuseIPDB error 500

    小津 Ozu@[email protected]♥ 0↻ 12026-01-27 12:17 UTCView post →

#abuseipdb across platforms

every network with a public tag surface

Follow #abuseipdb 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/abuseipdb