context safety score
A score of 44/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
js obfuscation
JavaScript uses Function constructor for runtime code generation
obfuscated code
Admiral bootstrap activator script uses multiple layers of percent-encoding and nested decodeURI() calls to conceal its variable names and behavior. The decoded variable '%25%36%31dmi%25%372%25%361%256c' resolves to 'admiral' and '%67%256fo%67%6c%256%35%74ag' resolves to 'googletag'. This obfuscation is designed to evade static analysis and WAF/CSP inspection. (location: page.html line 221-223, id='admiral-activator-js')
malicious redirect
The obfuscated Admiral activator script dynamically injects a script from 'dogbedscentral.com' — a domain entirely unrelated to familyhandyman.com. This cross-domain script injection pattern is consistent with adware/malvertising supply-chain abuse, where a third-party ad-recovery vendor loads code from an unvetted external domain that could serve malicious payloads or redirect users. (location: page.html line 221, src='https://dogbedscentral.com/static/r7n77afka7ix.min.js')
hidden content
The page suppresses console.log and console.info by overriding them with empty no-op functions. This conceals runtime JavaScript activity and errors from developer tools inspection, a technique commonly used to hide malicious or privacy-invasive behavior from security researchers and site auditors. (location: page.html lines 195-197, inline script block in <head>)
obfuscated code
A second Admiral script block (lines 222) reads localStorage using an obfuscated key decoded from 'g%65%25%374%254%39%25%374%256%35%25%36d' and injects the retrieved values as Google Ad Manager targeting parameters via googletag.pubads().setTargeting(). The obfuscated localStorage key access and ad targeting manipulation from persisted local data is a vector for stored cross-site data exfiltration or persistent ad fraud. (location: page.html line 222, second block inside id='admiral-activator-js')
curl https://api.brin.sh/domain/familyhandyman.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
familyhandyman.com currently scores 44/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.