context safety score
A score of 31/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
tls connection failed
Could not establish TLS connection
encoded payload
suspicious base64-like blobs detected in page content
phishing
1 deceptive links where visible host does not match destination host
malicious redirect
The site serves over HTTP (TLS connected=false, cert_valid=false) despite being a hosting/SSL provider that handles user authentication and payments. All traffic including login credentials and payment data is transmitted without encryption. (location: metadata.json: tls.connected=false, tls.cert_valid=false)
hidden content
An iframe loads content from '/secure.comodo.com.php' — a local PHP script with a path designed to visually impersonate the Comodo SSL trust seal domain (secure.comodo.com). This is a fake trust badge rendered via a server-side script rather than a genuine third-party seal, intended to falsely signal security to users. (location: page.html:663 — <iframe src="/secure.comodo.com.php" scrolling="no"></iframe>)
brand impersonation
The site uses a PHP script named 'secure.comodo.com.php' to simulate a Comodo SSL trust seal iframe. The filename is crafted to mimic the legitimate Comodo SSL verification endpoint (secure.comodo.com), falsely implying a verified Comodo SSL certificate is present when TLS is not even connected. (location: page.html:663 — <iframe src="/secure.comodo.com.php">)
social engineering
The site displays fabricated social proof statistics (253,053 domains, 55,526 members, 22,202 servers, 323 online visitors) with no verifiable source, and claims '100% DDoS Attack Protection Guarantee' and '1.5 Tbit/s capacity' while operating without a valid TLS connection, designed to build false trust. (location: page.html:452-458, meta description line 6)
credential harvesting
The site presents login ('Oturum Aç') and registration ('Üye Ol') flows, a mail order form, and payment notification forms over a connection with no valid TLS (connected=false, cert_valid=false), meaning credentials and financial data are transmitted in cleartext and susceptible to interception. (location: page.html:99 (login/register links), page.html:431-435 (payment/mail order forms), metadata.json TLS fields)
curl https://api.brin.sh/domain/yoncu.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
yoncu.com currently scores 31/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.