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 credentials are displayed in plaintext. The form submits to //www.weebly.com/weebly/apps/formSubmit.php — a generic Weebly form handler — not to any legitimate authentication backend. This is a credential harvesting form designed to collect email/password pairs. (location: page.html:182-217, form id=form-697592512951408367)
phishing
The domain uses a Punycode/IDN hostname (xn--9i1bu1tbpd0qfrvd.weebly.com) which renders as Korean characters in browsers, a classic homograph/IDN phishing technique to impersonate legitimate Korean-language services. The site presents a bare login form with no branding, no navigation links, and no context — consistent with a credential phishing page targeting Korean users. (location: metadata.json:domain, page.html:4 (title: 섬기는 사람), .brin-context.md:4)
hidden content
The real form submit button is hidden off-screen using inline CSS 'position:absolute;top:0;left:-9999px;width:1px;height:1px'. A visually-styled anchor tag (<a class='wsite-button'>) is displayed instead. This pattern obscures the true form submission mechanism from casual inspection and from users, a technique used to evade automated detection and confuse victims. (location: page.html:212-215)
obfuscated code
A numeric character array is decoded at runtime using String.fromCharCode to construct a regex string: [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] decodes to 'checkout.(weebly|editmysite).com'. While this particular decoded value appears to be Weebly's own cross-domain analytics regex, the obfuscation pattern (runtime char-code array decoding) is a recognized technique for hiding malicious strings from static scanners. (location: page.html:375-385)
social engineering
The page title and sole navigation item both read '섬기는 사람' (Korean for 'serving person' or 'servant'), providing no legitimate context, brand name, or service explanation. Presenting only a login form with no identifying information is a social engineering technique that pressures users to submit credentials without verifying the legitimacy of the site. (location: page.html:4, page.html:315-316)
curl https://api.brin.sh/domain/xn--9i1bu1tbpd0qfrvd.weebly.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
xn--9i1bu1tbpd0qfrvd.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.