#dane
Live, measured metrics for the hashtag #dane from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #dane
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 06:01 UTC2 uses by 2 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 06:01 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 06:01 UTCEverything below is measured over the latest 40 public posts (spanning ~2503 hours).
Posting hours (UTC) — busiest: 15:00
Languages: English (22) · Slovak (10) · Polish (5) · German (2) · Dutch (1)
Avg boosts / post: 1.9
Top of the latest posts
The 47-day certificate: faster treadmill, same broken foundation Managing TLS certificates has become pretty crazy: Over the years validity was cut down from several years to two years to one year to half a year now. In a few years it will
📧 Veilig mailen met de overheid? Dat kan alleen met de juiste standaarden. DANE en DMARC zijn essentieel: DANE zorgt voor een versleutelde verbinding, DMARC voorkomt phishing. Ondanks de verplichting is de adoptie van DANE nog niet optimaa
Question to the #mail-admins here who have multiple servers and use #DANE. Let‘s say I have multiple servers and each server creates a wildcard-certificate for the same domain via Let‘s Encrypt. How are those TLSA-records handled? Or do you
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/dane