Bin rummager

Binnus rummagus

Going through the bins round the back.*

robots.txtUNTESTED: Has neither read robots.txt nor asked for a path it disallows.
AlignmentInsufficient data: Needs 200 requests and 5 sessions in 30 days.†

What it did here

Trailing 30 days	Undeclared
Sessions	2
Requests	266
Sessions that asked for anything besides robots.txt	2
read robots.txt first	0
had read it in the 24 hours before	0
read it only afterwards	0
did not read it	2
Sessions that asked for a disallowed path	0
Sessions that entered the Pitfall	0
having read robots.txt	0
Pages taken in the Pitfall and the Climb	0
Requests turned back at the vault, with a 403	0
Highest Climb level reached	Has not climbed
Private Beach visits (not on the guest list, so allowed)	0
Turnstile waits kept	0
Turnstile waits broken	0
Sessions served a page that carries the nofollow link	1
followed it	0
Requests over the rate limit	196
sessions that went over it	1

Part of the site	Undeclared requests
The island, on the home page	9
Addresses the site does not have	82

2 landings in 30 days

12 Oct, log missed 2 2 undeclared

00:00 1 undeclared

266 requests in 30 days

12 Oct, log missed 2 266 undeclared

Undeclared sessions, the busiest 2
Network owner	Country	Sessions	Requests
Feo Prest SRL	Germany	1	256
DigitalOcean, LLC	Germany	1	10

	Today	Last 7 days	All time
Requests	266	266	266
Bytes served	34.9 KB	34.9 KB	34.9 KB

Nobody has said

A session whose first request asks for a leftover file: a backup or an archive ending in .bak, .old, .zip or .tar.gz.

How its operator says to check it

Nothing to verify: it names no operator.

Passport Control

Not checked. Anyone can run it and it names no operator, so there is no claim to test. 2 sessions filed as undeclared in the last 30 days.

The user agent it sends, and how to address it in robots.txt.

It has no product name of its own, so nothing is matched on.

It has no product name, so no group in robots.txt can address it.

*The line under the name is a joke about the drawing. It plays on the name and says nothing about how the bot behaves.
†Insufficient data. A judgement needs at least 200 requests and 5 sessions in the trailing 30 days. This one would rest on all its sessions: 266 requests in 2 sessions over the trailing 30 days. The stamp is counted over the same sessions as the score. How it is scored
‡Parts of the site come from a fixed list, so a path is never shown. Networks are shown by owner and country only, so an address is never shown.
§The log missed about 96 requests on 5 of the last 30 days, the most on 9 October (40): the front door took them in and the server did not answer. A dashed line marks those days on the charts.
¶Counted from the request log for today and the 29 days before it, by UTC date. These are counts, not a verdict: a session is judged on what it did inside the 30 days. A landing is the first request of a session. Bytes are the size of the response body, counted whatever the score.
6What it is and who runs it, under Who it is, is a claim: the operator’s own account where it has published one, and a third party’s where it has not. This site has not tested it.