context safety score
A score of 32/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
Domain nagad88f.com impersonates the brand 'Nagad88' — the appended 'f' is a typosquat/lookalike variant. The site uses the Nagad88 name, logo (nagad88logo.png), favicon, and full branding to pass itself off as the official platform. The og:image references 'www.Nagad88com' (yet another domain variant), indicating a network of lookalike domains. (location: page.html: <meta name=og:site_name content=Nagad88>, <meta name=og:image content=https://www.Nagad88com/static/image/home/nagad88logo.png>)
brand impersonation
The page's JavaScript dynamically rewrites the title and meta description based on the current hostname (nagad88f.com, nagad88.online, or default), revealing a multi-domain impersonation infrastructure operating under the same codebase across multiple lookalike domains. (location: page.html lines 4-17: domain_all hostname-switching script)
social engineering
The site presents itself as a 'trusted' and 'official' online casino and sports betting platform targeting Bangladesh users ('Official Site for Cricket Betting and Online Casino Bangladesh'). The combination of a 78-day-old domain with authoritative 'official' and 'trusted' branding is a classic social engineering pattern to build false legitimacy for a gambling/credential-harvesting platform. (location: page.html: <title>Nagad88 - Official Site for Cricket Betting and Online Casino Bangladesh</title>, <meta name=description>)
malicious redirect
An ExoClick ad tag (known adult/gambling ad network) is loaded unconditionally via external script with a conversion tracking goal ID. ExoClick tags are frequently abused to serve malvertising and drive-by redirects to phishing or malware pages. (location: page.html line 32: <script src=https://a.exoclick.com/tag_gen.js data-goal=650c398bdddf916e77d6e7b7f7ff3804 data-value={conversion_value}>)
malicious redirect
Opera/OPay ad tracking pixel loaded via '//res-odx.op-mobile.opera.com/sp.js' with advertiser ID 'adv11876078298304'. This third-party tracker is loaded on what presents as an 'official' site and can be used for audience retargeting and redirect chains. (location: page.html line 58: otag('init', 'adv11876078298304'))
hidden content
The page is a JavaScript-rendered SPA (Vue.js/Vuetify) that serves essentially no visible content without JS enabled. The static HTML shell conceals the actual page content from non-JS crawlers and security scanners, a technique used to hide credential-harvesting forms, malicious content, or cloaked pages from automated analysis. (location: page-text.txt line 1: 'We're sorry but the system doesn't work properly without JavaScript enabled')
credential harvesting
The site operates as an online gambling/casino platform (login, registration, deposits) on a 78-day-old lookalike domain impersonating a known brand. Users tricked into registering will submit credentials, payment details, and personal information to an unverified operator. The domain age, multi-domain infrastructure, and brand impersonation pattern are strongly consistent with credential harvesting operations. (location: metadata.json: domain_age_days=78; page.html: og:title, og:description referencing casino registration)
curl https://api.brin.sh/domain/nagad88f.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
nagad88f.com currently scores 32/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.