context safety score
A score of 38/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
encoded payload
suspicious base64-like blobs detected in page content
brand impersonation
The site nagad88a.com impersonates the Nagad88 gambling brand, using its logo, name, and branding assets (e.g., og:image references 'Nagad88com' and 'nagad88logo.png') while operating on a lookalike domain. The og:url and meta url tags point to 'nagad88f.com', not the scanned domain, indicating this is a clone/mirror site. (location: page.html: meta og:url, og:image, meta name=url)
malicious redirect
The canonical og:url and meta url content both reference 'https://www.nagad88f.com' and 'https://www.nagad88f.com/en-BD/home', which differ from the scanned domain nagad88a.com. JavaScript dynamically rewrites page title and description based on the current hostname, suggesting a multi-domain redirect network where traffic is funneled across several lookalike domains (nagad88.online, nagad88f.com, nagad88a.com). (location: page.html lines 9-17, meta og:url, meta name=url)
social engineering
The site presents itself as a 'trusted' and 'official' online casino and sports betting platform in Bangladesh with language like 'Trusted Casino', 'Reliable Platform', and 'Safe Experience' in meta keywords to build false credibility and lure users into gambling and financial transactions on an unverified 138-day-old domain. (location: page.html: meta keywords, og:description, meta description)
hidden content
The page body renders no visible content without JavaScript (SPA framework, likely Vue.js based on 'v-application' CSS classes), making all actual page content and functionality invisible to non-JS crawlers and security scanners. The real content, links, and forms are hidden inside dynamically loaded JavaScript chunks, preventing static analysis of credential harvesting forms or phishing flows. (location: page.html: noscript message, JS chunk preloads, page-text.txt lines 1-51)
brand impersonation
Multiple third-party ad and tracking scripts are loaded, including ExoClick (adult/gambling ad network: a.exoclick.com/tag_gen.js), Sportradar tag manager, Opera ad tracking (res-odx.op-mobile.opera.com/sp.js), and Google Tag Manager with IDs GTM-NN68BWHR and GTM-W8BF5C4. The ExoClick integration with a specific conversion goal ID suggests this site is part of an affiliate or ad fraud network exploiting the Nagad88 brand. (location: page.html lines 32-45, 46-58)
malicious redirect
The domain nagad88a.com is only 138 days old and not the canonical domain referenced in its own metadata (nagad88f.com). This pattern — young domain, canonical pointing elsewhere, multi-hostname JS branching — is consistent with a rotating domain infrastructure used to evade blocklists by cycling through new domains when old ones are flagged. (location: metadata.json: domain_age_days=138, page.html: hostname-based JS branching)
curl https://api.brin.sh/domain/nagad88a.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
nagad88a.com currently scores 38/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.