VirusTotal
7 / 91
ReportInterpretation & limits
Engine detections from this stored analysis. Vendors and collection times may differ from other sources.
“generalcart.shop”
Assessment based on the stored source evidence below. Review sources →
These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.
7 / 91
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
provider verdict: malicious
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
5 community references
ReportCommunity publication references, not a vendor verdict or evidence of a common operator.
stored report
Report A preserved page image documents what the collector received; a capture is not a safety verdict.
Analysis completed
ReportThis is the recorded automated analysis. Completion alone is not a safety verdict.
Checked; no threat flag recorded
ReportA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
Stored narrative · generated . Provider checks below retain their own observation dates.
On 2026-10-01, generalcart.shop was found in a PhishDestroy internal listing during a blocklist check, marking it as recorded in a publisher-owned catalogue. The domain was first observed on 2026-08-25, providing a reference point for subsequent evidence collection.
OTX documented five pulses for generalcart.shop on 2026-08-31. VirusTotal reported 7 detections out of 91 scanners for the domain on 2026-08-31. The SSL certificate, issued by Google Trust Services / WE1, was scanned on 2026-08-26. PageSpeed recorded a performance score of 68 for the domain on 2026-08-25.
The evidence from PhishDestroy, OTX, VirusTotal, SSL, and PageSpeed was collected on different dates, which allows for comparison of how the domain was recorded at various points in time. Each source provides a distinct perspective, and the sequence of dated records enables a reader to track changes or consistencies without inferring causality or status from any single observation.
Retain all dated evidence for generalcart.shop, including the PhishDestroy listing and scan results, to facilitate future comparisons. When reviewing new findings, record the exact date and source for each observation. Avoid submitting sensitive information to generalcart.shop during ongoing review and evidence collection.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Scanner note: timeout: raw=timeout; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='generalcart.shop', port=80): Read timed out. (read timeout=7)
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
Edge-IP reputation is not attributed to this domain.
elly.ns.cloudflare.comroute1.mx.cloudflare.netpriority 10route2.mx.cloudflare.netpriority 26route3.mx.cloudflare.netpriority 76Location describes the IP network.
c240fcafd92a109e0a6040937224b3f391683bade3fd965a8aff0b75ea63d29fSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of generalcart.shop · checked Aug 25, 2026
104.21.59.234.13 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive