#nxdomain
Live, measured metrics for the hashtag #nxdomain from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #nxdomain
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-29 16:54 UTC0 uses by 0 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-29 16:54 UTCLive pulse
measured · mastodon.social (Mastodon tag timeline) · fetched 2026-07-29 16:54 UTCEverything below is measured over the latest 11 public posts (spanning ~74301 hours).
Posting hours (UTC)
Languages: English (5) · German (3) · Russian (2)
Avg boosts / post: 1.7
Top of the latest posts
#DENIC heute: "Hej #ChatGPT, wie aktualisiert man den Schlüssel bei #DNSSEC?" Oder war es #Claude Code? 😏 #nxdomain #dns
Three major types of #DNS failures are timeouts, latency, and DNS NXDOMAIN errors. Observability tools often can overlook these areas - so do they matter? Well, it depends how many services you would like to break. Assuming your answer is ‘
Как аномальный NXDOMAIN-трафик привёл к росту счетов в Cloud DNS, а поддержка не помогла вовремя Использовали Cloud DNS, всё работало штатно. В марте 2026 года мы столкнулись с неприятной ситуацией: в облачном DNS, который использовался для
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/nxdomain