context safety score
A score of 38/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, targeting AI/bot agents by name. This is a deliberate signal or injection hook aimed at automated scanning agents like Brin, potentially to manipulate agent behavior or mark pages for agent-specific exploitation. (location: page.html:14)
social engineering
The page presents a fake Cloudflare-style CAPTCHA challenge ('One more step / Please complete the security check to access') using a custom reCAPTCHA sitekey. The host displayed in the challenge is dynamically injected via JavaScript from window.location.host, meaning this page can impersonate any domain's security check to trick users into completing the CAPTCHA. (location: page.html:25-31, page.html:106-108)
brand impersonation
The page mimics Cloudflare's well-known CAPTCHA interstitial page ('One more step', 'Please complete the security check', CAPTCHA widget, two-column FAQ layout) in exact visual and structural detail. The commented-out LinkedIn sitekey ('6Lc7CQMTAAAAAIL84V_tPRYEWZtljsJQJZ5jSijw') and dynamic host injection suggest this template is reused to impersonate multiple brands including LinkedIn. (location: page.html:24-95, page.html:109)
malicious redirect
After CAPTCHA completion, the script posts the response along with the full original URL ('location=' parameter) to '/cdn-cgi/l/chk_captcha', then redirects the user via window.location.replace(h) or window.location.reload(). The original URL is captured on page load and forwarded, enabling the operator to harvest where users came from and redirect them arbitrarily. (location: page.html:102-120)
hidden content
A div with 'position:absolute', 'left:-250px', 'top:-250px' is rendered off-screen and invisible to users. A setInterval loop every 1000ms repositions any such element to 'left:10px', suggesting dynamic manipulation of hidden elements after page load. (location: page.html:79-80, page.html:130-134)
hidden content
A covert beacon fires every 3,000,000ms (50 minutes) to 'https://gyrovague.com/tag/<random_string>/' with referrerPolicy:'no-referrer' and mode:'no-cors'. This is a stealth tracking/beaconing call to a third-party domain (gyrovague.com) that leaks visitor presence without user awareness or consent, deliberately obscured by no-referrer and no-cors to evade detection. (location: page.html:136)
credential harvesting
The CAPTCHA response token and the full original page URL (including any embedded credentials or session tokens in the URL) are exfiltrated via XHR POST to '/cdn-cgi/l/chk_captcha'. This endpoint is controlled by the archive.ph operator, not Google or Cloudflare, enabling harvesting of CAPTCHA tokens and user navigation context. (location: page.html:111-114)
curl https://api.brin.sh/domain/archive.phCommon questions teams ask before deciding whether to use this domain in agent workflows.
archive.ph currently scores 38/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.