VirusTotal
4 / 91
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 →
No stored capture is available for this domain.
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.
4 / 91
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.
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.
dial.shopping returned HTTP status 502 on 2026-10-01, the most recent technical check recorded in this evidence set. The domain was first observed on 2026-07-27, and the registrar recorded for it is Dynadot Inc.
PhishDestroy internally listed this domain in the evidence set. On 2026-08-15, VirusTotal reported 4 detections across 91 scanners, and OTX recorded 3 pulses on the same date. The HTTP check on 2026-10-01 returned status 502.
The VirusTotal and OTX records share the 2026-08-15 date, so those two observations can be compared directly with each other. The PhishDestroy listing and the 2026-10-01 HTTP result come from different points in the timeline, so they reflect separate moments rather than the same snapshot. Comparing the dated records shows how observations of dial.shopping differ across sources and times.
Retain each dated record for dial.shopping, including the VirusTotal, OTX, PhishDestroy and HTTP entries, so later checks can be compared against them. When new observations arrive, compare them with these existing dates and values rather than treating any single result as current. Avoid submitting sensitive or confidential information to dial.shopping while review is ongoing.
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='dial.shopping', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("
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.
5014.ns2.abovedomains.comLocation describes the IP network.
9 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