context safety score
A score of 43/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
cloaking
Page conditionally redirects based on referrer or user-agent
hidden content
The footer-container div is initialized with 'display: none' and only made visible conditionally via JavaScript after a 1-second delay. The footer contains legal disclosures, age restrictions, and payment processor information that is hidden from initial page render and from non-JS crawlers/agents. (location: page.html:716 — <div id="footer-container" style="... display: none">)
hidden content
The twitter:site meta tag is set to '@googleapis', falsely associating this adult gaming site with Google APIs on Twitter/X card previews. This is a misattribution that could mislead social media scrapers and AI agents evaluating the page's legitimacy. (location: page.html:3 — <meta name="twitter:site" content="@googleapis" />)
malicious redirect
Dynamic domain rotation logic generates up to 50 algorithmically computed subdomains across base domains 'adult-chess.com' and 'acgamers.com', rotating every 14 days. Scripts, stylesheets, and game build assets are dynamically fetched from whichever subdomain responds first. This pattern is consistent with domain-fronting or CDN-evasion techniques used to serve content from domains that may bypass blocklists or reputation filters. (location: page.html:68-106 — baseDomains, domainRotationDays, generateSubdomain(), getWorkingUrl())
hidden content
Client IP address is silently harvested via a HEAD request to the page's own URL reading the 'X-Client-IP' response header, stored in window.analyticsData.ipAddress before any user interaction or consent. This is covert data collection not disclosed in visible page content. (location: page.html:35-46 — window.analyticsData.ipReadyPromise fetch('HEAD'))
hidden content
Sentry error monitoring is configured to route telemetry to a custom self-hosted endpoint 'sentry.chickgoddess.com' rather than the official Sentry service. Stack traces and exception data from user sessions are sent to a third-party domain with no disclosed privacy implications to the user. (location: page.html:324-343 — Sentry.init({ dsn: 'https://...@sentry.chickgoddess.com/77' }))
curl https://api.brin.sh/domain/everlustinglife.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
everlustinglife.com currently scores 43/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.