context safety score
A score of 45/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
tls connection failed
Could not establish TLS connection
phishing
Domain 'refkremeuk.xyz' uses a .xyz TLD with a pattern ('refkreme') that does not correspond to any known legitimate brand, combined with a failed TLS connection (connected=false, cert_valid=false). The site could not establish a valid HTTPS session, which is a strong indicator of a malicious or improperly configured phishing infrastructure. (location: metadata.json: tls.connected=false, tls.cert_valid=false; domain: refkremeuk.xyz)
brand impersonation
The domain 'refkremeuk.xyz' contains the substring 'uk' suggesting a geographic lure targeting UK users, combined with the .xyz TLD — a common pattern in brand-impersonation and typosquatting campaigns designed to deceive users expecting a legitimate '.co.uk' or '.uk' domain. (location: metadata.json: domain=refkremeuk.xyz)
malicious redirect
TLS connection failed entirely (connected=false), meaning the page content could not be fetched securely. Sites with broken or absent TLS that still serve content over HTTP are frequently used as redirect hops in malicious redirect chains, avoiding TLS inspection by security tools. (location: metadata.json: tls.connected=false, tls.san_match=false, tls.version=null)
hidden content
The .brin-context.md references a 'page-hidden.txt' file for extracted hidden content, but the file is empty and both page.html and page-text.txt are also empty. An empty or withheld page with a live domain registration is consistent with a cloaked or conditional-delivery phishing page that only renders content to targeted victims (e.g., based on user-agent, referrer, or geolocation), hiding itself from scanners. (location: page.html (empty), page-text.txt (empty), page-hidden.txt (empty); domain: refkremeuk.xyz)
curl https://api.brin.sh/domain/refkremeuk.xyzCommon questions teams ask before deciding whether to use this domain in agent workflows.
refkremeuk.xyz 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.