context safety score
A score of 35/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
js obfuscation
JavaScript uses Function constructor for runtime code generation
malicious redirect
Multiple banner ads link to external gambling/betting sites (btp-02.com, lula.ws, zxx.bet, onetop.ws, qb-78.com, ld-01.com, tting.site) with affiliate/agent codes embedded in URLs (e.g., agentCode=1111, agentCode=2580, agentCode=2222), redirecting users to unrelated third-party gambling platforms. (location: page.html lines 574-594, pop-up modal line 717)
social engineering
An auto-opening modal popup (shown on page load unless a cookie is set) aggressively promotes external gambling sites with a prominent red call-to-action button labeled 'Go to Nicelink' and instructs users to bookmark nicelink51.com/nicelink22.com as the site's 'real-time address', creating urgency and dependency on these external redirector domains. (location: page.html lines 692-711, 714-741)
malicious redirect
The site's Twitter/SNS icon links and footer social links point to 'nicelink22.com' (not Twitter/X) — a domain that masquerades as a social platform link but redirects to an unrelated site, likely a link-shortener or affiliate redirect hub. (location: page.html lines 138, 206, 619)
brand impersonation
The nicelink22.com domain is styled as a Twitter link (using fa-twitter icon, title='트위터') but is not affiliated with Twitter/X, deceiving users into thinking they are visiting an official social media profile. (location: page.html lines 138, 206, 619)
hidden content
A popup div with id='pop-content' is set to display:none in HTML but is programmatically injected into a modal overlay on page load via JavaScript. Its gambling advertisement content and redirect buttons are not directly visible in the DOM without JS execution, obscuring its true purpose from static analysis. (location: page.html lines 714-741)
credential harvesting
A login form collects username (id='login_id') and password (id='login_pw') fields via a JavaScript-driven overlay. No visible form action URL is present — credentials are likely submitted via AJAX to an undisclosed endpoint, preventing inspection of where credentials are sent. (location: page.html lines 219-238)
social engineering
Users are told that bookmark functionality requires login, creating a false necessity to register/authenticate ('북마크 기능을 위해서 로그인이 필요합니다'). This pressures users into creating accounts on a site of unclear legitimacy. (location: page.html lines 223-225)
malicious redirect
Navigation menu icons for the '버즈툰' (bz) section load images from the external domain ionppn1.net, a third-party image CDN not affiliated with the site. All banner ad images are also served from this domain, which could be used for tracking pixel techniques or substituted with malicious content. (location: page.html lines 561-563, 574-594, 717)
curl https://api.brin.sh/domain/wftoon204.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
wftoon204.com currently scores 35/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.