context safety score
A score of 38/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
malicious redirect
script/meta redirect patterns detected in page source
brand impersonation
The domain medicoveronline.com impersonates the legitimate Medicover Hospitals brand (medicoverhospitals.in). It uses the official Medicover name, logo, branding, contact details (info@medicoverhospitals.in, +91 40 6833 4455), and content to appear as an official Medicover property while operating on an unauthorized lookalike domain. (location: medicoveronline.com — page.html, entire page)
malicious redirect
JavaScript embedded in the <head> section silently redirects all visitors to https://www.medicoverhospitals.in via window.location.href inside the Google Analytics gtag script block. This covert redirect is hidden alongside legitimate analytics code, obscuring its purpose from casual inspection. (location: page.html:38 — window.location.href = "https://www.medicoverhospitals.in";)
malicious redirect
The vaccination tracking form posts user-supplied Transaction ID (UVID) and mobile number to https://medicoveronline.com/track/valid.php and then unconditionally follows a server-controlled URL returned in the JSON response via window.location.replace(rresult.url). This allows the server to redirect the user to any arbitrary URL after harvesting their data. (location: page.html:902-907 — $.post to /track/valid.php then window.location.replace(rresult.url))
credential harvesting
A form collects users' Transaction ID / UVID and mobile phone number under the guise of tracking vaccination details, then transmits them to a server-side endpoint (https://medicoveronline.com/track/valid.php). The operator of this unauthorized lookalike domain can capture and misuse this sensitive medical/identity data. (location: page.html:260-276 — vaccination tracking form with UVID and mobile inputs)
social engineering
The site exploits the trusted Medicover healthcare brand and COVID-19 vaccination context to gain user trust. It encourages users to submit personal identifiers (mobile number and UVID) by presenting a believable 'Track your vaccination details' interface with options to 'Download invoice', 'Appointment details', and 'Download E-pass'. (location: page.html:251-252 — vaccination tracking section)
hidden content
The robots meta tag is set to 'noindex,nofollow', preventing search engines from indexing or crawling the page. This is atypical for a legitimate hospital landing page and suggests the operator intentionally hides the site from search engine scrutiny while still targeting direct/referred visitors. (location: page.html:10 — <meta name="robots" content="noindex,nofollow">)
phishing
The site is a fully rendered phishing page mimicking Medicover Hospitals India. It replicates official branding, services descriptions, testimonials, contact information, and social media links to deceive visitors into believing they are on a legitimate Medicover property before harvesting personal/medical information via the vaccination tracking form. (location: medicoveronline.com — page.html, full page)
curl https://api.brin.sh/domain/medicoveronline.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
medicoveronline.com currently scores 38/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.