srchs-research-bot
- 1landing in 30 days
- 3requests in 30 days
- 0%read robots.txt first: 0 of 1 session
- AlignmentInsufficient dataneeds 200 requests and 5 sessions in 30 days
UNTESTED Insufficient data
Labcoatus forscienceus
A joke about the drawing. It plays on the name and says nothing about how the bot behaves.
How to read this page
This is the record of one kind of bot and what it did on the island.
The tags under its name are its stamp, for how it treated robots.txt, and its alignment. The clipboard icon beside the name holds its totals.
What it did here counts its visits and what it asked for. Who it is says who runs it.
Reference, at the bottom, shows the user agent it sends and how to address it in robots.txt.
What it did here
Its record with each rule
| Trailing 30 days | Undeclared |
|---|---|
| Sessions | 1 |
| Requests | 3 |
| 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 entered the Pitfall | 0 |
| having read robots.txt | 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 |
| Requests over the rate limit | 0 |
| sessions that went over it | 0 |
What it asks for
| Part of the site | Undeclared requests |
|---|---|
| The island, on the home page | 2 |
| The About page | 1 |
Landings, last 30 days
The same figures as a table
| Day | Undeclared |
|---|---|
| 10 Sep | 0 |
| 11 Sep | 0 |
| 12 Sep | 0 |
| 13 Sep | 0 |
| 14 Sep | 0 |
| 15 Sep | 0 |
| 16 Sep | 0 |
| 17 Sep | 0 |
| 18 Sep | 0 |
| 19 Sep | 0 |
| 20 Sep | 0 |
| 21 Sep | 0 |
| 22 Sep | 0 |
| 23 Sep | 0 |
| 24 Sep | 0 |
| 25 Sep | 0 |
| 26 Sep | 0 |
| 27 Sep | 0 |
| 28 Sep | 0 |
| 29 Sep | 0 |
| 30 Sep | 0 |
| 1 Oct | 0 |
| 2 Oct | 0 |
| 3 Oct | 0 |
| 4 Oct | 0 |
| 5 Oct | 0 |
| 6 Oct | 0 |
| 7 Oct | 0 |
| 8 Oct | 0 |
| 9 Oct | 1 |
Today is the red bar.
Favourite hours, UTC
The same figures as a table
| Hour | Undeclared |
|---|---|
| 00:00 | 0 |
| 01:00 | 0 |
| 02:00 | 0 |
| 03:00 | 0 |
| 04:00 | 0 |
| 05:00 | 0 |
| 06:00 | 0 |
| 07:00 | 0 |
| 08:00 | 0 |
| 09:00 | 0 |
| 10:00 | 0 |
| 11:00 | 0 |
| 12:00 | 0 |
| 13:00 | 0 |
| 14:00 | 1 |
| 15:00 | 0 |
| 16:00 | 0 |
| 17:00 | 0 |
| 18:00 | 0 |
| 19:00 | 0 |
| 20:00 | 0 |
| 21:00 | 0 |
| 22:00 | 0 |
| 23:00 | 0 |
Busiest hour: 14:00 UTC, with 1 landing (the red bar).
What it has cost this site
| Today | Last 7 days | All time | |
|---|---|---|---|
| Requests | 3 | 3 | 3 |
| Bytes served | 106.9 KB | 106.9 KB | 106.9 KB |
Where it comes from
| Network owner | Country | Sessions | Requests |
|---|---|---|---|
| Datacamp Limited | United States | 1 | 3 |
Who it is
- What it is
- Seen at Port 443 under the name “srchs-research-bot”. Nobody has claimed it.
- Order
- Vagantes, the strays
- Kind
- Script or library
- Run by
- Nobody has said
- 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.
Reference
User agent, and how a request is filed under this species
srchs-research-bot
The product name it is matched on, wherever it appears in a user agent.
A request is filed under this species when its user-agent string contains the product name
srchs-research-bot as a whole word, in any mix of capitals. Where a string holds more than one product name, the
longest wins, and a named bot wins over a library it is built on.
How to address this bot in robots.txt
The line that addresses it
User-agent: srchs-research-bot
An example group. The path is a placeholder.
User-agent: srchs-research-bot Disallow: /a-path/ Allow: /a-path/one-page
This is reference, not advice. Systema Machinae is not a bot-blocking product.
This site’s own robots.txt does not name it. The group for every bot applies.
Additional info
How it is counted
- A landing
- The first request of a session.
- Bytes
- The size of the response body, counted whatever the score.
Everything under What it did here is read 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.
What is not shown
Parts of the site come from a fixed list, and networks are shown by owner and country only: an address is never shown.
Who it is
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.
Alignment and the stamp
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: 3 requests in 1 session over the trailing 30 days.
The stamp in the header, UNTESTED: Has neither read robots.txt nor asked for a path it disallows. It is counted over the same sessions as the score. How the score is worked out, and the count behind every input, is on the Census page.