CMS-Checker

2landings in 30 days
6requests in 30 days
0%read robots.txt first: 0 of 2 sessions
AlignmentInsufficient dataneeds 200 requests and 5 sessions in 30 days
0%of sessions verified as CMS-Checker’s own: 0 of 2

UNTESTED Insufficient data

Clipboardus tickedus

A clipboard that has ticked everything.

A joke about the drawing. It plays on the name and says nothing about how the bot behaves.

Verified sessions passed Passport Control. Unverified sessions said they were CMS-Checker and could not be checked, or have not been answered yet: they are shown for the species and are not put down to any operator. Sessions that failed are not on this page at all.

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	Verified	Unverified
Sessions	0	2
Requests	0	6
Sessions that asked for anything besides robots.txt	0	2
read robots.txt first	0	0
had read it in the 24 hours before	0	0
read it only afterwards	0	0
did not read it	0	2
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
The island, on the home page	0	6

Landings, last 30 days

VerifiedUnverified

The same figures as a table

Landings on each of the last 30 days, UTC
Day	Unverified	Total
10 Sep	0	0
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	2	2

Today is the red bar.

Favourite hours, UTC

VerifiedUnverified

The same figures as a table

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	1	1
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

Busiest hour: 11:00 UTC, with 1 landing (the red bar).

What it has cost this site

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

Where it comes from

Unverified sessions, the busiest 1
Network owner	Country	Sessions	Requests
Google LLC	United States	2	6

Who it is

What it is: Seen at Port 443 under the name “CMS-Checker”. Nobody has claimed it.
Order: Mensores, the surveyors
Kind: Autonomous bot
Run by: Nobody has said
Passport Control: No documented check. A session that says it is CMS-Checker 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	Trailing 30 days
Passed: verified	0
Could not be checked: unverified	2
Not yet answered: unverified	0
Failed, and filed under Googlebot (unverified)	0

Reference

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

CMS-Checker

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 CMS-Checker 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: CMS-Checker

An example group. The path is a placeholder.

User-agent: CMS-Checker
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 unverified sessions, so it is a statement about the species and not about any operator: 6 requests in 2 sessions 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.