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
Page performs an immediate meta-refresh redirect (content="0; URL=...") to an external domain 'fr.tc-hs.org' with no user interaction required. The redirect fires instantly on page load. (location: page.html:5 - <meta http-equiv="refresh" content="0; URL=https://fr.tc-hs.org?iduser=TkRJMU1RPT0=&a5=C7Qxf" />)
credential harvesting
The redirect URL contains a query parameter 'iduser=TkRJMU1RPT0=' which decodes from Base64 to 'NDI1MQ==' (a further Base64-encoded value resolving to '4251'), indicating a tracked user identifier being passed to an external site — consistent with credential harvesting or account takeover infrastructure. (location: page.html:5 - iduser=TkRJMU1RPT0= in redirect URL)
obfuscated code
The 'iduser' parameter value 'TkRJMU1RPT0=' is double Base64-encoded, obfuscating a user tracking token. An additional opaque parameter 'a5=C7Qxf' is also appended, suggesting obfuscated tracking or session correlation passed to the destination phishing infrastructure. (location: page.html:5 - query string parameters iduser and a5 in redirect URL)
phishing
The site is hosted on a legitimate Firebase subdomain (docfactor-be6bd.firebaseapp.com) to lend credibility, but immediately redirects victims to 'fr.tc-hs.org', an unrelated external domain. This is a classic phishing trampoline pattern abusing trusted cloud hosting to evade reputation filters. (location: page.html:5 - meta-refresh to https://fr.tc-hs.org)
hidden content
The page body is completely empty with no visible content (page-text.txt contains only whitespace), while the only functional element is the hidden meta-refresh redirect in the <head>. This conceals the malicious redirect from casual inspection and makes the page appear blank to users. (location: page.html:7-9 - empty <body>; page-text.txt lines 1-3)
curl https://api.brin.sh/domain/docfactor-be6bd.firebaseapp.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
docfactor-be6bd.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.