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
phishing
1 deceptive links where visible host does not match destination host
social engineering
Domain edizdalkilic.com (a Turkish personal name domain, 206 days old) is entirely operating as a Thai-language adult content aggregation site. The domain name is deceptive and dissociated from the actual site content, creating a false impression of legitimacy or personal identity to avoid scrutiny and blocklists. (location: metadata.json, page.html <title> and <meta> tags)
hidden content
The page contains an enormous keyword-stuffed category/tag list (hundreds of explicit Thai-language sexual terms and performer names) embedded in the DOM as navigation widgets. This content functions as SEO spam to drive organic search traffic for adult content queries, and is largely invisible in normal browsing context due to overflow-hidden scrollable containers. (location: page.html lines 416-739; page-text.txt lines 76-3656)
brand impersonation
The site uses the WordPress + Elementor + Yoast SEO stack with standard Google Site Kit / Analytics integration to mimic the appearance of a legitimate, professionally built website. The structured data (schema.org) presents the site as a registered Organization with a professional logo, masking its actual nature as an unlicensed adult content distribution site. (location: page.html lines 28, 93-95 (generator meta tags, JSON-LD schema))
social engineering
The site claims to offer free streaming of adult content ('ดูฟรีไม่เสียเงิน' / 'watch free, no cost') as a lure. This is a classic social engineering tactic used to drive high engagement and expose users to potential malvertising, unwanted redirects, or data harvesting as users interact with the site. (location: page.html line 18 (<title>), line 19 (<meta description>))
hidden content
The HTML lang attribute is set to 'th' (Thai) while the domain name is a Turkish personal name (edizdalkilic), and the organization name in JSON-LD references '2023' while the site was registered in 2025. These inconsistencies suggest cloaking or repurposing of an existing domain/template to obscure origin. (location: page.html line 2 (lang=th), line 28 (JSON-LD datePublished vs organization name year))
curl https://api.brin.sh/domain/edizdalkilic.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
edizdalkilic.com 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.