#serversecurity

Live, measured metrics for the hashtag #serversecurity 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 #serversecurity

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.

$5.00/ year · 14-character #name
Claim #serversecurity$5.00/yr
Annual, renews each year
Buy on hashtag.space (web3)
one-timepay once, yours for life
card via hashtag.org · tokens via hashtag.space
1
Uses / 7 days
Mastodon
1
Accounts / 7 days
Mastodon
40
Recent posts
Mastodon
~0/hr
Recent pace
Mastodon · last 40
0.2
Avg reactions / post
Mastodon · last 40

Day-by-day usage

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

1 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-27 10:17 UTC

Live pulse

measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 10:17 UTC

Everything below is measured over the latest 40 public posts (spanning ~56253 hours).

Posting hours (UTC) — busiest: 12:00

00:0012:0023:00

Languages: English (35) · Greek (1) · German (1) · Portuguese (1) · French (1)

Avg boosts / post: 1.2

Top of the latest posts

  • 11 bytes. That's all it takes. A newly disclosed OpenSSL "HollowByte" flaw lets attackers trigger a Memory Exhaustion DoS during the TLS handshake, forcing vulnerable servers to allocate up to 131 KB of heap memory from just an 11-byte mali

    thecybersecguru@[email protected]312026-07-19 06:51 UTCView post →
  • Two weeks ago we published our analysis of TURN security threats. Today: how to fix them. New guides covering implementation-agnostic best practices (IP range blocking, protocol hardening, rate limiting, deployment patterns) and coturn-spec

    Enable Security@[email protected]202026-02-25 10:03 UTCView post →
  • 20,000 failed SSH logins in 2 days. On a server hosting only a static webpage. Recently, I was checking logs on a VM that I own. It has no backend, no database. Just a static webpage served by NGINX. Yet, I found 20k failed SSH login attemp

    Sidharth@sidh212025-10-28 13:21 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/serversecurity