context safety score
A score of 44/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
tls connection failed
Could not establish TLS connection
malicious redirect
TLS connection failed entirely (connected=false, cert_valid=false, san_match=false) for weplayer.cc. The site cannot be reached over HTTPS, which is consistent with a domain used for redirects, parking, or infrastructure that does not serve content directly to browsers but may be used in redirect chains or malicious campaigns. (location: metadata.json: tls object)
brand impersonation
The domain 'weplayer.cc' uses a .cc TLD (Cocos Islands) combined with a media/player-themed name, a pattern commonly used to impersonate legitimate streaming or media player services (e.g., WePlay, media player brands). The domain age is unknown and WHOIS privacy status is undetermined, consistent with a newly registered lookalike domain. (location: metadata.json: domain=weplayer.cc)
phishing
The domain weplayer.cc has unknown domain age, unknown WHOIS privacy status, a .cc TLD, failed TLS, and no blocklist entry yet — a profile consistent with a newly stood-up phishing domain that has not yet been reported. The complete absence of page content despite a crawl attempt suggests the site may be serving content conditionally (e.g., only to targeted victims or specific user-agents). (location: metadata.json, page.html (empty), page-text.txt (empty))
hidden content
All content files (page.html, page-text.txt, page-hidden.txt) are completely empty despite the site being crawled. This is consistent with cloaking behavior — the server may detect automated crawlers and return empty responses, while serving malicious or deceptive content to real users or targeted victims. (location: page.html (0 bytes), page-text.txt (0 bytes), page-hidden.txt (0 bytes))
curl https://api.brin.sh/domain/weplayer.ccCommon questions teams ask before deciding whether to use this domain in agent workflows.
weplayer.cc currently scores 44/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.