context safety score
A score of 35/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
encoded payload
suspicious base64-like blobs detected in page content
malicious redirect
script/meta redirect patterns detected in page source
prompt injection
HTML comment '<!-- brin-agent/1.0 -->' is embedded in the page source, suggesting the page is aware of and targeting AI agent crawlers/scanners by name. This is a marker consistent with agent-aware content manipulation. (location: page.html:14)
social engineering
Fake Cloudflare-style CAPTCHA challenge page ('One more step / Please complete the security check to access') that impersonates a legitimate bot-protection flow. The page mimics Cloudflare's DDoS protection UI but is served by archive.today, not Cloudflare. This pattern is widely used in phishing chains to intercept users and agents mid-flow. (location: page.html:25-29)
brand impersonation
The page visually and structurally impersonates Cloudflare's 'One more step' CAPTCHA interstitial page, including identical layout, messaging ('Please complete the security check to access'), and a reCAPTCHA widget. The JavaScript even contains a commented-out LinkedIn reCAPTCHA sitekey, suggesting prior use impersonating LinkedIn as well. (location: page.html:107-109)
malicious redirect
After CAPTCHA completion, the script posts to '/cdn-cgi/l/chk_captcha' (a Cloudflare-mimicking endpoint) and then executes window.location.replace(h) or window.location.reload(), redirecting the user/agent to an attacker-controlled destination encoded in the original URL hash/href. The original URL is captured in variable 'h' before any hash manipulation. (location: page.html:102-120)
hidden content
A div element is positioned off-screen at left:-250px, top:-250px using absolute positioning, making it invisible to users but readable by scrapers and AI agents. This is a classic hidden content technique. (location: page.html:79)
hidden content
A setInterval beacon silently and repeatedly fetches randomized URLs on the third-party domain 'gyrovague.com' with referrerPolicy:'no-referrer' and mode:'no-cors' every 50 minutes (3,000,000ms). This covert tracking beacon exfiltrates visit signals to an unknown third party while suppressing referrer information to evade detection. (location: page.html:136)
prompt injection
The page manipulates browser history via window.history.pushState('/','','/') to erase the original URL from the address bar immediately on load, obscuring the true destination from users and potentially confusing agent context about the current page location. (location: page.html:103-104)
brand impersonation
JavaScript comment '//'sitekey': '6Lc7CQMTAAAAAIL84V_tPRYEWZtljsJQJZ5jSijw', // linkedin's' reveals the page was previously (or can be) configured to use LinkedIn's reCAPTCHA sitekey, indicating this template is reused to impersonate multiple brands. (location: page.html:109)
curl https://api.brin.sh/domain/archive.todayCommon questions teams ask before deciding whether to use this domain in agent workflows.
archive.today currently scores 35/100 with a suspicious verdict and low confidence. The goal is to protect agents from high-risk context before they act on it. Treat this as a decision signal: higher scores suggest lower observed risk, while lower scores mean you should add review or block this domain.
Use the score as a policy threshold: 80–100 is safe, 50–79 is caution, 20–49 is suspicious, and 0–19 is dangerous. Teams often auto-allow safe, require human review for caution/suspicious, and block dangerous.
brin evaluates four dimensions: identity (source trust), behavior (runtime patterns), content (malicious instructions), and graph (relationship risk). Analysis runs in tiers: static signals, deterministic pattern checks, then AI semantic analysis when needed.
Identity checks source trust, behavior checks unusual runtime patterns, content checks for malicious instructions, and graph checks risky relationships to other entities. Looking at sub-scores helps you understand why an entity passed or failed.
brin performs risk assessments on external context before it reaches an AI agent. It scores that context for threats like prompt injection, hijacking, credential harvesting, and supply chain attacks, so teams can decide whether to block, review, or proceed safely.
No. A safe verdict means no significant risk signals were detected in this scan. It is not a formal guarantee; assessments are automated and point-in-time, so combine scores with your own controls and periodic re-checks.
Re-check before high-impact actions such as installs, upgrades, connecting MCP servers, executing remote code, or granting secrets. Use the API in CI or runtime gates so decisions are based on the latest scan.
Learn more in threat detection docs, how scoring works, and the API overview.
Assessments are automated and may contain errors. Findings are risk indicators, not confirmed threats. This is a point-in-time assessment; security posture can change.
integrate brin in minutes — one GET request is all it takes. query the api, browse the registry, or download the full dataset.