AgentTrustBot

Shadesus honestus

An agent in dark glasses who insists you can trust it.*

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

1landing in 30 days
6requests in 30 days
100%read robots.txt first: 1 of 1 session
0%of sessions verified as AgentTrustBot’s own: 0 of 1

What it did here‡

VerifiedPassed Passport Control.
UnverifiedSaid they were AgentTrustBot and could not be checked, or have not been answered yet. Shown for the species, and not put down to any operator.
Failed Passport ControlFiled under Impostor and not on this page at all.

Its record with each rule

Trailing 30 days	Verified	Unverified
Sessions	0	1
Requests	0	6
Sessions that asked for anything besides robots.txt	0	1
read robots.txt first	0	1
had read it in the 24 hours before	0	0
read it only afterwards	0	0
did not read it	0	0
Sessions that entered the Pitfall	0	0
having read robots.txt	0	0
Requests turned back at the vault, with a 403	0	0
Highest Climb level reached	Has not climbed	Has not climbed
Private Beach visits (not on the guest list, so allowed)	0	0
Turnstile waits kept	0	0
Turnstile waits broken	0	0
Requests over the rate limit	0	0
sessions that went over it	0	0

What it asks for§

Part of the site	Verified requests	Unverified requests
robots.txt, on the buoy	0	1
Addresses the site does not have	0	5

Landings, last 30 days

10 Oct 0 verified, 1 unverified

VerifiedUnverified

Landings on each of the last 30 days, UTC
Day	Unverified	Total
11 Sep	0	0
12 Sep	0	0
13 Sep	0	0
14 Sep	0	0
15 Sep	0	0
16 Sep	0	0
17 Sep	0	0
18 Sep	0	0
19 Sep	0	0
20 Sep	0	0
21 Sep	0	0
22 Sep	0	0
23 Sep	0	0
24 Sep	0	0
25 Sep	0	0
26 Sep	0	0
27 Sep	0	0
28 Sep	0	0
29 Sep	0	0
30 Sep	0	0
1 Oct	0	0
2 Oct	0	0
3 Oct	0	0
4 Oct	0	0
5 Oct	0	0
6 Oct	0	0
7 Oct	0	0
8 Oct	0	0
9 Oct	0	0
10 Oct	1	1

Favourite hours, UTC

15:00 0 verified, 1 unverified

VerifiedUnverified

Landings in each hour of the UTC day, over the last 30 days
Hour	Unverified	Total
00:00	0	0
01:00	0	0
02:00	0	0
03:00	0	0
04:00	0	0
05:00	0	0
06:00	0	0
07:00	0	0
08:00	0	0
09:00	0	0
10:00	0	0
11:00	0	0
12:00	0	0
13:00	0	0
14:00	0	0
15:00	1	1
16:00	0	0
17:00	0	0
18:00	0	0
19:00	0	0
20:00	0	0
21:00	0	0
22:00	0	0
23:00	0	0

Where it comes from§

Unverified sessions, the busiest 1
Network owner	Country	Sessions	Requests
OVH SAS	Germany	1	6

What it has cost this site‡

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

Who it is¶

Nobody has said

Discentes, the learnersAutonomous bot

Seen at Port 443 under this name. Nobody has published anything about who runs it, so there is nothing to check its identity against.

Passport Control

No documented check. A session that says it is AgentTrustBot can be neither confirmed nor refuted, so every one is shown as unverified and none is put down to any operator.

Sessions that said they were this bot

1 in the trailing 30 days

Passed: verified0
Could not be checked: unverified1
Not yet answered: counted for nobody0
Failed, and filed under Impostor0

Reference

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

User agent, and how a request is filed under this species

AgentTrustBot

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 AgentTrustBot 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: AgentTrustBot

An example group. The path is a placeholder.

User-agent: AgentTrustBot
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.

Notes

*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 unverified sessions, so it is a statement about the species and not about any operator: 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
‡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.
§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.
¶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.