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 conditional redirect: visitors from Tunisia (TN) or Bulgaria (BG) are silently redirected to 'https://m-postbkn.web.app/' — a suspicious Firebase-hosted domain mimicking a postal/banking service. All other visitors are redirected to google.com as a decoy to avoid analysis. (location: page.html:1031, window.location.href = 'https://m-postbkn.web.app/')
social engineering
The page uses a traffic filtering system combining IP geolocation, ISP/provider blacklisting, and country-code checks to selectively expose malicious content only to real end-users in targeted countries (TN=Tunisia, BG=Bulgaria), while showing google.com to security researchers, bots, crawlers, and analysts. This is a classic phishing evasion technique designed to deceive automated security tools and human analysts. (location: page.html:23-38, checkCountry() and redirectBasedOnBlacklist() functions)
phishing
The destination domain 'm-postbkn.web.app' appears to impersonate a postal or banking service (post + bank abbreviation). The combination of geo-targeting to TN (Tunisia) and BG (Bulgaria), the evasion of security scanners, and the Firebase-hosted decoy landing strongly indicates a phishing campaign targeting users of postal/banking services in those countries. (location: page.html:1031, redirect target https://m-postbkn.web.app/)
brand impersonation
The redirect destination 'https://m-postbkn.web.app/' uses 'm-post' and 'bkn' (likely abbreviation for 'bank') in the subdomain, suggesting impersonation of a mobile postal or banking brand, possibly La Poste Tunisienne or a Bulgarian postal/banking service targeted at users from TN and BG. (location: page.html:1031, redirect target domain m-postbkn.web.app)
hidden content
The page displays no visible content to users (title is 'waiting', body has no rendered text). All logic is entirely within a script block that silently fingerprints the visitor and redirects them. The true malicious payload is hidden from casual inspection and only exposed to targeted victims. (location: page.html:4 (<title>waiting</title>), page.html:6-1041 (body contains only script, no visible content))
social engineering
Extensive IP and provider blacklist (500+ entries) specifically excludes security vendors (Palo Alto Networks, Zscaler, Cisco OpenDNS), cloud providers (Google, Microsoft, Amazon, OVH), VPN/proxy providers, and known security research infrastructure. This anti-analysis fingerprinting is designed to hide malicious behavior from security researchers and automated scanners while targeting real end-users. (location: page.html:43-999, ipBlacklist and providerBlacklist arrays including entries like 'PALO ALTO NETWORKS', 'Zscaler Switzerland GmbH', 'Cisco OpenDNS, LLC')
curl https://api.brin.sh/domain/zokoulou.firebaseapp.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
zokoulou.firebaseapp.com 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.