context safety score
A score of 32/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
malicious redirect
script/meta redirect patterns detected in page source
cloaking
Page loads content in transparent or zero-size iframe overlay
social engineering
Site presents itself as a legitimate, trusted sports gaming platform ('most reliable', 'most trusted platform') while operating as an unlicensed online gambling/betting exchange. Content is designed to build false trust and encourage users to deposit funds and provide payment details to an unverified operator. Domain is only 244 days old. (location: page.html:265-286, page-text.txt:30-51)
credential harvesting
The page embeds an iframe pointing to '/mobile?' which loads the actual login/interactive interface inside the outer shell. The outer page serves as a deceptive wrapper around the embedded application where user credentials (login) and payment information are collected. CSS rules exist specifically for credit card input iframes: '.name_on_card_div iframe, .card_exp_month_div iframe, .card_exp_year_div iframe, .security_code_div iframe, .card_number iframe' indicating card data capture forms are loaded inside iframes. (location: page.html:156-158, page.html:248)
malicious redirect
JavaScript on page load unconditionally redirects all mobile users (viewport < 1024px) to '/mobile' via 'window.top.location.href', bypassing any parent frame context. This top-level redirect overrides any containing frame, which is a technique used to escape security sandboxes and force navigation. (location: page.html:226-233)
brand impersonation
The site uses keywords 'funinexch', 'funinexch360', and 'funinexch login' in meta tags, suggesting it is impersonating or typosquatting a related brand 'funinexch' / 'funinexchange' to capture traffic intended for another platform. The domain funinexchange360.com with the '360' suffix is a common typosquatting or clone-site pattern. (location: page.html:9)
hidden content
The H1 element 'Funinexchange Sports on Mobile: Experience at the Next Level Anytime' is explicitly hidden via 'display: none' inline style. This is SEO cloaking — serving hidden keyword-rich content to search engine crawlers while hiding it from human visitors, a deceptive technique also used to hide instructions or content from automated scanners. (location: page.html:237)
phishing
The site promotes 'Funinexchange login bonus' and encourages users to log in and make deposits on a young domain (244 days old) operating as an unlicensed gambling site. The platform solicits financial transactions and account creation without verifiable licensing or regulatory information, consistent with a phishing/scam gambling site pattern. (location: page.html:273-281, page-text.txt:38-45)
hidden content
Social media links use '#blank' as href values (e.g., href='#blank') rather than actual social media URLs, meaning these buttons lead nowhere. This is deceptive UI — presenting a facade of legitimate social presence without actual accounts, a pattern common in scam/clone sites. (location: page.html:298-306)
curl https://api.brin.sh/domain/funinexchange360.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
funinexchange360.com currently scores 32/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.