Skip to main content
DanManREAL/ AI_LAB
Updated Nov 20, 2026Request a test

Field testReliability & safetyBy Published Tested Updated

Cerberus Guard on sample data: one crawler name, two verdicts, and a block earned by behavior

The report

Field test

Verdict

Name checked, block earned by behavior

On sample records, Guard verified one ClaudeBot claim, marked a second one an impostor and blocked neither. Only when a fake also asked for secret files did it add a one-day block, and a claim it could not check stayed pending.

On the tier list: A walkthrough of my own security code on sample data, so it places no agent on the tier list.

A crawler name is a claim, not proof

Cerberus Guard is the security system I built with Claude's help for danmanreal.com. Crawlers such as ClaudeBot and Googlebot announce themselves with a name in every request, but that name is just text, so anyone can send it. Guard looks for evidence behind the name, then decides separately whether any behavior deserves a block.

For the video, the saved October 27 version of Guard ran five times on made-up log records, with every network connection switched off. Lookups and provider lists were supplied as sample answers, so nothing here is real traffic, a real visitor or a real crawler.

Same name, two verdicts

Two sample visitors both claimed to be ClaudeBot. One came from an address on the sample provider list, and Guard marked it verified. The other did not, and Guard marked it an impostor. Neither was blocked: in this version, automatic blocking for a failed name is off by default. Spotting a fake and punishing it are two different decisions.

Search crawlers get a different check. Guard looks up the name behind the visitor's address, checks that it belongs to the expected provider, then looks that name up again; the address has to come back the same. With supplied answers the real verifier returned three different results: ok for a matching address, failed for a wrong one, and pending when the lookup service was unavailable.

Missing evidence stays pending

With no provider list to check against, a ClaudeBot claim stayed pending, not failed. That held even with automatic impostor blocking switched on and the sample clock moved past Guard's 30-minute grace window. An identity that can't be checked yet has not been proven fake, and Guard does not treat it as one.

Behavior earns the block

Then a sample visitor with a failed ClaudeBot claim asked for two secret files, the kind that hold passwords and private keys. Guard added one automatic block for one day, with the reason recorded as secret-file hunting. In the saved code, repeat offenses grow from 1 day to 7 and then 30; that ladder was read from the source, not run here.

The rule was written to local files in the sample folder. It shows Guard's decision, not a visitor being turned away on the live site.

Not locking out the owner

The last run sent the same failed claim and secret-file requests from an address configured as the owner's. Guard still logged it and still marked the claim failed, but held back the automatic block. That comes from explicit configuration, not from guessing that a familiar visitor must be me.

Where Gemini 4 Carbon fits

The video opens with Google's Gemini 4 Carbon, a model Google describes as strong at finding, validating and patching software vulnerabilities. In Google's announcement as read on October 31, access starts with a subset of cyber defenders and expands to trusted partners, with no public date. I had no access, so nothing on this page tests Carbon, and Google's benchmark scores are Google's claims, not results from this lab.

It is also a different job. A model like Carbon works on code; Guard checks visitors to a website. Claude helped write Guard, but Guard runs plain code and rules on every request, with no language model in the loop, so each decision can be traced to the check that caused it.

Sources: the five recorded terminal runs and their privacy scans, the saved Guard source the runs used, and Google's announcement as read on October 31. Real crawler traffic on this site, including 269 fake AI crawler visits in one week, is in my Claude Duet report. The raw files stay private.

Limits of this report

  • Sample records and supplied lookup answers only: no real visitors, no live site and no live blocking were tested.
  • One run per case. The runs show how Guard decides, not how accurate it is across real traffic.
  • Verification checks where a visitor comes from, not which model is behind it or whether its behavior is harmless.
  • Gemini 4 Carbon was not tested; what the page says about it comes from Google's announcement.

Follow the lab

New test reports and tier-list changes get announced in my Discord's #news channel. The full videos are on YouTube.

Receipts

12 items

DanManREAL · AI lab

Test receipt

Field testOct 31, 2026

Cerberus Guard, the security system for danmanreal.com (saved version of October 27, 2026)

Same name, two visitors (ClaudeBot)
verified · impostorone address was on the sample provider list, the other was not
Automatic blocks for those two
0 · 0automatic impostor blocking is off by default in this version, so a failed name alone blocks nothing
Search-crawler check, three offline DNS answers
ok · failed · pendingmatching return address, wrong return address, resolver unavailable; the real verifier with supplied answers
No provider list to check against
pending · 0 blockseven with automatic impostor blocking switched on and the clock moved 31 minutes, past the 30-minute grace window
Failed claim plus two secret-file requests
1 block · 1 dayreason recorded as secret-file hunter; the rule went into local sample files only
Repeat offenses, from the saved code
1 · 7 · 30 daysread from the source, not run in this walkthrough; the optional impostor rule has its own, stricter schedule
Configured owner address, same probes
failed claim · 0 blocksthe owner is still logged; only the automatic block is held back
Runs recorded, network switched off
5 · all finished cleanlyOctober 31 at about 6 PM ET; the demo script blocks every network connection before Guard loads
Screen recordings scanned for private data
5 of 5 cleantext recognition on every second of each recording, then a visual check of each final frame
Provider-list code used in these runs
same file as the Oct 27 live fixbyte for byte the file my crawler report shows running on the server that day
Context: Gemini 4 Carbon access, Google's announcement read Oct 31
a subset of cyber defenders firstthen trusted partners through Google's Fairwind Program; no public date given. Not tested here
Delivered episode and Shorts
11:12 · 1:22 · 1:11main video, then "A Crawler Name Is Not Proof" and "What Can You Use?"

Verdict

Name checked, block earned by behavior

Tier list A walkthrough of my own security code on sample data, so it places no agent on the tier list.

danmanreal.com/tests/cerberus-guard-crawler-claims

What was tested

Cerberus Guard, the security system for danmanreal.com (saved version of October 27, 2026)

Shorts

Related

Independent testing. Sponsorships are always disclosed, and verdicts are never for sale.

Disagree? Bring your receipts

All reports

36 reports