context safety score
A score of 43/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
js obfuscation
JavaScript contains heavy hex-escape encoding typical of obfuscation
malicious redirect
JavaScript on page load immediately redirects all visitors to an external third-party URL (https://pzz.isd.mybluehost.me/wp-content/12/12//) with no user interaction required. The redirect passes URL hash fragments as query parameters named 'ref', 'date', and 'courriel' (French for 'email'), strongly indicating a phishing or credential-harvesting landing page relay. (location: page.html:26-33, <script> block in <head>)
phishing
The redirect destination URL (https://pzz.isd.mybluehost.me/wp-content/12/12//?op=1&...) uses query parameters 'op=1', 'ref', 'date', and 'courriel' — a pattern consistent with phishing kits that pre-populate email addresses and tracking metadata on a fake login or credential-collection page. (location: page.html:29, randURLs array)
credential harvesting
The URL fragment (#) is parsed and its components passed as 'ref', 'date', and 'courriel' parameters to the redirect destination. This technique allows the attacker to pre-fill victim email addresses into a credential-harvesting form on the destination site, bypassing the need to collect them on this page. (location: page.html:27-29, hash parsing and redirect logic)
hidden content
The page renders no visible content to users (body contains only empty div elements with no posts — 'Aucun article'). All functional behavior is contained in JavaScript that executes silently and redirects immediately. The page acts as an invisible relay/doorway page with no legitimate content. (location: page.html:40-42, body content; page-text.txt confirms absence of visible text)
social engineering
The page abuses the trusted blogspot.com (Google Blogger) platform to host a redirect page, exploiting the domain's reputation and legitimate TLS certificate to bypass security filters and appear trustworthy to users and automated scanners before silently forwarding victims to a malicious third-party host. (location: metadata.json, page.html — hosted on jcamalalaj.blogspot.com)
curl https://api.brin.sh/domain/jcamalalaj.blogspot.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
jcamalalaj.blogspot.com currently scores 43/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.