context safety score
A score of 30/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
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
js obfuscation
JavaScript uses Function constructor for runtime code generation
js obfuscation
Obfuscated document.write with encoded content
prompt injection
Hidden HTML element contains AI-targeting instructions
malicious redirect
Back-button hijacking script manipulates browser history by pushing 10 states and intercepts the popstate event to redirect users to https://backbutton.videobaba.xyz/back-button-script/public/getit.php when they attempt to navigate back. This is a well-known dark pattern used on adult/ad-fraud sites to trap users. (location: page.html:106)
malicious redirect
Dynamically injected iframe on mobile viewports loads content from https://go.xlviiirdr.com/i with obfuscated tracking parameters including a long userId hash. The domain name (xlviiirdr) appears intentionally obfuscated (Roman numerals: 48-redirect) and targets mobile users specifically via JavaScript DOM injection rather than static HTML. (location: page.html:1368)
hidden content
Analytics/tracking script loaded from a third-party domain https://stats.indianpornempire.com/js/script.js using a data-domain attribute targeting antarvasna3.com. This is a covert analytics beacon that tracks user behavior and sends data to an external network. (location: page.html:104)
hidden content
Client hint delegation header (delegate-ch) sends detailed browser fingerprinting data (sec-ch-ua, sec-ch-ua-bitness, sec-ch-ua-arch, sec-ch-ua-model, sec-ch-ua-platform, sec-ch-ua-platform-version, sec-ch-ua-full-version-list, sec-ch-ua-mobile) to tsyndicate.com on every request, enabling covert user profiling without explicit disclosure. (location: page.html:108)
obfuscated code
Custom base64 encode/decode functions (b2a, a2b, b64e, b64d) are defined and used throughout the page to encode ad insertion code and data attributes. Ad content is stored as base64 in data-code attributes and decoded at runtime via b64d(), obscuring the actual injected content from static analysis. (location: page.html:1469-1471)
social engineering
Email newsletter signup form (Antarvasna Email Club) collects user email addresses with a consent checkbox. The form submits to Elementor's backend. The privacy assurance ('your information will remain confidential, never shared') is unverifiable and typical of mailing list harvesting on adult content sites. (location: page.html:1213-1242)
malicious redirect
Affiliate tracking link to keitaro.dsccash.com uses a cloaked redirect URL with tracking parameters (source, source_id, affid, oid). Keitaro is a known affiliate tracker platform; the link is labeled 'Indian Live Sex' and 'Live Cams' in navigation menus, routing users through an external monetization chain. (location: page.html:406,515,1289)
curl https://api.brin.sh/domain/antarvasna3.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
antarvasna3.com currently scores 30/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.