context safety score
A score of 43/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
cloaking
Page checks user-agent for bot/crawler strings to serve different content
js obfuscation
JavaScript uses Function constructor for runtime code generation
obfuscated code
String concatenation used to assemble an ID value ('da'+'5e'+'cf'+'97'+'8d'+'2c'+'19'+'b6'+'7d'+'52'+'04'+'d4'+'1b'+'66'+'ca'+'27') before passing it to an XHR request to /stats/u.php. This technique is commonly used to evade static string scanning of tracking or exfiltration endpoints. (location: page.html:409, page-text.txt:358)
obfuscated code
Cookie value '508d153ee29e0e66702395a612d2fb03c0fb2a48' is a Base64-encoded string ('WkJrQVUyN2VzWDM4aWZLWGlibkJFWWNReHp1VFVlUFVDVE1UYzNNalkxT0RRd01TMHdMVEE9a') set via inline script wrapped in HTML comment delimiters to partially obscure it from parsers. The cookie name itself is a SHA1-style hash, obscuring its purpose. (location: page.html:130)
obfuscated code
Two tracking cookies ('1r99a12' and '1r99a12_q') are set via script wrapped in HTML comment delimiters. The cookie value 'bm9yZWZ8fHwxfDB8MHxub25lfDA6' is Base64-encoded, encoding referrer and session data in a non-transparent way. (location: page.html:400-401)
malicious redirect
Navigation link 'FUCK NOW' routes through an internal redirect proxy (/sp/sp.php) to an external affiliate URL at a.montsapa.top, a domain associated with adult affiliate networks that may chain through additional redirects before reaching the destination. The URL contains tracking parameters and the destination domain is not disclosed to the user. (location: page.html:104)
social engineering
The 'FUCK NOW' call-to-action in the main navigation uses urgent, explicit language designed to drive impulsive clicks through an opaque redirect chain to an affiliate destination, obscuring the true landing site from the user. (location: page.html:104)
hidden content
The Delegate-CH meta tag delegates multiple high-entropy Client Hints headers (UA architecture, model, platform, bitness, full version list) to the third-party ad domain s.magsrv.com, enabling fingerprinting of visitors' devices without explicit user disclosure. (location: page.html:17)
hidden content
JavaScript dynamically rewrites gallery thumbnail href values on click via the inline script near line 256-259, replacing visible destination URLs with opaque paths ('/fxc/?'+id). This conceals the actual navigation target from users and link-preview tools until the click occurs. (location: page.html:256-259)
curl https://api.brin.sh/domain/freexcafe.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
freexcafe.com currently scores 43/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.