context safety score
A score of 49/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
malicious redirect
The page is served under domain freefunz.com but the Cloudflare challenge zone is set to 'go.fojik.site' (cZone: 'go.fojik.site'), indicating the actual traffic/challenge is being processed under a different domain. This domain mismatch suggests freefunz.com is acting as a front that funnels users through a separate domain (fojik.site), a common technique in redirect chains used for traffic monetization, malvertising, or cloaking malicious destinations. (location: page.html and page-text.txt: window._cf_chl_opt cZone value)
social engineering
The page presents a Cloudflare-style 'Just a moment...' interstitial with a meta refresh of 360 seconds and a 'noindex,nofollow' robots directive. This pattern is used to prevent crawlers and scanners from indexing the true destination while presenting a benign-looking holding page to automated tools, effectively cloaking the real content from security scanners while human visitors are passed through. (location: page.html: <meta name='robots' content='noindex,nofollow'> and <meta http-equiv='refresh' content='360'>)
hidden content
The domain is only 73 days old and uses noindex/nofollow meta tags to suppress search engine indexing of its content. Combined with the cZone mismatch pointing to a separate domain (fojik.site), the site appears designed to avoid scrutiny while operating, a pattern consistent with short-lived phishing or scam infrastructure. (location: metadata.json: domain_age_days=73; page.html: robots meta tag)
curl https://api.brin.sh/domain/freefunz.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
freefunz.com currently scores 49/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.