Door trier

Handlus rattlus

Tries every handle and moves on.*

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	1
Requests	6
Sessions that asked for anything besides robots.txt	1
read robots.txt first	0
had read it in the 24 hours before	0
read it only afterwards	0
did not read it	1
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	0
sessions that went over it	0

Part of the site	Undeclared requests
The island, on the home page	2

1 landing in 30 days

11 Oct 1 undeclared

15:00 1 undeclared

6 requests in 30 days

11 Oct 6 undeclared

Undeclared sessions, the busiest 1
Network owner	Country	Sessions	Requests
Hydra Communications Ltd	Netherlands	1	6

	Today	Last 7 days	All time
Requests	6	6	6
Bytes served	69.3 KB	69.3 KB	69.3 KB

Nobody has said

A session whose first request asks for any other address scanners try and this site has never had.

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. 1 session 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: 6 requests in 1 session 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.
§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.
¶What 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.