context safety score
A score of 47/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
phishing
1 deceptive links where visible host does not match destination host
malicious redirect
A script dynamically loads JavaScript from '//a.medfoodsafety.com/oauth2' — a domain unrelated to iafd.com, disguised with a medical/food safety name. It uses an 'oauth2' endpoint path to appear legitimate, injects itself into the page DOM at runtime, and passes parameters including 'exctl' that reference site navigation elements (container-fluid, nav, navbar-nav), suggesting capability to manipulate or overlay page structure. This pattern is consistent with malvertising or supply-chain injection. (location: page.html:686-692 (script id='adn-152'))
hidden content
Email addresses are obfuscated using Cloudflare's email protection encoding (cdn-cgi/l/email-protection) and also via HTML entity encoding (mailto: etc.). While Cloudflare email obfuscation is a standard anti-scraping measure, the combination of multiple obfuscation methods on the same page warrants noting. The mailto link on line 185 uses full HTML entity encoding to hide the address from automated scanners. (location: page.html:157, 185, 517)
hidden content
An HTML comment in the footer embeds a legal disclaimer about 18 U.S.C. 2257 record-keeping exemptions in a hidden comment node, invisible to users but visible to crawlers and agents. While legally common for adult sites, it is delivered as a comment rather than visible text. (location: page.html:645)
malicious redirect
A JavaScript snippet enforces frame-busting: 'top.location!=self.location&&(top.location=self.location.href)'. This forcibly redirects any parent frame to the current page URL, which can be used to break out of security sandboxes or iframe-based analysis environments used by AI agents or security tools. (location: page.html:659)
curl https://api.brin.sh/domain/iafd.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
iafd.com 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.