Security engines reporting a detection: 12. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
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.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not yet scannedNo crawler-versus-browser difference has been recorded yet
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Stored cloaking flag
Not yet scanned
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
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.
Threat Response Pipeline
Discovery
Analysis
Monitoring
7 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
amazon.discoveryloft.com detected and queued for full analysis
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.
3 evidence signal groups linked0 reports recordedUnverified
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · amazon.discoveryloft.com
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Same registrar: GoDaddy6
Registered through the same registrar. A registrar serves millions of unrelated customers, so this groups reports rather than proving a link.
(US)
