context safety score
A score of 32/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
tls connection failed
Could not establish TLS connection
encoded payload
suspicious base64-like blobs detected in page content
cloaking
Page loads content in transparent or zero-size iframe overlay
malicious redirect
Navigation link 'Ai Sex Chat' points to third-party ad network URL https://973007.xmlfeed.adplsr.com/?ss=1&domain=xtits.xxx embedded directly in site navigation, routing users to an external ad platform (adplsr.com) disguised as a site feature. (location: page.html:331 and page.html:419)
malicious redirect
'Busty Webcam' desktop nav link redirects to https://www.xtitscams.live/ — a separate domain with 'cams' and 'live' appended to the brand name, indicative of a traffic-harvesting or scam webcam site. (location: page.html:380-383)
malicious redirect
'Busty Webcam' mobile nav link uses a different redirect URL (https://rpwmct.com/?siteId=wl3&cobrandId=259434...) with unresolved affiliate placeholder {SUBAFFID}, routing through an opaque tracker domain rather than the domain shown in the desktop version. (location: page.html:450-455)
malicious redirect
'SEX GAMES' nav link redirects to https://a.adtng.com/get/10013195 — a known adult ad network tracker URL disguised as site navigation content. (location: page.html:385-388)
malicious redirect
'Sex Dating' desktop nav link redirects to https://s.zlinkr.com/d.php?z=4982790 and mobile uses https://s.zlinkc.com/d.php?z=4982790 — short-link redirect chains through zlinkr.com/zlinkc.com traffic broker domains. (location: page.html:390-391 and page.html:462)
hidden content
Dozens of category list items use class 'hidden' to render content invisible in the DOM without user interaction. While this is a common UI pattern, the volume (100+ hidden items) and the inclusion of sensitive categories may be used to inflate SEO signals or hide content from scanners. (location: page.html:602-1267 (class='item hidden' entries))
hidden content
An ad iframe (adtng.com, width=1323, height=110) is fully commented out in HTML but remains present in the source, preserving the ad integration code invisibly for potential future reactivation or to evade content scanners. (location: page.html:473-483)
social engineering
The site collects username, password, and email via a signup form while operating without valid TLS (TLS connected=false, cert_valid=false). Credentials submitted are transmitted without confirmed encryption, exposing users to interception. (location: page.html:140-187, metadata.json TLS fields)
credential harvesting
Login form POSTs credentials (username + password) to https://www.xtits.xxx/login/ over a connection where TLS is reported as not connected and certificate invalid, meaning credentials may be sent in plaintext or over an unverified channel. (location: page.html:108-130, metadata.json tls.connected=false)
hidden content
Client IP address (140.228.24.163) and country code (US) are exposed as JavaScript global variables in the page source, enabling fingerprinting of visitors by embedded third-party ad scripts. (location: page.html:28-29)
social engineering
Delegated client-hint headers (sec-ch-ua, sec-ch-ua-platform, sec-ch-ua-full-version-list, etc.) are delegated to tsyndicate.com via meta http-equiv='delegate-ch', allowing a third-party ad syndication domain to receive detailed browser and device fingerprinting data on every page load. (location: page.html:22)
curl https://api.brin.sh/domain/xtits.xxxCommon questions teams ask before deciding whether to use this domain in agent workflows.
xtits.xxx currently scores 32/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.