THUGS(red) DarkWeb/Monitor_

Statistics

What the monitor sees

Nine views of the same collection: where the services sit, whether they answer, what runs them, and what stops us getting through. Everything below is measured, not modelled — and where a measurement does not exist yet, the panel says so instead of drawing a plausible line.

Tracked 3,455 15 categories
Reachable 577 17% of the board
Blocked 29 answered 403
Broken 21 answered, but not with the site
Dark 2,828 82% of the board
Sweep lag 1h oldest measurement on the board
Checked 24h 3,455 100% of the board
Screenshots 713 captures on file
Reachability flow Open CSV

Every tracked service, flowing from its category through the reachability state we last measured to the HTTP class it answered with.

sites 3455 services across 14 categories: 577 reachable, 50 answering with something other than the site, 2828 dark.
Reachability now Open CSV

The current state of the board, broken down by category.

sites 577 of 3455 tracked services answered on the last sweep - 17% of the board.
Protection Open CSV

What sits in front of the services: which vendor, and whether it stops us.

sites headers, cookies and page titles 77 of 3455 services sit behind a detectable protection layer, and 43 of those are unreachable because of it.
Uptime calendar partial data Open CSV

A year of daily reachability, one cell per day.

site_checks_daily has no rows yet, so this is not uptime: each cell counts the services whose most recent successful reach falls on that day. A true day-by-day uptime calendar starts accumulating from the next crawl, once the collector writes its check history.

sites.last_alive Last successful reach for 638 services, spread over 37 days.
Collection growth Open CSV

Cumulative services under monitoring, stacked by category.

sites.audit_added The collection grew from its first entry in 2023-01 to 3455 services by 2026-08.
Churn Open CSV

Services added against services that went dark, week by week.

site_checks Over the last 52 weeks: recoveries 51, went dark 35, net +16.
Response timing Open CSV

How long the services take to answer, and how fresh each measurement is.

sites.response_ms Median response across 3400 measured services is 10587 ms.
Technology Open CSV

Server family to framework, sized by the number of services running it.

sites.tech_json 610 of 610 services report a server banner; nginx is the most common family.
Onion graph partial data Open CSV

How the services we watch relate to one another.

links_json is still empty, so no service has told us which other onions it references. The edges below are shared infrastructure instead: a hub is one exact Server banner, and the services hanging off it all answer with that identical version string, which usually means the same host or the same operator. The real reference graph replaces this once the collector harvests outbound links.

sites.header_server 215 services fall into 22 groups that answer with an identical server banner.