context safety score
A score of 48/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
cloaking
Page loads content in transparent or zero-size iframe overlay
malicious redirect
Navigation menu contains a link labeled 'Free Live Sex' that redirects through a third-party tracking/affiliate URL (go.xxxijmp.com) with campaign and user ID parameters, disguising the true destination from users and AI agents processing the page. (location: page.html:483 - <a href="https://go.xxxijmp.com/easy?campaignId=a4e645fa094031148a3edb23c9a9933a0bb4aebc2a362e02625f5a4a467aa485&userId=1c1e6eeba8bbb3821a69bb888ec0b3b1919608a902b340f7c1988785c62bd672" target="_blank">Free Live Sex</a>)
hidden content
Meta referrer tag set to 'unsafe-url', causing the full URL (including path and query parameters) to be sent as the Referer header to all third-party resources. This leaks user browsing context and session information to ad networks and trackers. (location: page.html:15 - <meta name="referrer" content="unsafe-url">)
hidden content
ExoClick ad network scripts loaded from a.realsrv.com inject ads via AdProvider and ExoVideoSlider. The video slider is configured with frequency_period=0 and on_complete=repeat, meaning ads repeat indefinitely with no frequency cap, and branding is disabled (branding_enabled=0), making ad origin opaque to users. (location: page.html:1430-1449 - ExoClick ad scripts and ExoVideoSlider.init config)
hidden content
A Stripchat live-cam widget script is loaded from creative.mavrtracktor.com and mounted directly onto document.body with autoplay=all. The script can render interactive live-sex content anywhere in the page DOM without a contained element, and carries a persistent userId tracking token. (location: page.html:1468-1476 - StripchatSpot script and mount call)
hidden content
Third-party script loaded from cdn.fastmediaworld.my with a zone ID parameter. Domain uses a .my (Malaysia) ccTLD with a CDN-style subdomain; this script's purpose is not disclosed on the page and it executes with full page-level JavaScript access. (location: page.html:1467 - <script src="https://cdn.fastmediaworld.my/sdk/p/?zid=11438">)
hidden content
An iframe loading a Stripchat/mavrtracktor widget is embedded in the main content area with userId tracking token passed in the URL. The iframe has no sandbox attribute, granting it full access to cookies, popups, and navigation from within the embedded context. (location: page.html:1424 - <iframe src="https://creative.mavrtracktor.com/widgets/v4/Universal?...userId=1c1e6eeba8bbb3821a69bb888ec0b3b1919608a902b340f7c1988785c62bd672">)
curl https://api.brin.sh/domain/pornxxxfap.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
pornxxxfap.com currently scores 48/100 with a suspicious 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.