#recursive_resolver
Live, measured metrics for the hashtag #recursive_resolver from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #recursive_resolver
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-27 07:06 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-27 07:06 UTCNo related tags with measured usage found for #recursive_resolver.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 07:06 UTCEverything below is measured over the latest 2 public posts (spanning ~193 hours).
Posting hours (UTC)
Languages: Russian (2)
Avg boosts / post: 0
Top of the latest posts
QNAME minimisation на практике: RFC 7816, реализация, грабли Когда вы открываете mail.google.com , ваш рекурсивный резолвер делает три-четыре шага: спрашивает root, потом TLD, потом authoritative для google.com , иногда ещё один уровень. Де
Я написал свой DNS-резолвер на Go вместо того, чтобы взять Unbound. Вот почему и что из этого вышло Три месяца назад я начал делать NextDNS-clone для Европы. Рекурсивный DNS с фильтрацией рекламы, трекеров и malware. Первый день: открываю U
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/recursive_resolver