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 geo-targeted and IP-filtered redirection to 'https://cadizgunworks.com/sumart/fid/' for visitors from Tunisia (TN) or Bulgaria (BG) who are not identified as bots/crawlers. This is a classic cloaking redirect used in phishing campaigns to deliver malicious payloads only to targeted victims while showing benign content to scanners. (location: page.html:1043)
social engineering
The page implements a sophisticated multi-layer victim filtering system: it checks the visitor's country code (only allowing TN/BG), IP address against a 500+ entry blacklist, and ISP/provider against a blacklist of cloud providers, security vendors (Palo Alto Networks, Zscaler), and research infrastructure (Google, Microsoft, Amazon, Facebook, DigitalOcean). This is designed to evade security analysis while targeting real end-users in specific geographies for a social engineering or phishing attack. (location: page.html:34-56, page.html:944-1012)
hidden content
The page has a title of 'waiting' and no visible body content — the entire page logic is executed via JavaScript. The redirection target and filtering logic are hidden from casual inspection and from users with JavaScript disabled. The page-text.txt shows only raw script code, confirming there is no human-readable content visible to the user, only JavaScript executing silently. (location: page.html:4, page.html:7-1053)
phishing
The destination URL 'https://cadizgunworks.com/sumart/fid/' follows a path structure ('/sumart/fid/') commonly associated with phishing kits (subdirectory staging). Combined with the geo-targeting (TN/BG) and bot-evasion, this strongly indicates the redirect leads to a phishing page targeting users in Tunisia or Bulgaria. (location: page.html:1043)
obfuscated code
The page uses a hardcoded IP geolocation API key ('aSkHvvXPpcHZeSv') in a call to 'https://pro.ip-api.com/json/?fields=17031711&key=aSkHvvXPpcHZeSv' to perform victim profiling. The API key is embedded in client-side JavaScript, and the field bitmask '17031711' is used to request specific data fields (IP, city, region, country code, ISP) in a non-obvious encoded format, obscuring the full scope of data being collected from visitors. (location: page.html:29)
social engineering
The blacklist explicitly includes security vendors and analysis infrastructure (PALO ALTO NETWORKS, Zscaler Switzerland GmbH, Cisco OpenDNS, Luxembourg House of Cybersecurity, Zwiebelfreunde e.V.) alongside major cloud and hosting providers. This demonstrates deliberate, targeted evasion of security scanning tools and threat intelligence platforms to prevent detection of the malicious redirect. (location: page.html:944-1012)
curl https://api.brin.sh/domain/redirectfibanhj.web.appCommon questions teams ask before deciding whether to use this domain in agent workflows.
redirectfibanhj.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.