context safety score
A score of 42/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
brand impersonation
The domain kamilkoc.com.tr is serving a full clone of the official FlixBus US homepage (www.flixbus.com), including all branding, logos, navigation, search booking widget, content, and structured data. The canonical tag points to www.flixbus.com and the page title reads 'FlixBus: Convenient and affordable bus travel in the US', but the serving domain is a Turkish third-party domain (kamilkoc.com.tr) with no affiliation to FlixBus. This is a complete brand impersonation of FlixBus. (location: kamilkoc.com.tr — entire page, page.html:25 (title), page.html:31 (canonical), page.html:312-334 (structured data))
phishing
The cloned FlixBus site on kamilkoc.com.tr includes a fully functional booking search mask (injectSearchMask calling shop.flixbus.com) and a 'Manage My Booking' login link pointing to https://shop.flixbus.com/rebooking/login. Users arriving at this impersonator domain expecting a legitimate travel site could submit booking requests or login credentials that may be intercepted or redirected through the fraudulent domain infrastructure. (location: page.html:713-717 (Manage My Booking nav link), page-text.txt:1976-1982 (injectSearchMask call))
malicious redirect
The page contains a geolocation overlay that dynamically redirects users to locale-specific FlixBus domains based on their detected location. This redirect logic is controlled by JavaScript on the impersonating domain (kamilkoc.com.tr), meaning an attacker controlling this domain could intercept or modify redirect targets before forwarding users — or silently log geolocation data while appearing to redirect legitimately. (location: page.html:475-499 (geolocation-overlay section), page-text.txt:1985-1991 (geolocationOverlay JS call))
hidden content
Multiple elements are rendered with 'display: none' including the emergency-box, emergency-overlay, and geolocation-overlay. These hidden containers are populated dynamically via JavaScript calls (emergencyMessage, geolocationOverlay). Their content is not visible in the static HTML but could be injected with arbitrary content at runtime on the attacker-controlled domain. (location: page.html:341 (emergency-box display:none), page.html:359 (emergency-overlay display:none), page.html:475 (geolocation-overlay display:none))
curl https://api.brin.sh/domain/kamilkoc.com.trCommon questions teams ask before deciding whether to use this domain in agent workflows.
kamilkoc.com.tr currently scores 42/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.