context safety score
A score of 45/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
phishing
1 deceptive links where visible host does not match destination host
brand impersonation
The domain marvelvsdc.faith presents itself as a 'Marvel vs DC' wiki using MediaWiki software, but the actual page content is entirely unrelated commercial Chinese-language content advertising a Hong Kong scrap metal recycling and demolition company (柏承貿易有限公司 / pak-shing.net). The legitimate-sounding wiki branding is being used as a facade to host SEO spam content. (location: page.html:title, page.html:28, page-text.txt:8)
social engineering
The site exploits the trusted appearance of a MediaWiki installation (complete with standard wiki navigation, 'From Marvel vs DC' attribution, and MediaWiki branding) to lend credibility to commercial spam content for a third-party business. This deceptive presentation manipulates users and search engines into trusting the content. (location: page.html:1-183, page-text.txt:1-146)
malicious redirect
Multiple external links embedded in the wiki content redirect visitors away from marvelvsdc.faith to pak-shing.net (e.g., https://www.pak-shing.net/%E4%BA%94%E9%87%91%E5%9B%9E%E6%94%B6, https://www.pak-shing.net/%E6%B8%85%E6%8B%86%E9%82%84%E5%8E%9F, https://www.pak-shing.net/%E6%B8%85%E5%A0%B4%E6%9C%8D%E5%8B%99). The wiki shell is being used purely as a link-farm to drive traffic to an external commercial site. (location: page.html:35, page.html:61)
hidden content
The domain name 'marvelvsdc.faith' and the wiki title 'Marvel vs DC' are completely disconnected from the page's actual content (Chinese-language commercial services). The .faith TLD combined with pop-culture branding is used to attract clicks or evade filters, while hiding the true commercial/spam nature of the content from users and automated scanners. (location: metadata.json:domain, page.html:5)
curl https://api.brin.sh/domain/marvelvsdc.faithCommon questions teams ask before deciding whether to use this domain in agent workflows.
marvelvsdc.faith currently scores 45/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.