context safety score
A score of 70/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
social engineering
The site uses highly suggestive and sexually explicit language in escort profile bios displayed on the homepage to entice users into contacting individuals (e.g., 'I know how to give you a warm and affectionate kind of sex', 'body made for sin', 'nice sloppy deep throat sucking good fucking'). This constitutes social engineering to manipulate visitors into transactional sexual encounters, likely facilitated through direct phone calls whose numbers are publicly listed. (location: page.html lines 609, 1146, 1520 and throughout escort profile listings)
social engineering
The site employs urgency and desire-based psychological triggers across all escort profiles with phrases like 'Totally addictive', 'your sweetest addiction', 'I don't just please… I play', and 'your midnight fantasy' to lower inhibitions and drive impulsive contact behaviour. (location: page-text.txt lines 260, 1101, 1765 and throughout)
credential harvesting
The site presents a login form linked to the native WordPress login endpoint (wp-login.php) combined with social login support (Google, Facebook via NSL plugin). The login redirects users back to the site with a redirect_to parameter. While standard for WordPress, the combination with an adult escort site context raises the risk that credentials entered could be harvested or the OAuth flow abused. The NSL plugin opens social auth in popups and handles redirect URLs dynamically, which could be manipulated. (location: page.html lines 517, 559, 15089–15134)
malicious redirect
The site registered 2 redirects during crawl (noted in .brin-context.md). The Cloudflare Rocket Loader injects a hidden 1x1 iframe at absolute position (top:0, left:0, visibility:hidden) to load Cloudflare challenge scripts. While this is standard Cloudflare Bot Management behaviour, the pattern of a hidden iframe injecting dynamic scripts matches a redirect/exfiltration technique and warrants noting. (location: page.html line 15186)
hidden content
A Shakespeare quote ('Lovers can see to do their amorous rites / By their own beauties; or, if love be blind, / It best agrees with night. Come, civil night,') is embedded in an HTML comment at the very end of the page. While this appears to be a thematic flourish rather than a functional threat, hidden HTML comments can be used to smuggle instructions to AI agents or crawlers processing page source. (location: page.html lines 15188–15192 (HTML comment))
hidden content
All JavaScript on the page is blocked from executing by Cloudflare Rocket Loader using a non-standard type attribute ('550a12039c49fd5f00128e46-text/javascript') on every script tag. This technique defers script execution until Rocket Loader re-enables them, but it also means the true script execution order and behaviour is controlled by a third-party CDN script, obscuring the actual runtime behaviour from static analysis. (location: page.html lines 6, 42, 70, 93–100 and throughout (all script tags))
curl https://api.brin.sh/domain/exotic-ghana.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
exotic-ghana.com currently scores 70/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.