#splithorizon
Live, measured metrics for the hashtag #splithorizon from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #splithorizon
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 · mas.to (Mastodon public tags API) · fetched 2026-10-03 02:55 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mas.to (Mastodon public search API) · fetched 2026-10-03 02:55 UTCLive pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-10-03 02:55 UTCEverything below is measured over the latest 2 public posts (spanning ~567 hours).
Posting hours (UTC)
Languages: English (2)
Avg boosts / post: 0.5
Top of the latest posts
I've been using #SplitHorizon #DNS with #tailscale for a while now, but I just figured out how to do it with #AdGuardHome as well. There's the clients:persistent configuration, with configuration based on source address you can send queries
@cks @lanodan @drscriptt There are actually quite a few, nowadays. See RFCs 6762, 7686, and 8375. example. is not the worst choice, although you could have gone with test. or internal. or intranet. . Given your objective, any of the further
#splithorizon across platforms
every network with a public tag surfaceFollow #splithorizon 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/splithorizon