context safety score
A score of 68/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
malicious redirect
Exit button links to https://www.google.com — a classic deceptive redirect pattern used to give the impression of a safe exit while the site has already loaded tracking/ad scripts. The 'Exit' anchor uses Google as a decoy destination rather than navigating away from harmful content. (location: page.html:747)
social engineering
Age verification gate uses manipulative language requiring users to click 'Enter' and accept Terms and Conditions and Privacy Policy/GDPR before viewing content. The gate creates a false sense of legal consent and is a common pattern on adult content sites to coerce agreement to unfavorable terms. (location: page.html:743-756)
malicious redirect
Two third-party ad scripts loaded from a.pemsrv.com: one is a popunder script (popunder1000.js) and one is an interstitial script (fp-interstitial.js). Popunder ads are an aggressive advertising tactic that open new browser windows/tabs without user consent and are frequently used to deliver malware, phishing pages, or unwanted content. The ad zone IDs 4647574 and 4631580 are configured with ad_new_tab=true and trigger methods. (location: page.html:796-818)
social engineering
The site pre-fills a newsletter field with 'Guest' via JavaScript, potentially priming users for newsletter subscription without explicit opt-in awareness. (location: page.html:788-790)
hidden content
Unrendered Smarty/template syntax present in a style block: '{if $tpl_settings.name == \'escort_rainbow\'}' — indicates server-side template code was not processed and leaked into the HTML. While low risk on its own, it reveals the underlying CMS framework (Flynax) and template structure, which could assist targeted attacks. (location: page.html:476-498)
curl https://api.brin.sh/domain/escortmod.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
escortmod.com currently scores 68/100 with a caution verdict and medium 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.