context safety score
A score of 37/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
phishing
1 deceptive links where visible host does not match destination host
cloaking
Page loads content in transparent or zero-size iframe overlay
malicious redirect
A third-party script is dynamically injected from the suspicious domain 'pristine-creative.com' using a heavily obfuscated path ('/cYDB9.6lb/2p5mlqSUW_QX9CN/T/MqwxNWz/g/4gMbSY0J1/Mhz/AJ3gOPD/gtyc'). The script is loaded asynchronously with no-referrer-when-downgrade policy and contains logic to ignore specific CSS classes ('.dddnp', '.ddddnp'), suggesting selective behavioral targeting. This pattern is consistent with malvertising or traffic-redirecting scripts. (location: page.html:77-86)
obfuscated code
The injected script from 'pristine-creative.com' uses a self-invoking anonymous function with obfuscated URL path components, dynamic script element creation, and DOM insertion techniques to evade static detection. The URL path appears randomly generated to bypass blocklists. (location: page.html:77-86 / page-text.txt:5-14)
malicious redirect
An affiliate tracking link routes through 'go.mavrtracktor.com' with a long opaque campaignId and userId hash. This is a third-party ad/traffic broker with a tracker-style domain name. The link is presented in the navigation menu as 'ライブ配信中' (Live Streaming), potentially deceiving users into clicking a redirector. (location: page.html:99)
hidden content
An iframe sourced from 'creative.mavrtracktor.com' is embedded with class 'ddddnp', which matches one of the CSS class selectors explicitly excluded from the pristine-creative.com script's 'ignoreTo' list. This suggests the iframe is intentionally exempted from certain script processing, indicating coordinated hidden/selective-rendering behavior. The iframe loads adult webcam widget content silently. (location: page.html:1744)
social engineering
The site presents adult doujinshi (fan-made explicit manga) content using popular well-known anime/game IP names (Fate/Grand Order, Pokemon, Blue Archive, One Piece, etc.) as category labels to attract users searching for legitimate content about those franchises, then exposes them to explicit material. This constitutes brand/IP exploitation for audience manipulation. (location: page.html:223-343, page.html:984-1739)
obfuscated code
Third-party ad scripts are loaded from 'js.waqool.com' using numeric zone IDs in the path (a90001728.js, a90001729.js). These are ad network scripts from an external domain with no transparency about their payload, representing a supply-chain risk vector for malvertising. (location: page.html:976-980)
curl https://api.brin.sh/domain/ddd-smart.netCommon questions teams ask before deciding whether to use this domain in agent workflows.
ddd-smart.net currently scores 37/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.