amcan.shop was checked by VirusTotal on 2026-10-07, providing a dated scan result for this domain. The domain was also listed in the PhishDestroy internal catalogue, which is a publisher-owned listing.
Recorded Evidence
VirusTotal scanned amcan.shop on 2026-10-07 and found zero detections out of 92 scanners. OTX referenced the domain in four pulses as of 2026-10-07. The SSL certificate was issued by Let's Encrypt / YE1 and was scanned on 2026-10-07. The domain was first observed on 2026-10-06.
Interpretation
These records from VirusTotal, OTX, and PhishDestroy document how amcan.shop was referenced by automated scanners and community sources on their respective dates. The SSL certificate observation provides additional technical context for the domain's configuration.
Recommended Actions
Preserve the VirusTotal scan results and OTX pulse references for amcan.shop as source records. Compare future observations and catalogue listings to these records to monitor any changes in how the domain is referenced.
スキャナーに関する注記:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='amcan.shop', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("SOC
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS 非アクティブreason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation不明Probe Inconclusive20%2026-10-11 10:08:00 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-09 01:48:53 UTClast content: 2026-10-08 22:00:25 UTCcurrent episode first observed: 2026-10-09 20:20:42 UTCobserved RIP window: 2026-10-09 01:48:53 UTC → 2026-10-09 20:20:42 UTC · 18.53hmidpoint estimate ≈ 2026-10-09 11:04:47 UTC · precision medium · basis bounded
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.
使用技術 · 1 identified
H
HTTP/3
Miscellaneous
HTTP/3 is the third major version of the Hypertext Transfer Protocol used to exchange information on the World Wide Web.
Google PageSpeed Insights — mobile performance audit of amcan.shop· checked Oct 7, 2026
77
Needs Work
Performance
FCP
2.86s
First Contentful Paint
LCP
4.95s
Largest Contentful Paint
CLS
0.006
Cumulative Layout Shift
TBT
71ms
Total Blocking Time
SI
2.86s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
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-06 21:59:36 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 195.96.130.197.
脅威対応 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
4 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.
