context safety score
A score of 40/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
encoded payload
suspicious base64-like blobs detected in page content
brand impersonation
The page is served from rocketaccount.com but loads fonts, favicon, and assets exclusively from rocketmortgage.com (e.g., favicon from prod.rockmedialibrary.com referencing 'RocketMortgage', fonts from www.rocketmortgage.com/nsassets/fonts/wntl/). The domain rocketaccount.com is not the official Rocket Mortgage domain, yet it fully impersonates the Rocket Mortgage brand identity. (location: page.html:12, page.html:40)
hidden content
Meta tags for 'noindex,nofollow' and cache-control directives are commented out in the HTML source. This means the page was previously configured to avoid indexing and caching (typical of a staging/phishing page), and those directives have been deliberately suppressed in the live version, leaving no trace in rendered output while keeping the code in the source. (location: page.html:3-5, page-hidden.txt:1-3)
obfuscated code
A script tag loads a resource from a heavily obfuscated path: '/pFi-oE8iLYNf6BIMaOO7Dz1n/EOu5hVpuaYEzNtfE/TXUGYQ/TwU4/LUgBEDkB'. This path is not a recognizable asset filename and appears randomly generated or base64/encoded, consistent with a tracking beacon, fingerprinting script, or credential-harvesting payload loaded dynamically. (location: page.html:54)
credential harvesting
The site presents as 'Rocket Account' — a login/account portal for what appears to be Rocket Mortgage — hosted on the non-official domain rocketaccount.com. Combined with the obfuscated external script and brand impersonation, this page is structured to capture user credentials (username/password) under the guise of a legitimate account portal. (location: page.html:8, page.html:54)
phishing
rocketaccount.com is not the official Rocket Mortgage domain (rocketmortgage.com). The site fully mimics the Rocket Mortgage brand (title 'Rocket Account', official fonts, favicon, color scheme) while operating on a lookalike domain, consistent with a phishing page designed to steal Rocket Mortgage customer credentials. (location: page.html:8-12, metadata.json)
curl https://api.brin.sh/domain/rocketaccount.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
rocketaccount.com currently scores 40/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.