context safety score
A score of 39/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
hidden instruction
high hidden content ratio detected in DOM
brand impersonation
The page title is generic 'Dashboard' and meta description references 'Coderthemes' admin template, while the domain laser247.pro appears to be an online gambling/betting platform. The site uses a stolen or repurposed admin theme template (Coderthemes) to construct a fake dashboard interface, impersonating a legitimate business platform. (location: page.html:3,9,10)
hidden content
The page-text.txt contains only whitespace — the visible text content is entirely empty despite a full HTML shell being rendered. This indicates the real content is loaded dynamically via Angular (app-root) or deliberately hidden from static analysis, a common technique to evade content scanners. (location: page-text.txt:1-4, page.html:50)
malicious redirect
External script loaded from speedcdn.io (https://speedcdn.io/flashphoner/js/flashphoner.bundle.min.js) — a third-party CDN not affiliated with any major provider. Loading executable JavaScript from an unknown CDN allows the CDN operator to inject arbitrary code, redirect users, or harvest credentials. The associated CSS is also loaded from this domain. (location: page.html:13,14)
credential harvesting
The site is a gambling/betting platform (laser247.pro) that renders a login/dashboard interface via an Angular SPA (app-root). The page-text is empty indicating the credential form is dynamically injected. Combined with external script loading from speedcdn.io, this architecture is consistent with a credential harvesting setup where login forms are injected client-side to avoid static detection. (location: page.html:50-51)
phishing
laser247.pro uses a .pro TLD with 'laser247' branding, a pattern commonly associated with cloned or fake versions of legitimate betting/gaming sites (e.g., Laser247 is a known brand in online gambling). The site appears to be a spoofed or unauthorized clone using a deceptive domain to lure users of the legitimate service, collecting credentials or payments under a false brand identity. (location: metadata.json:domain, page.html:3)
hidden content
Multiple commented-out viewport meta tags and script references in HTML comments suggest iterative obfuscation testing or remnants of template manipulation. A commented-out HTTP (non-HTTPS) jQuery UI script reference (http://ajax.googleapis.com) is present, indicating mixed-content loading was previously attempted. (location: page-hidden.txt:1-17)
curl https://api.brin.sh/domain/laser247.proCommon questions teams ask before deciding whether to use this domain in agent workflows.
laser247.pro currently scores 39/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.