context safety score
A score of 40/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
social engineering
Site hosts a large-scale adult escort and sex services classified ad platform (kanesex.com) with thousands of active listings. Many listings use urgent, manipulative language ('call now', 'don't think about it', 'limited time') and false scarcity tactics to pressure users into phone/WhatsApp contact with unknown individuals. Multiple listings claim photos are '100% real' while urging immediate action — classic social engineering manipulation. (location: page.html:lines 640-2700, page-text.txt throughout premium listings)
social engineering
Multiple webcam/online service listings (Live Webcam Sex category) request payment via IBAN, Iris, Revolut, and PaysafeCard prepaid vouchers. The PaysafeCard listings explicitly state 'από περίπτερο' (from kiosk), directing victims toward anonymous, non-reversible payment methods. This is a common advance-fee and payment-harvesting social engineering pattern. (location: page-text.txt:lines 1117-1135, 1937-1983)
credential harvesting
The site collects user registration (email, username, password) and messaging data via forms at /user/register and /user/login. The platform is a Greek adult classifieds site with no apparent strong identity verification, making it a potential credential harvesting vector. User-submitted contact data (phone numbers, WhatsApp, Viber, Skype, email) are harvested in plaintext within listing bodies. (location: page.html:lines 96-97, page-text.txt:lines 3211-3214 (skype email exposed in listing))
hidden content
A conditionally-loaded external JavaScript resource is injected only when cookies are accepted: '//jb7hvckszone.com/aas/r45d/vki/1756805/tghr.js'. This obfuscated third-party script is loaded from a suspicious domain (jb7hvckszone.com) outside the main site domain and is hidden behind a cookie consent gate. This pattern is used to evade static scanners and inject malicious payloads only for consenting users. (location: page-hidden.txt:lines 62-74)
malicious redirect
A hidden JavaScript block conditionally loads an external script from 'jb7hvckszone.com' — a domain with an obfuscated, random-looking name ('jb7hvckszone') not associated with any known legitimate ad or analytics provider. The script path '/aas/r45d/vki/1756805/tghr.js' contains obfuscated path components consistent with malvertising or redirector infrastructure. This script could redirect users or load additional payloads. (location: page-hidden.txt:lines 65-66)
social engineering
Several listings are attributed to an anonymous account ('Anonymous (offline)') posting multiple distinct escort ads under different female personas (e.g., Eirini at line 884, Kamila at line 1130). This indicates fake persona creation to deceive users about the identity of the service provider, a social engineering deception tactic. (location: page.html:lines 884, 1130)
social engineering
Third-party ad network 'realsrv.com' (a.realsrv.com/ads.js and syndication.realsrv.com) is used for display advertising throughout the page. realsrv.com is associated with adult ad networks that have been linked to malvertising campaigns. Ads are loaded via script injection and iframe fallbacks across multiple ad zones (4099860, 3622569, 538869, 3634629). (location: page.html:lines 333-342, 624-633, and additional ad zones in page-text.txt)
curl https://api.brin.sh/domain/kanesex.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
kanesex.com currently scores 40/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.