context safety score
A score of 47/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
The scanned URL is https://avsubthai.me but all canonical links, internal navigation, CSS, JS, images, and structured data point exclusively to a different domain: ww.avsubthai.men. The og:url and canonical href both reference ww.avsubthai.men, indicating the .me domain silently redirects/proxies visitors to the .men domain without disclosure. This is a classic domain-shadowing/redirect pattern used to evade blocklists. (location: page.html:12-13 (canonical and og:url), page.html:75 (nav link to wwww.avsubthai.me — note extra 'w'))
malicious redirect
A nav menu item links to https://wwww.avsubthai.me/ (four w's — a typosquat variant of the site itself). This could redirect users to an attacker-controlled domain distinct from both avsubthai.me and ww.avsubthai.men, exploiting visual similarity. (location: page.html:75 (menu-item-232 href='https://wwww.avsubthai.me/'))
hidden content
The Histats.com analytics tracker is injected via dynamically created script tag in the footer, loading external JS from //s10.histats.com/js15_as.js. This third-party script executes with full page privileges and can exfiltrate visitor data (IP, browser fingerprint, referrer) to histats.com, an analytics service with no user disclosure on the page. (location: page.html:963-971 (footer Histats script block))
hidden content
A speculation-rules prefetch block is embedded as a script tag with type='speculationrules', instructing the browser to speculatively prefetch internal site links. While not directly malicious, combined with the domain redirect pattern this could pre-load content from the ww.avsubthai.men domain into the browser cache without explicit user navigation. (location: page.html:976-978)
brand impersonation
The site uses the registered trademark-adjacent branding of well-known adult content platform 'Pornhub' via its WordPress theme named 'backpornbunny26', and the page title/meta closely mimics the branding style of legitimate Japanese AV subtitle aggregators. The .me TLD site acts as a front for the .men TLD site, creating a confusing multi-domain identity that could be used to impersonate or traffic-jack users seeking a known site. (location: page.html:19 (theme CSS), page.html:47 (body class wp-theme-backpornbunny26), metadata.json (domain: avsubthai.me))
curl https://api.brin.sh/domain/avsubthai.meCommon questions teams ask before deciding whether to use this domain in agent workflows.
avsubthai.me currently scores 47/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.