context safety score
A score of 44/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
brand impersonation
The domain polygon-rpc.com uses Polygon's brand name, logo (from chainlist.onerpc.com/assets/blockchains/polygon.svg), and styling to imply official Polygon network affiliation. The site is actually operated by Ankr (third-party), disclosed only in the footer as 'Made with ♥ by Ankr'. Users and AI agents querying Polygon RPC endpoints may mistake this for the official Polygon-operated RPC. (location: page.html: <title>, og:title, twitter:title, page header — 'Polygon RPC Endpoint: Fastest, free-est, and most reliable RPC endpoint')
social engineering
The page displays 'Action Required! This free RPC endpoint will stop working on Feb 16, 2026.' combined with 'Public access has been deprecated. Sign in to start using the endpoint for free.' These urgency and scarcity tactics pressure users into creating an Ankr account, using false urgency to drive account registration at ankr.com. (location: page.html: crossLink message and Freemium endpoint section — 'Action Required! This free RPC endpoint will stop working on Feb 16, 2026')
malicious redirect
The 'Sign in & copy endpoint' button on a Polygon-branded page redirects users to https://ankr.com/rpc/polygon — a different domain operated by Ankr. Users believe they are authenticating with a Polygon service but are redirected to and authenticate with a third-party platform. The displayed endpoint URL is truncated as 'https://polygo...' obscuring the full destination. (location: page.html: <a class='signInButton' href='https://ankr.com/rpc/polygon'>Sign in & copy endpoint</a>)
credential harvesting
The site gates RPC endpoint access behind a mandatory sign-in ('Public access has been deprecated. Sign in to start using the endpoint for free.'), funneling users into account creation at ankr.com under the pretext of a Polygon-branded service. This pattern harvests user credentials (email/OAuth) for Ankr's platform via a misleadingly branded Polygon page. (location: page.html: Freemium endpoint section — 'Public access has been deprecated. Sign in to start using the endpoint for free.')
curl https://api.brin.sh/domain/polygon-rpc.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
polygon-rpc.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.