context safety score
A score of 27/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
hidden instruction
high hidden content ratio detected in DOM
malicious redirect
script/meta redirect patterns detected in page source
cloaking
Page loads content in transparent or zero-size iframe overlay
brand impersonation
The page title and meta description claim to be the 'Maxwinexch Official Platform' but the structured data (ld+json) references a different brand 'Winexch' with URL 'https://winexch24.com/' and associated social media accounts. The domain maxwinexch365.com impersonates or mimics the legitimate winexch24.com brand, using near-identical branding to mislead users. (location: page.html:10, page.html:42-45)
brand impersonation
A hidden H1 element contains the text 'Winexch' rendered with opacity:0, font-size:0.1px, display:none, and color:transparent — classic hidden SEO/brand injection to associate the page with the 'Winexch' brand while concealing it from users. This is used to siphon organic search traffic from the legitimate Winexch brand. (location: page.html:271)
hidden content
H1 tag with text 'Winexch' is deliberately hidden from users using multiple redundant CSS properties (opacity:0!important, font-size:0.1px!important, display:none!important, color:transparent!important). This hidden content is used to manipulate search engines and deceive users about the site's true identity. (location: page.html:271)
phishing
The site presents itself as an 'Official Platform' for login and signup (per title and meta description) for online gambling/betting in India. The domain is only 334 days old and impersonates or closely mimics the established 'Winexch' brand. Combined with credential collection (signup/login), this strongly indicates a phishing operation targeting users of the legitimate Winexch platform. (location: page.html:10-12, metadata.json:whois.domain_age_days=334)
credential harvesting
The page is an 'Official Platform' login/signup page (per title: 'Secure Signup and Login') that embeds login/registration UI via an iframe (/mobile). Credentials entered by users deceived by the brand impersonation would be harvested by the fraudulent site operator. (location: page.html:10, page.html:260)
malicious redirect
JavaScript at page load unconditionally redirects mobile visitors (viewport width < 1024px) to '/mobile' via window.top.location.href, bypassing any parent frame context. This top-level redirect could be used to send users to a different credential-harvesting page while evading iframe sandboxing. (location: page.html:109-114)
social engineering
The page uses authoritative language ('Official Platform', 'Secure Signup and Login') combined with brand impersonation of an established Indian online betting platform to build false trust and encourage users to submit credentials. Meta keywords target high-value Indian gambling search terms to maximize victim reach. (location: page.html:10-12)
hidden content
A ByteDance pixel/tracking script (static.bytedance.com) is dynamically injected without disclosure, collecting user behavioral data for an undisclosed third party. This is not a standard analytics tool and its presence on a financial/gambling credential page raises significant data exfiltration concerns. (location: page.html:234-241)
curl https://api.brin.sh/domain/maxwinexch365.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
maxwinexch365.com currently scores 27/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.