context safety score
A score of 43/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
malicious redirect
Meta refresh tag immediately redirects (content='0; url=...') to an unrelated suspicious domain 'esqdsbhghgwip.com', which has no apparent relationship to the hosting domain 'quncxunesplo.firebaseapp.com'. Zero-delay redirect designed to silently forward visitors. (location: page.html:5 - <meta http-equiv="refresh" content="0; url=https://esqdsbhghgwip.com">)
malicious redirect
JavaScript window.location.href redirect to 'http://deuxmillevingcing.sbs/bboxx/bots' — a suspicious .sbs TLD domain with a path strongly suggesting bot/automated-agent targeting ('/bboxx/bots'). Uses HTTP (not HTTPS), indicating a low-trust destination. The redirect target path '/bboxx/bots' may be specifically designed to serve different content to automated agents or scrapers. (location: page.html:8 - window.location.href = "http://deuxmillevingcing.sbs/bboxx/bots")
prompt injection
The redirect path '/bboxx/bots' on the JavaScript redirect target strongly suggests the destination is designed to serve content specifically to bots or AI agents, potentially delivering adversarial prompt injection payloads to automated systems that follow or analyze this page. (location: page.html:8 - http://deuxmillevingcing.sbs/bboxx/bots)
social engineering
Page presents a fallback anchor link with innocuous text ('suivez ce lien') directing users to the same suspicious domain 'deuxmillevingcing.sbs/bboxx/bots', masking the true destination and encouraging manual navigation to a malicious site if automatic redirect fails. (location: page.html:14 - <a href="http://deuxmillevingcing.sbs/bboxx/bots">lien</a>)
hidden content
The meta refresh redirect target ('esqdsbhghgwip.com') differs from the JavaScript redirect target ('deuxmillevingcing.sbs/bboxx/bots'). Two distinct redirect destinations are present — one in the meta tag and one in JavaScript — potentially routing different clients (e.g., JS-capable browsers vs. crawlers) to different malicious destinations. This split-destination technique is used to evade detection. (location: page.html:5,8 - meta redirect vs. JS redirect pointing to different domains)
curl https://api.brin.sh/domain/quncxunesplo.firebaseapp.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
quncxunesplo.firebaseapp.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.