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
cloaking
Page conditionally redirects based on referrer or user-agent
js obfuscation
JavaScript uses Function constructor for runtime code generation
hidden content
A div with style='visibility:hidden;width:0px;height:0px' is present inside the header section containing multiple nested empty structural elements. This zero-size invisible container hides content from users while it remains in the DOM and is accessible to scrapers and AI agents. (location: page.html:510-573)
hidden content
Ad template containers are wrapped in a div with style='display:none' near the bottom of the body. These hidden divs contain ad script markup stored as HTML-encoded strings (e.g., adskeeper script encoded as <script>) and active script tags that load third-party ad code outside of visible page context. (location: page.html:2197-2255)
obfuscated code
The adenv() function constructs a base64-encoded parameter string 'ct=eyJwdHlwZSI6...' inline and appends device fingerprinting data (notification permission, service worker state, timezone, language, iOS detection) to an ad/tracking request. The encoded payload obscures the data being transmitted to third-party ad infrastructure. (location: page.html:88-94)
obfuscated code
The depscr/depscrs functions dynamically inject script elements from arbitrary HTML blobs with timed delays and include a 'debugger' statement. This pattern is used to defer and obfuscate ad injection, making static analysis of loaded scripts difficult. (location: page.html:96-114)
malicious redirect
All internal article and channel links use a quadruple-slash URL scheme (e.g., ////meesevats1.rssing.com/..., ////configuration1502.rssing.com/...). This non-standard href pattern resolves to protocol-relative URLs pointing to numerous unvetted third-party subdomains, and an AI agent following these links would be silently redirected to external third-party domains without explicit protocol indication. (location: page.html:924,934,1107,1117 (and many others throughout))
social engineering
The 'Trending Articles' and 'Top-Rated Articles' sections surface explicit adult content titles (e.g., 'Korean Sex Porn Videos: XXX Videos & Free Porn Movies' with 46 upvotes, Hindi-language explicit content) alongside benign educational content, normalizing mixed-trust content and potentially luring users or agents to follow links to unvetted external subdomains. (location: page.html:1107,1134; page-text.txt:588,616)
curl https://api.brin.sh/domain/rssing.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
rssing.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.