context safety score
A score of 23/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
malicious redirect
script/meta redirect patterns detected in page source
social engineering
The page fabricates a fictitious academic authority ('김수진 박사' / Dr. Kim Su-jin) described as a sex-education scholar and content director with 12+ years of experience, complete with a fake last-updated date (2025-08-24, future-dated relative to domain age of 121 days). This manufactured credibility is used to legitimise an unlicensed adult content aggregator and drive user trust and engagement. (location: page.html:1229-1233, page-text.txt:979-983)
social engineering
Fabricated user reviews with vulgar usernames ('왕부랄', '귀두맛', '딸맨') are presented as genuine UGC testimonials to build social proof and encourage continued site use. The reviews are clearly astroturfed to manipulate user perception of site quality and safety. (location: page.html:1396-1411, page-text.txt:1147-1161)
social engineering
The site explicitly markets itself as a replacement ('대체 사이트') for a well-known Korean adult site '야동코리아', with fabricated traffic statistics ('70% 이상') and a comparison table designed to divert users from a competitor. This siphoning strategy exploits brand recognition of an established platform to capture its user base. (location: page.html:1250-1261, page-text.txt:1000-1066)
malicious redirect
All banner ad clicks are routed through an internal click-tracking redirect endpoint (/click?id=N&url=<encoded-destination>) before forwarding users to third-party gambling and betting sites (bet38join.com, kcasinojoin.com, kplay.casino, bella00.com, smtb-0038.com, etc.). The encoded URLs obscure the true destination from users and tracking systems, and all destinations appear to be unlicensed offshore gambling operations. (location: page.html:709-878)
malicious redirect
The page's canonical URL and og:url metadata point to yadongtv86.com, while the page is actually served from yadongtv84.com. Assets (CSS, JS, images) are also loaded from yadongtv86.com. This domain mismatch indicates the site operates across multiple numerically-sequenced domains to evade blocklists and maintain persistence after domain takedowns, as explicitly described in the site's own FAQ. (location: page.html:33-44, page.html:76)
hidden content
Multiple popup elements are initialised with class 'hidden' and are only revealed via JavaScript after a 100ms delay based on cookie state. The popup banners link to external gambling/betting sites. This technique hides ad content from static crawlers and security scanners while still displaying it to real users. (location: page.html:274-307, page.html:1564-1694)
hidden content
A hidden 1x1 invisible iframe is dynamically injected into the document body via an immediately-invoked function expression (IIFE). The iframe executes a script that sets Cloudflare challenge parameters and loads an external script from '/cdn-cgi/challenge-platform/scripts/jsd/main.js'. While potentially legitimate Cloudflare Bot Management, the injection pattern (hidden iframe writing inline script) is also a known technique for covert script execution. (location: page.html:2021, page-text.txt:1662)
social engineering
The site instructs users to bookmark a landing page (xn--2q1bp1r9rce9ecnf02r.org) and follow a Telegram channel (t.me/redbdo) to receive updated domain addresses when the current domain is blocked. This is a deliberate evasion-persistence strategy that recruits users as a distribution channel for blocked-site circumvention, normalising access to potentially illegal content. (location: page.html:1333-1334, page-text.txt:1083-1085)
malicious redirect
Footer links for company information, FAQ, privacy policy, terms, and copyright policy all point to yadongtv86.com rather than the current domain yadongtv84.com. Users clicking these links are silently redirected to a different domain, which could be used for SEO manipulation or to serve different content to users vs. crawlers. (location: page.html:1479-1504)
hidden content
Third-party analytics tracking is loaded from a self-hosted Matomo instance at yagrotomo.com (not the site's own domain), enabling cross-domain visitor tracking without clear user disclosure. All page views and link clicks are sent to this external domain, which could be used to build behavioural profiles of visitors across multiple adult/gambling sites in the same network. (location: page.html:56-69)
curl https://api.brin.sh/domain/yadongtv84.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
yadongtv84.com currently scores 23/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.