context safety score
A score of 37/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
phishing
1 deceptive links where visible host does not match destination host
malicious redirect
script/meta redirect patterns detected in page source
social engineering
A JavaScript confirm() dialog fires immediately on page load with a false security warning: 'Your download activity is being exposed and puts you at risk. Protect yourself with NordVPN.' This is a fabricated threat alert designed to frighten users into clicking OK, which then redirects them to an affiliate VPN offer. The message is deceptive — there is no actual exposure or risk being detected. (location: page.html:13-16, inline <script> block)
malicious redirect
If the user clicks OK on the fake security alert dialog, window.location.href is set to '/offers/nordvpn/?sid=CoolROM_Alert', an affiliate tracking redirect. This is a forced navigation triggered by social engineering, not user intent. (location: page.html:14)
social engineering
The Facebook share button and Twitter tweet iframe are both pre-configured to share the NordVPN affiliate offer URL ('/offers/nordvpn/?sid=CoolROM_Alert') rather than the site's homepage. This attempts to use the user's social accounts to propagate the affiliate/scam redirect to their contacts. (location: page.html:335, page.html:338)
hidden content
A push notification SDK (push-sdk.com/f/sdk.js?z=665109) is dynamically injected into the page head via JavaScript, tracking click_id and source_id URL parameters. This is a covert push notification subscription mechanism that can harvest user permission and send unsolicited push notifications without transparent disclosure. (location: page.html:106-125)
malicious redirect
The og:url canonical and rel=canonical tags point to 'https://coolrom.com/' (without .au) while the actual domain being served is coolrom.com.au. This cross-domain canonical mismatch may be used to transfer SEO authority or confuse agents/crawlers about the true domain identity. (location: page.html:30, page.html:36)
curl https://api.brin.sh/domain/coolrom.com.auCommon questions teams ask before deciding whether to use this domain in agent workflows.
coolrom.com.au currently scores 37/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.