#dnsbl
Live, measured metrics for the hashtag #dnsbl from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #dnsbl
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.social (Mastodon public tags API) · fetched 2026-07-27 12:30 UTC2 uses by 1 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.social (Mastodon public search API) · fetched 2026-07-27 12:30 UTCLive pulse
measured · mastodon.social (Mastodon tag timeline) · fetched 2026-07-27 12:30 UTCEverything below is measured over the latest 40 public posts (spanning ~18403 hours).
Posting hours (UTC) — busiest: 13:00
Languages: English (30) · German (6) · Spanish (1) · Chinese (1)
Avg boosts / post: 0.9
Top of the latest posts
❌ The short answer is no — our datasets are free only for low-volume, non-commercial use. Not sure if that’s you? Check our Fair Use Policy: 👉 https://www.spamhaus.org/blocklists/dnsbl-fair-use-policy/ If you need data for commercial use,
📣 TODAY we will start to restrict access to KT (Korea Telecom) IP addresses querying our DNSBLs. To stay protected by the data, register for Spamhaus Technology's FREE Data Query Service. It takes minutes to change the config - register he
#lazymastodon #ipv6 #DNSBL question: I'm having spam trouble again. What's the theory (or just the practice) behind DNSBL for IPv6 addresses? The cheapest VPSes get 48 to 64 bit subnets; blocking individual addresses can't be the solution,
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/dnsbl