Benchmark · May 2026
What blind retrieval misses before an agent fetches
These examples show what blind retrieval can miss before an agent fetches an external source — and what Entropy0 surfaces through source-level infrastructure signals. Each row shows the Trust, Threat, and Deviation scores computed at scan time, along with the action guidance returned for a balanced policy and fetch / read_only / medium interaction context.
These examples show how Entropy0 evaluates source-level infrastructure signals before external sources enter an AI workflow. Entropy0 does not inspect page content, does not detect prompt-injection payloads, does not guarantee that a source is safe, and should not be treated as a replacement for content scanning, prompt-injection defenses, sandboxing, or human review. Action guidance is shaped by infrastructure posture and interaction context — the same domain may return a different action depending on what the agent is about to do with it.
Scores reflect the infrastructure state observed at scan time (May 2026) under a balanced policy and a fetch / read_only / medium interaction context. Infrastructure changes after that date will produce different scores. This is a signal demonstration, not a statistically representative safety benchmark or third-party evaluation.
Every POST /v1/decide response returns one of five actions. The same domain may return a different action depending on interaction context and policy profile.
Typosquat domains
Domains that visually mimic legitimate brands — character swaps, missing letters, TLD substitutions. Without a source trust gate, an agent has no signal to distinguish them from the originals.
Newly-registered domains
Domains under 30 days old. Domain age is invisible to standard retrieval logic — a freshly registered domain and a ten-year-old established source are indistinguishable without infrastructure signal.
Expired and re-registered domains
Domains that once belonged to legitimate organisations, expired, and were re-registered by different parties. WHOIS age appears old; infrastructure posture has changed.
UGC platforms — infrastructure trust ≠ content trust
High-reputation platforms that host user-generated content. Entropy0 returns high infrastructure trust for the platform itself. Platform-level trust does not imply page-level or user-generated content safety — individual repos, files, packages, or deployed apps are not evaluated.
- · Prompt injection inside page content — Entropy0 does not scan page text. Use Lakera, LlamaFirewall, or a content-inspection layer for that.
- · Individual artifacts on trusted platforms — a specific GitHub repo, npm package, or S3 object. Entropy0 evaluates domain infrastructure, not hosted artifacts.
- · Model output safety — jailbreak detection, output toxicity, hallucination. Out of scope for a pre-ingestion source trust gate.
- · Content accuracy or factual quality — a domain with high infrastructure trust may still host inaccurate content. Trust posture and content quality are independent signals.
Entropy0 is a pre-ingestion trust gate, not a complete AI safety solution. It should be deployed alongside content-level guardrails, sandboxing, and human review — not instead of them.
Run any domain through the same engine used to produce the scores above. No account required — 5 scans per hour per IP.