context safety score
A score of 38/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
phishing
1 deceptive links where visible host does not match destination host
malicious redirect
External third-party script loaded from suspicious domain 'gomatinequisheoi.com' (38522.gomatinequisheoi.com/4/js/269753) — a known popunder/ad network associated with aggressive redirects and malvertising. This script runs async and can redirect users or load malicious payloads without user interaction. (location: page.html:858)
malicious redirect
Script loaded from '/HillTOP Popunder anti.php' — the filename explicitly references 'Popunder', a technique that forces browser redirects to open new windows/tabs, often used for ad fraud, phishing landers, or malware distribution. (location: page.html:42)
brand impersonation
Site uses typosquat-style branding ('xlxx2', 'xlxx') that closely mimics the well-known adult platform 'xnxx'. Keywords meta tag explicitly includes 'xnxx' and 'porno' to capture organic search traffic intended for the legitimate site. Tags like 'xhmster' (line 231 in page.html) also mimic 'xhamster'. (location: page.html:7, page.html:137, page.html:231)
hidden content
Multiple overlapping ad-network site-verification meta tags from different providers (clickaine x2, 6a97888e x2, juicyads, Trafficstars, bm-site-verification, clckd) with duplicate keys indicate the site is registered with numerous ad networks simultaneously, including low-reputation networks known for malvertising. Duplicate meta name values are anomalous and suggest hidden monetization infrastructure. (location: page.html:12-19)
social engineering
External navigation link uses 'target=_blink' (typo of _blank) pointing to theporndude.com with rel='nofollow noreferrer', and a link to yalasex.com — outbound referral links designed to funnel traffic to partner sites, a common pattern in SEO-driven adult content rings that may expose users to further social engineering or malicious sites. (location: page.html:114, page.html:117)
curl https://api.brin.sh/domain/xlxx2.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
xlxx2.com currently scores 38/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.