context safety score
A score of 57/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
phishing
1 deceptive links where visible host does not match destination host
malicious redirect
The page is served from a WPEngine staging/shadow domain (ccemulticultur.wpenginepowered.com) that impersonates the official Utah government site (multicultural.utah.gov). The canonical URL and most resource links point to multicultural.utah.gov, but the actual serving domain and several internal navigation links (pillar cards, footer links, contact-us anchor, partner-with-us, equity-in-utah) redirect users to ccemulticultur.wpenginepowered.com instead of the official .gov domain. This domain substitution means users clicking those links stay on the unofficial shadow domain rather than reaching the authentic government site. (location: page.html lines 279-309, footer links: ccemulticultur.wpenginepowered.com/about-us/#contact-us, ccemulticultur.wpenginepowered.com/equity-in-utah/, ccemulticultur.wpenginepowered.com/partner-with-us/)
brand impersonation
The page fully replicates the visual identity, branding, content, logo, navigation, and official Utah state government styling of multicultural.utah.gov while being served from the non-governmental domain ccemulticultur.wpenginepowered.com. The HTML canonical tag points to multicultural.utah.gov, RSS/API feeds reference multicultural.utah.gov, yet the actual serving domain is a WPEngine-hosted clone. This constitutes brand impersonation of a U.S. state government agency, potentially deceiving users and AI agents into treating the shadow domain as authoritative. (location: metadata.json (domain: ccemulticultur.wpenginepowered.com), page.html line 46 (canonical: https://multicultural.utah.gov/), page.html lines 9-13 (all feed/API alternates point to multicultural.utah.gov))
hidden content
Two entire page sections are hidden from all viewport sizes using combined CSS classes x-hide-lg x-hide-md x-hide-sm x-hide-xl x-hide-xs, rendering them invisible to every user on any device. These sections (e4323-e74, e4323-e82) contain duplicate mission/vision content. While this may be a responsive design artifact, sections hidden across all breakpoints are invisible to human users but present to crawlers and AI agents, contributing to the flagged hidden content ratio of 0.06. (location: page.html lines 258-268 (e4323-e74 section), page.html line 268 (e4323-e82 section) — CSS classes: x-hide-lg x-hide-md x-hide-sm x-hide-xl x-hide-xs)
hidden content
A text element with classes x-hide-lg x-hide-md x-hide-sm x-hide-xl x-hide-xs (e4323-e44, e4323-e54, e4323-e61, e4323-e70, e4323-e80, e4323-e94) appears multiple times hiding headline text from all viewport sizes. These are invisible to all users on all screen sizes, creating content visible only to scrapers or AI agents. (location: page.html lines 235, 241, 247, 253, 259, 269 — multiple elements with all x-hide-* classes combined)
curl https://api.brin.sh/domain/ccemulticultur.wpenginepowered.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
ccemulticultur.wpenginepowered.com currently scores 57/100 with a caution 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.