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
The page performs a conditional redirect to 'https://dfkrezd.web.app' — an unknown Firebase-hosted application — exclusively for visitors from Tunisia (TN) or Bulgaria (BG) who are not bots/crawlers. All other visitors are redirected to example.com as a decoy. This is a classic cloaking-and-redirect pattern used in phishing campaigns to evade automated scanners while delivering malicious content only to targeted geographic victims. (location: page.html:1031, window.location.href = 'https://dfkrezd.web.app')
social engineering
The page uses extensive bot/crawler detection to hide malicious behavior from security researchers, automated scanners, and major cloud providers (Google, Microsoft, Amazon, Facebook, OVH, DigitalOcean, Palo Alto Networks, Zscaler, etc.). Over 500 IPs and dozens of ISPs/ASNs associated with security tooling are blacklisted. The page presents as a blank 'waiting' page to evade analysis. This is deliberate deception designed to pass manual and automated security reviews while targeting real end users. (location: page.html:40-1024, redirectBasedOnBlacklist function with extensive ip/provider blacklists)
hidden content
The page title is 'waiting' and the body contains no visible content — the entire page behavior is controlled by JavaScript that runs silently. The actual destination URL (https://dfkrezd.web.app) and the targeting logic (geo-filtering to TN/BG) are hidden from casual inspection and from any scanner or browser that gets classified as a bot. (location: page.html:4-6, <title>waiting</title> with empty body except script)
phishing
The infrastructure pattern — a throwaway Firebase subdomain (yasdroumenhouna.firebaseapp.com) acting as a transparent redirector to another Firebase app (dfkrezd.web.app), with geo-targeting restricted to Tunisia and Bulgaria, bot-evasion blacklists, and a blank decoy page — is consistent with a phishing campaign landing page. Firebase free hosting is commonly abused for phishing due to the trusted google-managed TLS and domain reputation. (location: metadata.json: domain=yasdroumenhouna.firebaseapp.com; page.html:1031 redirect target=https://dfkrezd.web.app)
malicious redirect
Visitor IP geolocation is collected via a third-party API (https://ip-api.io/json/) prior to any redirect decision. The collected data includes IP, city, region, country code, ISP/organisation, and timezone. This data exfiltration to a third-party service occurs silently without user consent and feeds the targeting logic. (location: page.html:18, xhr.open('GET', 'https://ip-api.io/json/', true))
curl https://api.brin.sh/domain/yasdroumenhouna.firebaseapp.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
yasdroumenhouna.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.