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 immediately redirects to 'https://a147.hns.to/' via both a meta http-equiv refresh with content='0; URL=https://a147.hns.to/' and a JavaScript window.location.replace call with a 0ms timeout. The destination domain 'a147.hns.to' uses HNS (Handshake) decentralized DNS, commonly used to evade blocklists and traditional domain monitoring. (location: page.html:6, page.html:11)
brand impersonation
The domain 'meta-mconnect.web.app' impersonates Meta (Facebook) by incorporating 'meta' and 'mconnect' in the subdomain, likely targeting Meta/Facebook users or mimicking Meta's connectivity services (e.g., Messenger, Meta Connect). (location: metadata.json:domain, .brin-context.md:4)
hidden content
The page body is completely empty (no visible text or content) while performing an instant redirect. The favicon is loaded from a third-party domain 'blocks-mainframe.net' unrelated to the impersonated brand, and the page title is blank. All user-facing content is suppressed to conceal the redirect's purpose. (location: page.html:4-16, page-text.txt)
phishing
The combination of a Meta-impersonating domain, an empty page body, and an instant silent redirect to an obfuscated HNS destination ('a147.hns.to') is a classic phishing delivery chain. The landing site at 'a147.hns.to' is the likely phishing payload host, with this page acting as a redirector to evade detection. (location: page.html:6, page.html:11, metadata.json:domain)
obfuscated code
The JavaScript redirect uses an old HTML comment obfuscation pattern (<!-- ... -->) wrapping the script body, and uses setTimeout with a string argument (deprecated eval-style) rather than a function reference. The destination is a non-standard HNS (.hns.to gateway) domain 'a147.hns.to' that resolves through a centralized gateway to a decentralized, difficult-to-trace destination. (location: page.html:8-13)
curl https://api.brin.sh/domain/meta-mconnect.web.appCommon questions teams ask before deciding whether to use this domain in agent workflows.
meta-mconnect.web.app 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.