context safety score
A score of 71/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
credential harvesting
The login form collects Turkish National ID number (TC Kimlik No / tckn) and phone number (msisdn) via AJAX POST to /kullanici/oturum-ac, followed by an OTP form posting to /kullanici/login-otp. The site is hosted on a subdomain (bireyselsigorta.bereket.com.tr) of a legitimate Turkish insurance company, but the form collects highly sensitive government-issued identity numbers combined with phone numbers — a two-factor credential pair that could be abused if the site were compromised or impersonated. The pre-scan context flags 10 credential form inputs, confirming the extent of PII collection. (location: page.html:172-229, /kullanici/oturum-ac, /kullanici/login-otp)
social engineering
A prominent security warning popup (showBox function and #myModal) warns users that the company will NEVER ask for phone brand/model, full TC identity number, or mother's maiden name via email — this is a counter-phishing notice. While this is a defensive measure, its presence strongly indicates that active social engineering / phishing campaigns impersonating this brand are ongoing in the wild, making this site a confirmed target of impersonation attacks. (location: page.html:69, page.html:646)
malicious redirect
Three JS redirect patterns are flagged by the pre-scan heuristics. Inspection reveals window.location.href redirects to '/' and '/kullanici/Home' within AJAX success callbacks (postOTPForm and AydnCheck functions). These appear to be legitimate post-authentication navigation flows rather than malicious redirects. No off-domain redirect targets were found. Flagged as low severity for completeness since the destinations are relative paths on the same origin. (location: page.html:370, page.html:529, page.html:599)
brand impersonation
The page title, branding, logo assets, and user agreement text all reference 'Bereket Sigorta' and 'Bereket Emeklilik ve Hayat A.Ş.', a real Turkish insurance company. The site is served from the subdomain bireyselsigorta.bereket.com.tr with an OV TLS certificate issued by COMODO CA, and the domain is 12,973 days old — consistent with a legitimate property. However, the security warning modal explicitly acknowledges active impersonation attempts against this brand, indicating threat actors are creating spoofed versions of this login page to harvest TC identity numbers and OTPs. (location: page.html:8, page.html:119, page.html:129, page.html:164)
curl https://api.brin.sh/domain/bireyselsigorta.bereket.com.trCommon questions teams ask before deciding whether to use this domain in agent workflows.
bireyselsigorta.bereket.com.tr currently scores 71/100 with a caution 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.