context safety score
A score of 48/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
TLS connection failed (connected=false, cert_valid=false, san_match=false) for a domain impersonating Refinitiv (a major financial data brand). The site at refinitiv.co.uk did not establish a valid TLS session, suggesting the domain may redirect or proxy traffic insecurely, or the infrastructure is not legitimately operated by the brand owner. (location: metadata.json: tls.connected=false, tls.cert_valid=false, tls.san_match=false)
brand impersonation
The domain refinitiv.co.uk uses the exact brand name of Refinitiv (now LSEG, a major global financial data and analytics company) under a .co.uk ccTLD. The legitimate brand operates under refinitiv.com. Registering a near-identical domain under a different TLD is a classic brand impersonation technique used for phishing or credential harvesting against financial sector users and enterprise clients. (location: metadata.json: domain=refinitiv.co.uk)
phishing
Combination of brand impersonation (refinitiv.co.uk mimicking refinitiv.com), failed TLS, and empty page content is consistent with a parked or pre-deployment phishing site. The domain is aged (14833 days) which may be used to lend credibility, but the lack of any legitimate resolvable content with a broken TLS posture indicates likely malicious intent targeting Refinitiv/LSEG customers or employees. (location: metadata.json, page.html (empty), page-text.txt (empty))
curl https://api.brin.sh/domain/refinitiv.co.ukCommon questions teams ask before deciding whether to use this domain in agent workflows.
refinitiv.co.uk currently scores 48/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.