amazon.discoveryloft.com was observed with a VirusTotal record dated 2026-10-12, which documents both detections and scanner counts. The domain also received a PageSpeed performance score on 2026-10-13, providing technical insight into its infrastructure.
Recorded Evidence
VirusTotal recorded 12 detections out of 92 total scanners for amazon.discoveryloft.com on 2026-10-12. On 2026-10-13, the domain was listed on two external blocklists: OpenPhish and Phishunt. The PageSpeed performance score for the domain was measured at 59 on 2026-10-13. PhishDestroy internally listed the domain, and the first observation date was 2026-10-13.
Interpretation
The VirusTotal record contains a measurement of detection activity from multiple scanners, offering a broad perspective on the domain's status at the time of observation. External blocklist entries from OpenPhish and Phishunt provide additional context about its presence in public security intelligence sources. PhishDestroy's internal listing is another recorded indicator, while the PageSpeed performance score documents technical characteristics for comparison.
Recommended Actions
For amazon.discoveryloft.com, it is important to preserve the VirusTotal detection record and external blocklist entries for ongoing reference. Comparing future observations from VirusTotal and blocklists against these records can help track changes. Retaining the PageSpeed performance score may assist in monitoring technical infrastructure developments.
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-13 10:00:15 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-13 10:00:15 UTClast content: 2026-10-13 10:00:15 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.
Google PageSpeed Insights — mobile performance audit of amazon.discoveryloft.com· checked Oct 13, 2026
59
Needs Work
Performance
FCP
4.92s
First Contentful Paint
LCP
7.19s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
186ms
Total Blocking Time
SI
5.94s
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-12 23:34:45 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 64.233.162.121.
脅威対応 Pipeline
ディスカバリー
Analysis
Monitoring
10 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)
