VirusTotal
10 / 91
“Amelia Activewear Shop | Amelia Activewear”
On 2026-10-01, ameliaactivewearhq.shop returned an HTTP status code of 301 during a recorded check. The same source set records a page title of "Amelia Activewear Shop | Amelia Activewear" on that date, and the domain was first observed on 2026-10-01.
VirusTotal, checked on 2026-09-29, reported 10 detections across 91 scanners. OTX was checked on 2026-10-01 and recorded 2 pulses, while the PhishDestroy internal listing was true on 2026-10-01. A urlscan report was available on 2026-10-01, and the target brand recorded was fakeshop.
The VirusTotal observation predates the HTTP, OTX, PhishDestroy, and urlscan records by two days, so the sources describe ameliaactivewearhq.shop at different moments. That gap limits direct comparison, because each named source captures only its own dated snapshot rather than a continuous history.
Retain the dated records for ameliaactivewearhq.shop, including the HTTP status, VirusTotal result, OTX pulses, and PhishDestroy listing, so later checks can be compared against them. When new observations arrive, compare them with these exact dates rather than treating any single snapshot as current. Avoid submitting sensitive information to ameliaactivewearhq.shop while the review continues.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
CaddyScanner note: redirect: raw=redirect_301; http=301; via=http_proxy; location=https://ameliaactivewearhq.shop/; server=Caddy
braelyn.ns.cloudflare.comcolin.ns.cloudflare.comLocation describes the IP network.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of ameliaactivewearhq.shop · checked Oct 1, 2026
195.96.130.244. 10 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive