The domain aperolshop.shop was first recorded on 2026-10-07 with a PhishDestroy internal listing and an OTX pulse reference. VirusTotal’s scan on 2026-10-04 showed zero detections out of 92 participating engines.
Recorded Evidence
VirusTotal checked aperolshop.shop on 2026-10-04, finding zero detections from 92 scanners. OTX included the domain in two pulses on 2026-10-07. The PhishDestroy internal listing also flagged aperolshop.shop on 2026-10-07.
Interpretation
These dated observations reflect independent monitoring snapshots rather than a continuous timeline. VirusTotal’s result indicates no scanner flagged the domain at the time of its scan. OTX’s two pulses represent community-sourced threat intelligence references. The PhishDestroy listing documents the domain’s inclusion in a curated catalogue.
Recommended Actions
Retain the VirusTotal scan results, OTX pulse references, and the PhishDestroy internal listing as baseline records for aperolshop.shop. Compare future VirusTotal scans, OTX pulses, and PhishDestroy listings to identify any changes in status or new intelligence.
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.
Latest HTTP observation不明Probe Inconclusive20%2026-10-11 10:11:06 UTC
RDAP registration不明
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.
Threat First Observed2026-10-07 03:43:03 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 46.245.239.66.
脅威対応 Pipeline
ディスカバリー
Analysis
Monitoring
9 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.
OTX Community References
2 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
2026年10月7日
Brand Impersonation
Impersonation of Fakeshop
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
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)
