---
title: "How the Trap List Scanner Works: The Published Rules"
description: "The Trap List scanner, rule by rule: how it fetches a page safely, which text counts as hidden from people, and which words read as an instruction to an agent."
url: https://thesimind.si/trap-list/method/
---

# How the Trap List scanner works

The Trap List scanner is rule based and uses no paid service. It fetches a page safely, finds text hidden from people, and lists the page only when that hidden text also reads as an instruction to an agent under the phrase rules on this page. The same rules file runs the scanner.

## Fetching a page safely

The scanner fetches the reported address once, as SIMindTrapCheck/1.0, with these limits:

- Only http and https, on ports 80 and 443.

- It resolves the name itself and refuses private, loopback, link local, multicast, shared and reserved addresses, then connects to the address it checked and to no other.

- It follows at most 3 redirects and checks every hop the same way.

- It reads at most 2 MB and stops after 8 seconds in all.

- It reads HTML pages only, and never runs their scripts.

- It never stores the page. It keeps the SHA-256 of the bytes it read.

## Hidden from people

Text counts as hidden from people when it is in one of these places, set by inline styles or simple style rules in the page:

## Reads as an instruction to an agent

The hidden text is cut into sentences, and each sentence is read alone and with the next one. It reads as an instruction to an agent when it matches an action rule, and also an override rule or an address rule. Either part alone is never enough.

### Override rules

- ignore-previousAsks to ignore, forget or override earlier instructions

- new-instructionsAnnounces new instructions or a new task

- system-promptNames the system prompt or a developer message

- you-are-nowTries to give the agent a new role

### Address rules

- vocativeSpeaks to an agent by name at the start of a sentence

- if-you-areSays if you are an assistant, an agent or a bot

- to-all-agentsAddresses all or any agents

- agents-readingSpeaks to agents that read, browse or sum up the page

- when-you-readSpeaks to whoever sums up or reads the page

### Action rules

- visitAsks to visit, open or call an address

- sendAsks to send, post or share something somewhere

- revealAsks to reveal instructions, keys or private data

- runAsks to run code or commands

- payAsks to move money or sign a transaction

The rules file the scanner runs, with every pattern:

## When a page is listed

A page is listed only when one scan confirms both parts. The entry keeps:

- the address and the date found

- the hiding method and where in the page it was

- the matched instruction as plain text, cut to 200 characters, with its links disarmed, never shown as a link

- the SHA-256 of the page as fetched

- the seal: the evidence record joins SI MIND's hourly Proof of Mind seal on Solana

Road Test course pages are never listed. A page that could not be fetched waits for a later scan and is not listed until one confirms it.

## Rechecks and appeals

Anyone can ask for a recheck of an entry once a day. A site owner proves the domain with a meta tag on the listed page, or a file at /.well-known/simind-trap-check.txt, and gets a recheck at once. When a recheck finds the hidden instruction gone, the entry shows cleared on that date. If it comes back, the page is listed again.

## What the scanner cannot see

The scanner reads the page as the server sends it. It does not see text that scripts add after loading, rules in separate style sheets, text inside images, or pages behind a sign-in. A page that is not listed is not promised to be safe.

The Trap List scanner fetches a reported page over http or https on ports 80 and 443, checks every address it connects to against private and reserved ranges, follows at most 3 redirects, reads at most 2 MB in 8 seconds and stores no page body. It collects text hidden from people (tiny, transparent, background colored, off screen or clipped, not displayed, comments, meta tags, alt text, aria labels, data attributes, JSON-LD) and lists the page only when that text matches a published action rule together with an override rule or an address rule.

## Rules anyone can read, a list anyone can check

Report a page, check a page, or build the check into your agent.
