context safety score
A score of 43/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
cloaking
Page loads content in transparent or zero-size iframe overlay
js obfuscation
JavaScript uses Function constructor for runtime code generation
hidden content
Massive injection of gambling/casino promotional content (Palmerbet, Jokaroom, Elitebet, Slotomania, Chasebet, Casino Rocket, Pointsbet, Spin Samurai, Stellar Spins, BSB007, Boombet, 7Bit, PlayCroco, Goldbet, JeetCity, Ignition Casino) embedded within the RichRelevance legitimate business homepage. Content spans thousands of lines of SEO link-farm text hidden from normal page view, exploiting the domain's authority for search ranking manipulation. (location: page-text.txt lines 836-2031)
hidden content
Pornographic Turkish-language keywords injected at the bottom of the page content: 'sikiş hikayeleri', 'xnxx', 'sex hikayeleri', 'rokettube', 'olgun porno', 'bakire porno', 'türkçe porno', 'milf porno', 'sex izle', 'brazzers', 'hd porno'. These appear twice in the extracted text, indicating hidden spam link injection on a compromised site. (location: page-text.txt lines 2186-2229)
social engineering
Multiple injected gambling brand sections (Elitebet, Palmerbet, Chasebet, PlayCroco, etc.) repeatedly prompt users to perform login actions, sign up, and download apps, using persuasive language about 'secure login', 'easy registration', and 'welcome bonuses'. These sections are designed to drive traffic to third-party gambling platforms from a trusted corporate domain. (location: page-text.txt lines 836-2031)
brand impersonation
The legitimate RichRelevance B2B enterprise personalization brand and trusted domain (6881 days old) is being exploited to host and lend credibility to unrelated third-party gambling and casino brands including Elitebet, Palmerbet, Jokaroom, Casino Rocket, Boombet, PlayCroco, Goldbet, JeetCity, and others. Recent blog posts in German and Turkish about 'Chicken Road Casino' and '1King Casino' further confirm ongoing brand abuse. (location: page-text.txt footer section lines 2143-2153, and embedded casino content lines 836-2031)
obfuscated code
Inline CSS in page.html contains systematically mangled CSS selectors and property values throughout: spaces inserted into class names ('. ite-logo', '# croll-header', '.po t-entry', '.mile tone'), property values corrupted ('tran parent' instead of 'transparent', ' olid' instead of 'solid', 'fir t-child' instead of 'first-child', 'ance tor' instead of 'ancestor'). This pattern across thousands of lines of CSS suggests either a site compromise artifact or deliberate obfuscation to hinder analysis. (location: page.html lines 850-3076)
hidden content
WordPress blog posts published under the RichRelevance domain promoting German-language Chicken Road Casino content (April 14, 2025) and Turkish-language 1King Casino content (March 15, 2025) are surfaced in the site footer as 'Recent Posts', indicating the attacker has persistent write access to publish gambling SEO content via the CMS. (location: page-text.txt lines 2143-2153)
curl https://api.brin.sh/domain/richrelevance.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
richrelevance.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.