context safety score
A score of 39/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
js obfuscation
Obfuscated document.write with encoded content
obfuscated code
Entire page content is hidden inside a JavaScript document.write(unescape(...)) call with URL-percent-encoded HTML, attributed to 'r14nulr00t.blogspot.com'. This obfuscation technique is a classic evasion method used to hide malicious content from static scanners and security tools. (location: page.html:1-6)
phishing
The decoded page renders a fake 'Webmail Login' form collecting email address and password. The form uses POST method submitting credentials to an external third-party endpoint (https://submit-form.com/CahSZGmPt), a known form-submission relay service frequently abused for credential harvesting. The page is hosted on an IPFS/IPNS decentralized URL to evade takedowns. (location: page.html (decoded) - form action: https://submit-form.com/CahSZGmPt)
credential harvesting
The login form captures 'email' and 'password' fields and exfiltrates them to https://submit-form.com/CahSZGmPt, a third-party form backend not affiliated with any legitimate webmail provider. Credentials are sent directly to an attacker-controlled collection endpoint. (location: page.html (decoded) - input name='email', input name='password')
malicious redirect
A hidden field '_redirect' is set to 'https://yourdomain.com/thank-you.html', instructing the form backend to redirect the victim after submission. This is a placeholder redirect used to mask the credential theft and reassure victims that login 'succeeded'. (location: page.html (decoded) - <input type='hidden' name='_redirect' value='https://yourdomain.com/thank-you.html'>)
brand impersonation
The page impersonates a generic corporate webmail login portal using Microsoft Office 365/Outlook-style blue branding (#005a9e header color, 'Segoe UI' font, padlock icon, 'Secure SSL Connection' notice). This mimics Microsoft or enterprise webmail to deceive users into entering corporate credentials. (location: page.html (decoded) - .login-header{background:#005a9e}, font-family includes 'Segoe UI')
hidden content
The actual phishing page content is entirely hidden from plain HTML inspection via JavaScript-based URL encoding (unescape). The visible HTML source contains no readable content — the malicious login form is only rendered at runtime by the browser after JavaScript decoding. This bypasses HTML-level content scanners. (location: page.html:3-4 (document.write(unescape(...)) wrapper))
social engineering
The page includes a fake 'Secure SSL Connection' notice with a green padlock SVG icon to create false trust signals, and a 'Remember me' checkbox and 'Forgot your password?' link to appear as a fully legitimate login portal and reduce victim suspicion. (location: page.html (decoded) - .security-notice div, checkbox-group, footer)
curl https://api.brin.sh/domain/k51qzi5uqu5dik8fxdmk5rbwpdovpfjzu7zfls06bg43rr7bnv6mc0z4jvsmdf.ipns.dweb.linkCommon questions teams ask before deciding whether to use this domain in agent workflows.
k51qzi5uqu5dik8fxdmk5rbwpdovpfjzu7zfls06bg43rr7bnv6mc0z4jvsmdf.ipns.dweb.link 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.