#dnsrecords
Live, measured metrics for the hashtag #dnsrecords from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #dnsrecords
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-29 16:25 UTC1 uses by 1 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-29 16:25 UTCNo related tags with measured usage found for #dnsrecords.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-29 16:25 UTCEverything below is measured over the latest 16 public posts (spanning ~56041 hours).
Posting hours (UTC) — busiest: 20:00
Languages: English (15) · French (1)
Avg boosts / post: 0.6
Top of the latest posts
🚨 BREAKING NEWS: The internet is shocked! 🚨 68.4% of companies still can't handle basic email security a mere 11 YEARS after DMARC's debut! 🎉 Let's all pretend to be surprised while they fumble with their DNS records like it's rocket sci
🥳 Wow, a thrilling map of Swiss email providers! Because nothing screams excitement like 2,100 municipalities' DNS records. 🤯 Spoiler alert: it’s as riveting as watching grass grow, but with more acronyms. 📧🌱 https://mxmap.ch/ #SwissEma
𝗦𝗣𝗙 𝗵𝗮𝘀 𝗮 𝟭𝟬-𝗹𝗼𝗼𝗸𝘂𝗽 𝗹𝗶𝗺𝗶𝘁. 𝗠𝗼𝘀𝘁 𝗽𝗲𝗼𝗽𝗹𝗲 𝗳𝗶𝗻𝗱 𝗼𝘂𝘁 𝘁𝗵𝗲 𝗵𝗮𝗿𝗱 𝘄𝗮𝘆. above 10 DNS the entire SPF check returns permerror I see this constantly A company adds a new ESP their IT team appends another `i
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/dnsrecords