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
phishing
The domain uses a Punycode/IDN homograph encoding (xn--serviciodeverificacindeidentidad-9dd) that decodes to 'servicodeverificacióndeidentidad' — Spanish for 'identity verification service'. This is a classic phishing lure designed to impersonate a legitimate identity or government verification portal, hosted on a free Weebly site with no authentic branding. (location: domain: xn--serviciodeverificacindeidentidad-9dd.weebly.com)
credential harvesting
The page contains a login form with fields labeled 'Correo electrónico' (email) and 'Contraseña' (password). Critically, the password field uses type='text' instead of type='password', meaning the password is displayed in plaintext. The form submits to //www.weebly.com/weebly/apps/formSubmit.php — an external third-party endpoint — exfiltrating credentials to the attacker's Weebly account. There is no legitimate service branding, no privacy policy, and no indication of what service the credentials are for. (location: page.html:152-187, form id='form-287281964211661264')
credential harvesting
The submit button is rendered off-screen using CSS (position:absolute; top:0; left:-9999px; width:1px; height:1px), making it invisible to users. A visible anchor element styled as a button ('Iniciar sesión') is used instead, obscuring the real form submission mechanism and making the credential harvesting harder to detect. (location: page.html:182-185)
brand impersonation
The site title and all OG metadata are generically set to 'My Site' while the domain name explicitly claims to be an 'identity verification service' in Spanish. The site has no actual branding, logo, or content — only a login form — strongly suggesting it is impersonating a legitimate identity verification authority (e.g., a government or financial institution) without displaying explicit branding to avoid detection. (location: page.html:4-6, metadata.json)
social engineering
The domain name 'servicio de verificación de identidad' (identity verification service) in Spanish is designed to create a sense of official legitimacy and urgency, coercing Spanish-speaking victims into submitting their credentials under the belief they are completing an identity verification process with an authoritative entity. (location: domain: xn--serviciodeverificacindeidentidad-9dd.weebly.com)
hidden content
The page site locale is set to 'fr_FR' (French) and store country to 'TW' (Taiwan) with currency 'TWD' (Taiwan Dollar), while all visible content is in Spanish. This geographic/language mismatch is inconsistent with a legitimate identity verification service and may indicate deliberate obfuscation of the site's true origin or targeting. (location: page.html:98-102)
obfuscated code
A character-code array is used to obfuscate a domain string: 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]. Decoded via String.fromCharCode, this yields 'checkout.(weebly|editmysite).com', used as a regex for cross-domain link tracking. While this specific pattern originates from Weebly's platform analytics code, its presence alongside active credential harvesting warrants flagging as it demonstrates obfuscation techniques on this malicious page. (location: page.html:319-329)
curl https://api.brin.sh/domain/xn--serviciodeverificacindeidentidad-9dd.weebly.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
xn--serviciodeverificacindeidentidad-9dd.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.