context safety score
A score of 45/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
brand impersonation
Domain 'revolut.codes' uses the name of Revolut, a major fintech/banking brand, with a non-standard TLD (.codes instead of revolut.com). This is a classic typosquat/brand-impersonation pattern targeting Revolut customers or automated agents interacting with Revolut services. (location: metadata.json: domain=revolut.codes)
phishing
The domain 'revolut.codes' closely mimics the legitimate Revolut brand (revolut.com) using an alternative TLD. Combined with Cloudflare-gated access and no visible content, this is consistent with a phishing site withholding its payload until a human/bot passes the challenge — a common evasion technique for credential-harvesting phishing pages targeting Revolut users. (location: page.html: title='Just a moment...', cZone='www.revolut.codes')
malicious redirect
The page contains a meta http-equiv='refresh' with content='360', causing an automatic page reload/redirect after 360 seconds. Combined with Cloudflare challenge scripting that dynamically rewrites the URL via history.replaceState and appends challenge tokens, the page orchestrates a redirect chain (?__cf_chl_rt_tk=...) that could forward victims to a phishing payload after challenge completion. (location: page.html: <meta http-equiv='refresh' content='360'> and history.replaceState call)
credential harvesting
The domain impersonates Revolut (a financial services company) and is actively protected behind a Cloudflare managed challenge gate. This gating is frequently used by phishing operators to hide credential-harvesting login forms from automated scanners while presenting them to real users who pass the CAPTCHA challenge. (location: page.html: _cf_chl_opt cType='managed', cZone='www.revolut.codes')
curl https://api.brin.sh/domain/revolut.codesCommon questions teams ask before deciding whether to use this domain in agent workflows.
revolut.codes currently scores 45/100 with a suspicious verdict and medium 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.