context safety score
A score of 36/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 contains heavy hex-escape encoding typical of obfuscation
obfuscated code
The page contains a heavily obfuscated JavaScript payload using hex-encoded string arrays, variable name mangling (_0x1a2b, _0x4e3d, etc.), and a base64-encoded redirect URL ('aHR0cHM6Ly9rb2Zlc2xvcy5jb20vZ28vMjQ0ODk4NA==' decodes to 'https://kofeslos.com/go/2448984'). The obfuscation is designed to evade automated scanners and conceal the true destination. (location: page.html:12 — inline <script> block)
malicious redirect
The obfuscated script forcibly redirects visitors to 'https://kofeslos.com/go/2448984' — a third-party tracking/redirect URL on 'kofeslos.com', which is unrelated to the landing domain (123rutor.su). The redirect is attempted three ways in sequence: window.location.replace(), window.location.href assignment, and window.location.assign(), each with increasing delays (100ms, 500ms), maximizing redirect success. This is a classic traffic distribution system (TDS) relay used to funnel victims to phishing, malware, or scam pages. (location: page.html:12 — decoded base64 target: https://kofeslos.com/go/2448984)
hidden content
The page renders no visible content to the user (empty <div id='root'></div>, blank body). All functional behavior is entirely within the obfuscated script. The meta tag 'robots: noindex,noarchive,nofollow' actively prevents search engine indexing and caching, a technique used to hide the page from security researchers and crawlers while still serving it to real users. (location: page.html:7 — <meta name='robots' content='noindex,noarchive,nofollow'>; page.html:10 — empty #root div)
social engineering
The script includes an anti-analysis check: it compares window.outerWidth minus window.innerWidth and window.outerHeight minus window.innerHeight against a threshold of 160px (0xa0). If browser devtools are open (which widen the outer dimensions), the redirect is suppressed and the script exits early. This is a deliberate evasion of security analysts and automated headless browsers, ensuring the malicious redirect only fires for real end-users. (location: page.html:12 — conditional: if(window.outerWidth - window.innerWidth > 0xa0 || window.outerHeight - window.innerHeight > 0xa0) return;)
curl https://api.brin.sh/domain/123rutor.suCommon questions teams ask before deciding whether to use this domain in agent workflows.
123rutor.su currently scores 36/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.