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
cloaking
Page loads content in transparent or zero-size iframe overlay
hidden content
Multiple navigation menu items are commented out in HTML, including a 'Sex Dating' link to external redirect domain s.zlinkr.com and an 'AI JERK OFF' link to tsyndicate.com direct API. These commented-out links with active affiliate/tracking parameters suggest A/B testing of deceptive navigation labels targeting users and AI agents crawling the page. (location: page-hidden.txt:9,11 / page.html:5996,6003)
hidden content
A full-width iframe (1323x110px) served from a.adtng.com is embedded in a hidden/commented section and also rendered live on the page. The ad network adtng.com is known for aggressive adult ad delivery including pop-unders and malvertising chains. (location: page-hidden.txt:15 / page.html:6025)
malicious redirect
Navigation menu item labeled 'Sex Dating' links directly to https://s.zlinkr.com/d.php?z=4982798 — a redirect/traffic broker URL that routes visitors through an opaque redirect chain. The destination is unknown and may lead to phishing, scam, or malware landing pages. (location: page.html:5996)
malicious redirect
Navigation menu item labeled 'Sex Games' links to https://a.adtng.com/get/10013195 — a direct ad-network tracker URL rather than an actual games page, routing visitors through an ad network redirect chain with no transparency about the final destination. (location: page.html:5999)
hidden content
The page uses 'delegate-ch' meta HTTP header to forward extensive browser client hints (UA string, platform, architecture, bitness, model, full version list, mobile status) to tsyndicate.com — a third-party ad network. This leaks detailed device fingerprint data to a third party without user consent or disclosure, and enables cross-site tracking and profiling. (location: page.html:17)
hidden content
The page exposes the visitor's full IPv6 address (var CLIENT_IP) and country code (var COUNTRY_CODE) in inline JavaScript on the page, making this data accessible to any third-party scripts loaded on the page, including ad networks. (location: page.html:20-21)
social engineering
Navigation item labeled 'AI SEX CHAT🔥' with emoji is designed to attract clicks, and the commented-out variant linked directly to tsyndicate.com's direct API endpoint — an ad/affiliate redirect URL — rather than a legitimate AI chat service. This uses urgency and novelty framing to drive traffic to ad networks. (location: page-text.txt:96 / page.html:6003)
hidden content
Yandex Metrika tracking pixel is loaded via a hidden 1x1 image positioned at left:-9999px (off-screen), constituting a hidden tracking element. While Yandex analytics is common, the off-screen placement is consistent with covert tracking patterns. (location: page-text.txt:2541)
curl https://api.brin.sh/domain/analdin.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
analdin.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.