context safety score
A score of 47/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
Meta refresh tag redirects visitors after 2 seconds to https://nqd.yfm.mybluehost.me/PASS/ — an unrelated third-party host on shared hosting (mybluehost.me) with a suspicious /PASS/ path strongly indicative of a credential harvesting or phishing landing page. (location: page.html:6 — <meta content='2;URL=https://nqd.yfm.mybluehost.me/PASS/' http-equiv='refresh'/>)
brand impersonation
The page uses the official PayPal favicon (loaded from https://www.paypalobjects.com/webstatic/icon/favicon.ico) to visually impersonate PayPal in browser tabs and bookmarks, while the actual site is an unrelated Blogger page acting as a redirect intermediary. (location: page.html:5 — <link href='https://www.paypalobjects.com/webstatic/icon/favicon.ico' rel='icon'/>)
phishing
The page combines PayPal brand impersonation (favicon), a deceptive 'redirecting, please wait' message in German, and an automatic meta-refresh to a /PASS/ endpoint on a third-party host. This is a classic phishing relay pattern designed to harvest PayPal credentials. (location: page.html:5-6,20,30)
credential harvesting
Redirect destination path '/PASS/' on nqd.yfm.mybluehost.me is a strong indicator of a password/credential harvesting page. Combined with the PayPal favicon impersonation, this page functions as a phishing relay funneling victims to a credential collection endpoint. (location: page.html:6 — https://nqd.yfm.mybluehost.me/PASS/)
social engineering
Page title and visible body text read 'Umleitung wird durchgeführt, bitte warten...' (German: 'Redirect is being performed, please wait...') — a social engineering message designed to lower user suspicion and keep them on the page during the 2-second auto-redirect countdown. (location: page.html:20,30 — <title> and <h3> elements)
curl https://api.brin.sh/domain/xfgyjm.blogspot.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
xfgyjm.blogspot.com currently scores 47/100 with a suspicious verdict and medium 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.