VirusTotal
2 / 94
ReportInterpretation & limits
Engine detections from this stored analysis. Vendors and collection times may differ from other sources.
“Even geduld...”
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.
2 / 94
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
checked — no detections recorded
ReportAlerts refer to the preserved scan. They do not describe the current state of the site.
checked — no match recorded
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
no community references
ReportCommunity publication references, not a vendor verdict or evidence of a common operator.
provider verdict: suspicious
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
stored report
View stored capture ↗ ReportA 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.
0 external matches
DetailsA 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.
The domain bagworkoor.digital is associated with a generic phishing operation and has a high threat score of 85/100. It has been flagged as malicious by 2 out of 95 security vendors, including Gridinsoft and SOCRadar, and is listed on 3 public blocklists. Google Safe Browsing has not flagged this domain, indicating some level of evasion in detection.
Registered with PDR Ltd. d/b/a PublicDomainRegistry.com, the domain was created on March 16, 2026, and first detected on March 17, 2026. The hosting IP address is 188.114.97.3. The site status remains unknown, suggesting it may be operational or recently spun up.
Given the high threat score and detection status, block the domain at the perimeter and submit a report to the registrar's abuse desk for further investigation.
What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.
These checks have no retained result. This does not mean they passed or that a scan is running.
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.
june.ns.cloudflare.comnikon.ns.cloudflare.comLocation describes the IP network.
Saved 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 bagworkoor.digital · checked Mar 17, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Scanner note: unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='bagworkoor.digital', port=80): Max retries exceeded with url: / (Caused by NewConnectionEr
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown→dns_inactive
dns_nxdomain
dns_inactive→Unknown
probe_inconclusive
Unknown→dns_inactive
dns_nxdomain
dns_inactive→Unknown
probe_inconclusive
Unknown→dns_inactive
dns_nxdomain
dns_inactive→Unknown
probe_inconclusive
Unknown→dns_inactive
dns_nxdomain
dns_inactive→Unknown
probe_inconclusive
Unknown→dns_inactive
dns_nxdomain
dns_inactive→Unknown
origin_unreachable · http_5xx
Unknown→dns_inactive
dns_nxdomain
dns_inactive→Unknown
origin_unreachable · http_5xx
Unknown→dns_inactive
dns_nxdomain
dns_inactive→Unknown
origin_unreachable · http_5xx
dns_inactive
dns_nxdomain
10 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.
Reported by 1 community member, first seen Mar 17, 2026
PD-20260317-A150E8 Recipient: abuse@publicdomainregistry.com Registrar: PublicDomainRegistry (PDR Ltd.) (India) Policy Violations: Explicit policy to immediately suspend domains used for phishing, 419 scams, identity fraud, malware distribution without prior notice Applicable Laws: IT Act 2000 §§66C–66D (identity theft, cheating by personation), Indian Penal Code §420 / Bharatiya Nyaya Sanhita §318 (fraud)
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