#validns
Live, measured metrics for the hashtag #validns from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #validns
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-28 01:14 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-28 01:14 UTCNo related tags with measured usage found for #validns.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 01:14 UTCEverything below is measured over the latest 5 public posts (spanning ~3988 hours).
Posting hours (UTC)
Languages: English (5)
Avg boosts / post: 4.2
Top of the latest posts
#validns v0.10.0 released! Added: - Validate zones signed with Ed25519 and Ed448 (RFC 8080) - Validate SVCB (TYPE 64) and HTTPS (TYPE 65) records per RFC 9460, including all nine IANA-registered SvcParam keys. - CAA tag-value validation and
#validns v0.11.0 released! New: - Major work on verbose output to render records and rdata (-1 meow) - Support for EUI48 and EUI64 records (RFC 7043) - Detect NSEC3 records with flags, iterations, or salt inconsistent with NSEC3PARAM - New
And we released #validns v0.10.0 two days ago with new features and fixes thanks to this fund 🥳 https://mastodns.net/@jelu/116595663313729106 @nlnetlabs @Nominet #RIPE92
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/validns