context safety score
A score of 24/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
credential harvesting
Login form collects mobile number and password via POST with no visible action URL (action=""), suggesting credentials are submitted to the same page for server-side capture. The site appears to be a standalone credential collection page with registration and other navigation links commented out, leaving only the login form functional. (location: page.html:92-120)
phishing
The page presents a bare login interface with no meaningful branding, no terms of service, no privacy policy, and no contextual information about what service is being accessed. Registration and other navigation links are commented out, leaving only credential capture functionality. This is consistent with a phishing page designed solely to harvest credentials. (location: page.html:85-121)
social engineering
The page prominently displays a WhatsApp support contact number (9274920435) labeled as 'RP Whatsapp Support' with 'RP=Reward Points', a common social engineering tactic used in Indian financial scam operations to establish legitimacy and create a direct communication channel with victims for further manipulation. (location: page.html:63-64)
brand impersonation
The site uses generic Metronic Shop UI template metadata (description, keywords, author set to 'keenthemes') while presenting itself as 'SDPAY', indicating the site was built on a cloned/stolen UI template. The meta description and keywords are never updated from template defaults, suggesting a hastily assembled fraudulent site. (location: page.html:9-11)
hidden content
Multiple navigation and registration links are commented out in the HTML (register link, login link, remember-me checkbox, sign-up link), stripping the page of all functionality except credential submission. This deliberate removal of legitimate site structure is consistent with a purpose-built credential harvesting page. (location: page.html:66-71, 89, 109-116, 119)
curl https://api.brin.sh/domain/sdpay.co.inCommon questions teams ask before deciding whether to use this domain in agent workflows.
sdpay.co.in currently scores 24/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.