#httpsonly

Live, measured metrics for the hashtag #httpsonly from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.

hashtag.org network · sponsored

Own #httpsonly

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.

$51.02/ year · 9-character #name
Claim #httpsonly — $51.02/yr→Buy on hashtag.space (web3)
card via hashtag.org · tokens via hashtag.space
0
Uses / 7 days
Mastodon
0
Accounts / 7 days
Mastodon
7
Recent posts
Mastodon
~0/hr
Recent pace
Mastodon · last 7
0
Avg reactions / post
Mastodon · last 7

Day-by-day usage

measured · fosstodon.org (Mastodon public tags API) · fetched 2026-07-28 22:44 UTC
0
07-22
0
07-23
0
07-24
0
07-25
0
07-26
0
07-27
0
07-28

0 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 22:44 UTC
#httpsonlymode
0 uses · 0 accounts / 7d

Live pulse

measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 22:44 UTC

Everything below is measured over the latest 7 public posts (spanning ~49009 hours).

Posting hours (UTC)

00:0012:0023:00

Languages: English (5) · Dutch (1) · German (1)

Avg boosts / post: 0.4

Top of the latest posts

  • Gisteren en zojuist (13:47) ontving ik phishingmails zogenaamd van KPN. Ditmaal heb ik screenshots op mijn Windows PC gemaakt, resp. van Thunderbird en Firefox. De mail zat in mijn inbox (niet als spam herkend): zowel SPF, DKIM als DMARC wa

    Erik van Straten@[email protected]♥ 0↻ 22026-06-24 13:43 UTCView post →

  • @BleepingComputer : when using untrustworthy networks, use a browser that supports "warn for insecure connections" - and enable it (my advice: do both anyway). Note that it is near-impossible to redirect an https connection without a certif

    Erik van Straten@[email protected]♥ 0↻ 12025-11-28 19:52 UTCView post →

  • The MIT website is still responding to non-TLS http requests at http://mit(dot)edu with a redirect to another non-TLS http URL. How profoundly stupid is that!? I expect better from MIT. For websites that are used by end-user browsers, the *

    Daniel Norton@[email protected]♥ 0↻ 02024-02-07 03:48 UTCView post →

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/httpsonly