context safety score
A score of 46/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
obfuscated code
Large heavily obfuscated JavaScript block present in a <script data-cfasync="false"> tag. Uses a rotating array self-invoking obfuscator pattern (while(!![]){...O["push"](O["shift"]())}) with hex-encoded property lookups and string-splitting to conceal its true behavior. True payload (likely ad injection, tracking, or redirect logic) cannot be determined without deobfuscation. (location: page.html:198)
hidden content
jQuery script tag uses a non-standard MIME type attribute (type="7593fe690cb64e59b791b8b0-text/javascript") which prevents the browser from executing it natively but allows Cloudflare Rocket Loader or similar loaders to selectively execute it. The LiveInternet counter script uses the same custom type, indicating deliberate deferred/hidden script execution pattern. (location: page.html:8, page.html:191)
hidden content
LiveInternet counter pixel uses a 1x1 base64-encoded transparent GIF (data:image/gif;base64,...) with its src dynamically replaced by script, leaking the page URL, referrer, title, and screen resolution to counter.yadro.ru (a Russian analytics/tracking service). This constitutes covert user tracking without disclosure. (location: page.html:187-196)
social engineering
Search history section ('Son Axtarış') surfaces queries referencing minors (e.g., 'Azeri uşaq aqlaması' meaning 'Azerbaijani child crying', 'mekdeblilrr' meaning 'schoolchildren', 'Qizi ilk defe sikir' meaning 'fucking a girl for the first time') which may be used to normalize or funnel users toward CSAM-adjacent content, and could serve as SEO bait to attract vulnerable users. (location: page.html:173-174, page-text.txt:141)
curl https://api.brin.sh/domain/seks.wsCommon questions teams ask before deciding whether to use this domain in agent workflows.
seks.ws currently scores 46/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.