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 via meta http-equiv refresh (delay=0) to http://sethittoem.temp.swtest.ru/, a suspicious .ru subdomain on a temporary/test hosting service. The redirect is instantaneous and the destination domain exhibits high-risk characteristics: use of 'temp' and 'swtest' subdomain patterns commonly associated with throwaway phishing infrastructure. (location: page.html:5 — <meta http-equiv="refresh" content="0;URL='http://sethittoem.temp.swtest.ru/'">)
phishing
The site is hosted on a legitimate Google Firebase domain (wgy-df.web.app) but serves solely as a redirect trampoline to http://sethittoem.temp.swtest.ru/. Using trusted cloud infrastructure to launder reputation and bypass blocklists is a canonical phishing delivery technique. The destination .ru temporary-subdomain URL is consistent with phishing kit hosting. (location: page.html:5,12 — meta refresh and anchor href both point to sethittoem.temp.swtest.ru)
social engineering
The visible page text 'Please wait while we redirect you...' and 'Please Click Here if you were not redirected automatically.' is a classic social-engineering lure designed to build urgency and trust, prompting users to voluntarily click through to the malicious destination if the automatic redirect is blocked. (location: page.html:9,12 — body text and anchor element)
brand impersonation
The site exploits the Google Firebase (web.app) domain to appear legitimate and inherit Google's trusted brand reputation. Victims and security filters may associate web.app with Google-owned safe infrastructure, masking the true malicious forwarding behavior. (location: metadata.json — domain: wgy-df.web.app; page.html:5 — redirect to external .ru domain)
curl https://api.brin.sh/domain/wgy-df.web.appCommon questions teams ask before deciding whether to use this domain in agent workflows.
wgy-df.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.