context safety score
A score of 37/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
The page presents a Korean-language login form collecting '이메일 주소' (email address) and '비밀번호' (password) as plain text inputs (type='text' not type='password'), submitting to //www.weebly.com/weebly/apps/formSubmit.php. The password field uses type='text' instead of type='password', meaning credentials are visible in plaintext. The site has no apparent legitimate service identity, indicating this is a credential harvesting form. (location: page.html:187-200, form id='form-377843196366606256')
phishing
The domain uses a Punycode/IDN hostname (xn--1-pd6er94a.weebly.com) which encodes non-ASCII characters to disguise the true domain name. The page title and navigation contain Korean text '섬기는 사람' (serving person) with no identifiable brand or service, but presents a login form harvesting email and password — a classic phishing page structure hosted on a free website builder to avoid detection. (location: metadata.json:domain, page.html:4,305,321)
brand impersonation
The page is hosted on Weebly (a legitimate website builder) and leverages Weebly's infrastructure and branding (CDN, footer 'Powered by Weebly', Weebly signup links) to add a veneer of legitimacy to what appears to be a credential harvesting login form targeting Korean-speaking users. The og:title is set to 'My Site' while the actual page title is Korean, suggesting the page was not set up transparently. (location: page.html:5,265-283)
hidden content
The submit button for the login form is positioned off-screen using CSS 'position:absolute;top:0;left:-9999px;width:1px;height:1px', hiding the real submit button from view. A fake anchor element styled as a button is shown instead. This is a technique used to obscure form submission mechanics from users and security scanners. (location: page.html:212-215)
obfuscated code
A JavaScript array of character codes 'var r = [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 using String.fromCharCode to construct a regex pattern. While this appears to be Weebly's analytics cross-domain linker pattern ('checkout.(weebly|editmysite).com'), the technique of encoding strings as character arrays to avoid static analysis is an obfuscation pattern commonly associated with malicious scripts. (location: page.html:368-378)
social engineering
The page presents a minimal, stripped-down Korean-language login interface with no identifying brand, no terms of service, no privacy policy, and no explanation of what service the user is logging into. The use of Korean text ('이메일 주소', '비밀번호', '로그인') targets Korean-speaking users who may be deceived into believing this is a legitimate login portal for a familiar service. The storeCountry is set to 'NG' (Nigeria) while targeting Korean users, which is anomalous. (location: page.html:100,187,195,214)
curl https://api.brin.sh/domain/xn--1-pd6er94a.weebly.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
xn--1-pd6er94a.weebly.com currently scores 37/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.