context safety score
A score of 46/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
tls connection failed
Could not establish TLS connection
malicious redirect
script/meta redirect patterns detected in page source
malicious redirect
The page contains only a JavaScript redirect via window.location.href that immediately forwards all visitors to '/lander' on page load. The actual page content is completely hidden behind this redirect, preventing inspection of the destination. Combined with TLS not connected/invalid, this is a strong indicator of a traffic redirection scheme. (location: page.html:1 — window.onload=function(){window.location.href="/lander"})
hidden content
The visible page body is entirely empty (page-text.txt is blank) because all content is concealed behind a JavaScript redirect. No legitimate content is rendered to the user or to crawlers — the page exists solely to route traffic, obscuring the true destination from security scanners. (location: page.html:1 — <body> is absent; page-text.txt is empty)
hidden content
TLS connection failed (connected=false, cert_valid=false, san_match=false) for a site presenting itself as a financial service ('alphatreasury.co.uk'). Absence of valid TLS on a treasury/finance-themed domain suggests the site may be avoiding certificate transparency logs, which are used to detect phishing infrastructure. (location: metadata.json — tls.connected=false, tls.cert_valid=false, tls.san_match=false)
phishing
The domain 'alphatreasury.co.uk' uses financial/institutional terminology ('alpha', 'treasury') to impersonate or attract users expecting a legitimate financial or government treasury service. The combination of a deceptive domain name, invalid TLS, and a silent JavaScript redirect to an unverifiable '/lander' path is a pattern consistent with phishing infrastructure. (location: metadata.json — domain: alphatreasury.co.uk; page.html:1 — redirect to /lander)
curl https://api.brin.sh/domain/alphatreasury.co.ukCommon questions teams ask before deciding whether to use this domain in agent workflows.
alphatreasury.co.uk currently scores 46/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.