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
malicious redirect
The scanned URL is https://turkish123.to but the canonical URL, all asset links, and navigation links point to https://ahs.turkish123.com — the .to domain silently redirects visitors to a different subdomain host. This domain-hop is not disclosed to the user and could be used to serve different content or track users across domains. (location: page.html:20 — <link rel="canonical" href="https://ahs.turkish123.com/"> and page.html:228 — href="https://ahs.turkish123.com")
hidden content
A 1x1 invisible iframe is injected into the document body via Cloudflare's challenge-platform script. The iframe has position:absolute, top:0, left:0, height:1, width:1, border:none, visibility:hidden. A script is then dynamically written into the iframe's document that loads an external challenge script from /cdn-cgi/challenge-platform/scripts/jsd/main.js. While this is nominally Cloudflare Bot Management, the pattern of injecting hidden iframes with dynamic script execution is a recognized vector for covert data collection or fingerprinting. (location: page.html:659)
hidden content
CSS rule explicitly hides the aniview video player credit/logo elements using display:none !important, suppressing attribution for embedded third-party video content: #aniview-credit, .avp-logo-0-t, .avp-logo-0-i { display: none !important; }. This is consistent with unauthorized streaming sites hiding the identity of embedded video players to avoid takedowns. (location: page.html:305-308)
social engineering
The page contains fabricated trust signals: it claims 'Since 2020, Turkish123 has been a safe and reliable place' and 'No unsafe site can survive that long', using circular logic to self-certify safety. It also promotes proxy mirror sites (Turkish123.com, Turkish123.org, turkish123.website) to redirect users when the primary domain is blocked — a common technique used by piracy and potentially malicious sites to maintain user traffic after enforcement actions. (location: page.html:350, page.html:360)
malicious redirect
The page actively promotes multiple proxy/mirror domains (turkish123.com, turkish123.org, turkish123.website) as alternate access points. This is a deliberate multi-domain redirect strategy used to maintain access after blocklisting and to funnel users across unvetted domains that may serve different payloads. (location: page.html:360 — Turkish123 Proxy Websites feature list item)
hidden content
Main page content (the entire informational text block) is injected at runtime via JavaScript using $('.main-content').html(...) inside a jQuery document.ready handler rather than being present in static HTML. This technique hides content from static scanners and crawlers while serving it to browsers, a common SEO cloaking and content-hiding technique used by piracy and ad-fraud sites. (location: page.html:341-370)
hidden content
Third-party ad script loaded from vt.neterbarit.com — a domain not associated with major ad networks — using data-cfasync="false" to bypass Cloudflare's async script handling. This allows the script to execute synchronously and outside normal content security controls. The domain 'neterbarit.com' is not a recognized legitimate ad network and may serve malicious ads or tracking payloads. (location: page.html:331 — src="//vt.neterbarit.com/t4CxGWSZr8hEArwq/126019")
hidden content
Ad scripts from platform.pubadx.one are loaded twice with data-cfasync="false" and one instance also includes data-no-optimize="1", explicitly bypassing both Cloudflare processing and script optimization. pubadx.one is not a major recognized ad exchange and loading it in this fashion circumvents standard security layers. (location: page.html:375, page.html:385)
curl https://api.brin.sh/domain/turkish123.toCommon questions teams ask before deciding whether to use this domain in agent workflows.
turkish123.to 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.