VirusTotal
5 / 89
ReportInterpretation & limits
Engine detections from this stored analysis. Vendors and collection times may differ from other sources.
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.
5 / 89
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
3 community references
ReportCommunity publication references, not a vendor verdict or evidence of a common operator.
provider verdict: clean
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
stored 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.
disneystoremall.com returned HTTP status 502 in an HTTP check dated 2026-10-01, a recorded response that describes only that check. The domain was first observed on 2026-09-05, and its registration date is 2026-09-01.
The domain was registered on 2026-09-01 with registrar Dynadot Inc. First observation of disneystoremall.com occurred on 2026-09-05. An HTTP check on 2026-10-01 recorded status 502. VirusTotal, checked on 2026-09-17, reported 5 detections across 89 scanners. OTX, checked on 2026-09-17, listed 3 pulses. The PhishDestroy internal catalogue included a listing for this domain, and the blocklist check was performed on 2026-10-01.
The HTTP 502 response is a single dated record and does not describe the domain's content or its availability outside that check. The VirusTotal and OTX figures come from separate sources checked on the same date, and each metric reflects only its own scanner or pulse collection. The registration, first-observation, and HTTP dates span a short window, but the gaps between them do not by themselves show a change in the domain's state.
Preserve the HTTP check record for disneystoremall.com and the PhishDestroy catalogue entry as separate source records. Compare the VirusTotal detection record with the OTX pulse record in separate reviews rather than merging them. Retain the registration and first-observation records for disneystoremall.com so later checks can be compared against them.
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='disneystoremall.com', port=80): Max retries exceeded with url: / (Caused by NewConnectionE
ns2.dyna-ns.netLocation describes the IP network.
11 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.
1 community report
CategoryPHISHING
The PhishFort Detection System has flagged this as a domain threat, classified as null. Threat detected at 2026-09-04T17:11:33.195Z.
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