NEW TRIPWIRE BOARD
plant a URL where nothing should ever touch it — a passwords.xlsx on a share, a honeypot row in a database dump, a fake AWS key in a repo. Nobody has a reason to fetch it. If anything ever does, you learn the second it happened.
- each wire is a URL only you hold — plant it, then never touch it again
- a trip records what and when: method, target, user-agent, referer, timestamp
- the log is append-only in attested RAM — an intruder who owns the host still can't delete the record of their own trip. Stopping the deployment is visible; rewriting history isn't possible.
- the canary URL answers every fetch with the same dull 404, live or dead — probing it tells an intruder nothing
BOARD IS ARMED
this is the board — there is no public page. anyone holding this link sees your alarms and your canary URLs, so keep it as private as the wires themselves:
#……
PLANT A NEW TRIPWIRE
the canary URL — plant it and forget it:
THIS BOARD NEEDS ITS OWNER LINK.
a tripwire board has no public view — telling the world which of your wires are quiet tells an intruder where to step. the owner token rides the link's # fragment and never reaches the server except to prove ownership.
NOTHING HERE
this board never existed, or went 30 days with no trip, no edit and no owner visit, and was swept. the server can't tell you which — boards leave nothing behind.