context safety score
A score of 34/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
js obfuscation
JavaScript uses Function constructor for runtime code generation
malicious redirect
The canonical URL and all internal navigation links point to 'o.3seq.cam' (a .cam TLD domain) while the scanned domain is '3seq.com'. The alternate media link also points to 'z.3seq.cam'. Users and agents visiting 3seq.com are silently redirected to a different TLD (.cam) for all content and login operations. The .cam TLD is distinct from .com and can be used for traffic hijacking and bait-and-switch schemes. (location: page.html:4-5, line 43, lines 92-125)
brand impersonation
The site at 3seq.com presents itself as 'قصة عشق' (the original site) using the phrase 'الاصلي' (meaning 'the original') in the meta description, yet serves all assets, content, and links from the domain 'o.3seq.cam' — a different TLD. This pattern is consistent with a site impersonating or squatting on a legitimate brand's identity across two distinct domains (.com vs .cam), potentially to capture traffic intended for the real site. (location: page.html:46, metadata.json:1)
credential harvesting
Login and registration links ('تسجيل الدخول' / 'عضوية جديدة') present in the navigation point exclusively to 'https://o.3seq.cam/login' and 'https://o.3seq.cam/register' — a .cam TLD domain distinct from the scanned 3seq.com. Users who believe they are logging into 3seq.com are actually submitting credentials to a different domain (o.3seq.cam), which may be operated by a different party. (location: page.html:107-108, line 125)
hidden content
Multiple HTML comments contain fully-formed commented-out img tags referencing 'grey.gif' placeholder images and a commented-out search form pointing to 'https://o.3seq.cam'. While this appears to be leftover template/debug code rather than malicious hidden content, the volume (18+ commented-out image tags) and presence of a functional form in comments is notable. (location: page-hidden.txt:2-31)
obfuscated code
A Cloudflare challenge script injected via a hidden 1x1 invisible iframe dynamically creates and appends a script element with an inline innerHTML payload containing encoded parameters ('MTc3MjYyOTM0NQ==' base64) and loading '/cdn-cgi/challenge-platform/scripts/jsd/main.js'. The iframe is set to position:absolute, visibility:hidden — a classic technique for hiding script injection from users and some automated scanners. (location: page.html:828, page-text.txt:730)
curl https://api.brin.sh/domain/3seq.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
3seq.com currently scores 34/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.