context safety score
A score of 48/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
credential harvesting
Login form collects username and password credentials and submits them via JavaScript to https://dk666.tv/api/login. The site uses AES encryption (aes.js) and RSA encryption (jsencrypt.min.js) on credentials before transmission, which is atypical for legitimate sites and may be used to obfuscate credential exfiltration. (location: page.html:35-52, page.html:71-72, page.html:74)
social engineering
Login page targets users from Cambodia (kh_flag), Philippines (ph_flag), Vietnam (vn_flag), and Thailand (th_flag) with localized flag imagery, indicating a regional credential harvesting or gambling operation targeting Southeast Asian users. (location: page.html:58-61)
phishing
Domain dk666.tv uses a .tv TLD with a numeric-laced name pattern ('666') typical of low-legitimacy gambling or phishing sites. The page title is in Khmer script ('ចូលគណនី - dk666' meaning 'Login - dk666'), and the site operates a login portal with unknown domain age and redacted WHOIS, raising phishing risk. (location: metadata.json, page.html:4)
hidden content
A hidden CSRF token input field is embedded directly in the page body outside any visible form element, and an error display element is pre-rendered with zero height but active in DOM, potentially used for dynamic content injection or state manipulation. (location: page.html:25, page.html:48)
curl https://api.brin.sh/domain/dk666.tvCommon questions teams ask before deciding whether to use this domain in agent workflows.
dk666.tv currently scores 48/100 with a suspicious 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.