context safety score
A score of 24/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
cloaking
Page checks user-agent for bot/crawler strings to serve different content
cloaking
Page conditionally redirects based on referrer or user-agent
malicious redirect
Two obfuscated third-party scripts are dynamically injected at page load from suspicious domains 'robustpsychology.com' and 'relievedjoke.com'. Both use encoded path segments with random-looking strings, are loaded asynchronously with 'no-referrer-when-downgrade' referrer policy, and are injected via self-invoking functions with randomised variable names (gyhl, omorof). These are hallmarks of adware/malvertising script loaders that can redirect users or serve malicious ads. (location: page.html:1796-1817)
malicious redirect
A third-party script is loaded from 'news-sodahe.com' with tracking parameters (id, p1-p4 sub parameters). The domain 'news-sodahe.com' is a known push-notification spam / unwanted redirect network used to harvest notification subscriptions and redirect users to scam/malware pages. (location: page.html:1819)
malicious redirect
'Live Cams' navigation link uses an affiliate redirect through 'go.xlirdr.com' with a hardcoded campaign ID and hashed user ID, routing users through an uncontrolled third-party redirect domain before reaching the destination. The domain 'xlirdr.com' acts as a redirect intermediary that can be changed to route to malicious destinations. (location: page.html:185,208)
obfuscated code
Two script injection blocks at the bottom of the page use self-invoking functions with randomised parameter names (gyhl, omorof) and heavily obfuscated URL paths with forward-slash escaping ('\/'). The scripts are dynamically appended to the DOM to evade static analysis. Source domains 'robustpsychology.com' and 'relievedjoke.com' are not legitimate analytics or CDN providers. (location: page.html:1796-1817)
hidden content
CSS class 'ocultar-en-escritorio' (Spanish: 'hide on desktop') sets max-height:0, font-size:0, and display:none on desktop viewports while revealing content on mobile (max-width 640px/479px). Similarly 'hide-desktop' class is set to display:none with font-size:0 and max-height:0 at the document level. These responsive-hiding patterns can be used to serve hidden content to mobile users or specific user-agents that is not visible to desktop scanners. (location: page.html:54,222-223)
social engineering
The age verification gate is bypassed for any user-agent matching /bot|crawl|spider|slurp|google/i, meaning search crawlers and potentially AI agents that identify themselves as bots will never see the age gate. The 'exit' button redirects to google.com rather than a genuine exit, which is a deceptive UX dark pattern designed to keep users on the site. (location: page.html:97)
social engineering
Video title in user-uploaded content 'big ass solo girl Masturbation wet pussy watch more www.vipxcams.com' embeds a third-party domain (vipxcams.com) directly in the video title as an advertisement/redirect lure, using the site's own content listing as a vector to drive traffic to an external cam site. (location: page.html:1484-1494)
curl https://api.brin.sh/domain/xporn.tvCommon questions teams ask before deciding whether to use this domain in agent workflows.
xporn.tv currently scores 24/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.