context safety score
A score of 45/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
brand impersonation
The domain tripadvisor.in mimics the well-known TripAdvisor brand (tripadvisor.com) using a country-code TLD (.in for India) rather than the legitimate .com domain. This is a classic brand impersonation pattern used to deceive users into believing they are on the official TripAdvisor site. (location: domain: tripadvisor.in)
malicious redirect
The page immediately loads an external script from ct.captcha-delivery.com and configures a challenge via geo.captcha-delivery.com. These are not TripAdvisor infrastructure. The entire page content is a bot/human detection gate that redirects visitors through a third-party captcha delivery network, which can be used to fingerprint, track, or selectively redirect users based on their profile. (location: page.html: <script src="https://ct.captcha-delivery.com/i.js">)
credential harvesting
A session cookie value is embedded directly in the page's JavaScript payload and sent to geo.captcha-delivery.com. The cookie string ('uuwkAgAnZUQnzNqVBdnGr6EylvAV11MZ6qx9c~...') is exposed in plaintext in the HTML, and the captcha challenge infrastructure at captcha-delivery.com can harvest session/browser fingerprint data from visitors before any actual content is served. (location: page.html: dd.cookie value passed to geo.captcha-delivery.com)
obfuscated code
The page contains no legitimate TripAdvisor content. Instead, it serves only an obfuscated JavaScript challenge object (variable 'dd') with encoded fields including a hash ('hsh'), encrypted token ('e'), and session cookie. The animation CSS hides the 'Please enable JS' message for 1.5 seconds to mask the redirect mechanics from casual inspection. (location: page.html: <style>#cmsg{animation: A 1.5s;}@keyframes A{...}</style> and dd object)
social engineering
The visible message 'Please enable JS and disable any ad blocker' social-engineers users into disabling browser security protections (ad blockers often also block malicious scripts and trackers), making them more vulnerable to subsequent tracking or malicious payloads delivered after the captcha gate. (location: page.html / page-text.txt: 'Please enable JS and disable any ad blocker')
curl https://api.brin.sh/domain/tripadvisor.inCommon questions teams ask before deciding whether to use this domain in agent workflows.
tripadvisor.in currently scores 45/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.