On 2026-10-02, applecrossgalleryonline.shop was recorded in the VirusTotal source with 12 detections across 91 scanners. The same date carries a PhishDestroy internal listing for the domain, and the source records give 2026-10-02 as the first observation date.
Recorded Evidence
VirusTotal reported 12 detections out of 91 scanners for applecrossgalleryonline.shop on 2026-10-02. PhishDestroy included the domain in its internal listing on 2026-10-02. The source records state that applecrossgalleryonline.shop was first observed on 2026-10-02. The domain resolved to IP address 46.245.239.183 in the recorded evidence.
Interpretation
The VirusTotal and PhishDestroy entries describe separate observations of applecrossgalleryonline.shop, each with its own scope and method. Because the recorded dates coincide, the entries can be read side by side, but the detection count and the listing flag are different kinds of records and should not be merged into a single measure. The shared first observation date marks the earliest point in the available chronology.
Recommended Actions
Preserve the VirusTotal and PhishDestroy records for applecrossgalleryonline.shop as separate items, and keep the original context of each entry. When reviewing applecrossgalleryonline.shop, compare the source records individually rather than combining their metrics. Retain the recorded first observation date alongside those entries so later reviews can trace the chronology.
DOM Analysisanalyzed 2026年10月9日score 88/1001 brand signal
Submitted URLhttp://applecrossgalleryonline.shop/
Favicon Hash
ICANN OVERSIGHT
认证和 RAA 背景
Registrar accreditation and DNS abuse obligations
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.
Accreditation is a contract, not a safety certification.
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observation内容在线Ordinary HTTP content served90%2026-10-11 10:07:44 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-11 10:07:44 UTClast content: 2026-10-11 10:07:44 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
Domain Status Transition2026-10-09 01:47:36 UTC
Domain state transitioned from dead to alive.
Domain Status Transition2026-10-03 10:14:52 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-10-02 19:21:23 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 46.245.239.183.
威胁响应 Pipeline
发现
Analysis
Monitoring
12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
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.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
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.
(US)
