context safety score
A score of 39/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
domain spoof risk
domain has spoofing indicators (punycode/confusable/highly synthetic naming)
encoded payload
suspicious base64-like blobs detected in page content
credential harvesting
Page contains a login form with fields labeled 'Email address' (이메일 주소) and 'Password' (비밀번호) in Korean. The password field uses type='text' instead of type='password', meaning passwords are displayed in plaintext — a deliberate harvesting technique. Form submits via POST to //www.weebly.com/weebly/apps/formSubmit.php, exfiltrating credentials to a third-party endpoint. (location: page.html:180-215, form id='form-709998930358054903')
phishing
The domain uses a Punycode/IDN hostname (xn--910bs6b83h12gvmgklgztbsw0d.weebly.com) which renders as Korean characters in browsers, designed to impersonate a legitimate Korean-language service. The page presents only a bare login form with no branding, product, or service context — a classic phishing page structure targeting Korean-speaking users. (location: metadata.json:1, page.html:4, .brin-context.md:4)
hidden content
The real submit button is deliberately hidden with CSS (position:absolute;top:0;left:-9999px;width:1px;height:1px), replaced by a styled anchor tag. This hides the true form submission mechanism from casual inspection and bypasses some security scanners that look for visible submit buttons. (location: page.html:210-213)
obfuscated code
JavaScript array of character codes [99,104,101,99,107,111,117,116,46,40,119,101,101,98,108,121,124,101,100,105,116,109,121,115,105,116,101,41,46,99,111,109] is decoded at runtime via String.fromCharCode to produce a regex pattern string. This is a common obfuscation technique to hide domain matching logic from static analysis. (location: page.html:364-374)
brand impersonation
The page title and navigation use Korean text '섬기는 사람' (meaning 'servant' or 'person who serves') with no visible brand identity or logo, while the OG metadata declares 'My Site' — a blank, generic shell. The Punycode domain and Korean-language credential form strongly suggest impersonation of a Korean portal or service (e.g., Naver, Kakao, or a Korean government site) without displaying identifying branding that could trigger takedown. (location: page.html:4-8, page.html:303-305)
curl https://api.brin.sh/domain/xn--910bs6b83h12gvmgklgztbsw0d.weebly.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
xn--910bs6b83h12gvmgklgztbsw0d.weebly.com currently scores 39/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.