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 in <head> immediately redirects all visitors to an external suspicious URL at 'auc.bqv.mybluehost.me' via window.location.href assignment. The redirect is unconditional and executes before any page content renders, passing URL hash fragments (ref, date, courriel) as query parameters to the destination — a classic phishing traffic-forwarding pattern. (location: page.html:26-33, <script> block in <head>)
phishing
The redirect destination 'https://auc.bqv.mybluehost.me/website_90a8ee5d/wp-content/css/12//?op=1&ref=...&date=...&courriel=...' uses a non-descriptive subdomain on a shared host, a randomized path under wp-content/css (anomalous for CSS directories), and passes 'courriel' (French for 'email') as a tracked parameter — strongly indicating a phishing landing page designed to harvest email credentials. (location: page.html:29, randURLs array value)
credential harvesting
The redirect URL passes URL hash fragments including 'courriel' (email address) as a query parameter to the external destination. This pattern is used in phishing campaigns to pre-populate or track victim email addresses at the harvesting endpoint, confirming credential-harvesting intent. (location: page.html:29, query parameters: &courriel= + hash[2])
hidden content
The page body contains no visible content whatsoever (empty blog with 'Aucun article'). The entire functional payload is concealed inside a <script> block in the <head> that executes the redirect silently, making the malicious behavior invisible to casual inspection and bypassing content-based filters that only examine rendered text. (location: page.html:39-42, page-text.txt:1-12 (body renders empty))
social engineering
The page abuses the trusted blogspot.com domain (Google-hosted, valid DV TLS cert from Google Trust Services) to lend legitimacy to the redirect chain. Victims and automated tools are more likely to trust a blogspot.com URL, masking the true malicious destination on mybluehost.me. (location: metadata.json: domain=yagfalabfgal.blogspot.com, tls.issuer=Google Trust Services)
curl https://api.brin.sh/domain/yagfalabfgal.blogspot.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
yagfalabfgal.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.