activelyblackshop.shop returned HTTP 301 on 2026-10-01, a redirect response recorded during an HTTP check. The same domain was first observed on 2026-09-09, according to the earliest recorded observation date in this evidence set.
Recorded Evidence
VirusTotal recorded 10 detections across 89 scanners on 2026-09-18. OTX listed 4 pulses on 2026-09-10. The domain appeared in the PhishDestroy internal listing, and a PageSpeed check on 2026-09-09 produced a performance score of 71. An SSL scan on 2026-09-09 identified the issuer as Let's Encrypt / YE2, while the IP address 195.96.130.237 resolved to the US under HMZ Web Hosting Co.
Interpretation
The HTTP, VirusTotal, OTX, PageSpeed and SSL records were captured on separate dates, so they describe distinct snapshots rather than one combined measurement. The redirect response on 2026-10-01 and the first observation on 2026-09-09 bracket a period in which the domain was already known to the listed sources. Because the detection count and pulse count come from different platforms and dates, they should be read as independent signals rather than a single score.
Recommended Actions
Preserve the PhishDestroy internal listing, the VirusTotal record and the OTX pulses as separate source records for activelyblackshop.shop. Compare the HTTP response record against the first-observed entry when reviewing the domain's timeline. Retain the PageSpeed and SSL scan outputs alongside those records so each dated observation remains traceable.
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-11 10:20:22 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 10:20:22 UTClast content: 2026-10-11 10:20:22 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.
使用技術 · 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 activelyblackshop.shop· checked Sep 9, 2026
71
Needs Work
Performance
FCP
3.03s
First Contentful Paint
LCP
4.75s
Largest Contentful Paint
CLS
0.019
Cumulative Layout Shift
TBT
214ms
Total Blocking Time
SI
4.62s
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.
VirusTotal Detections Update2026-09-10 21:14:52 UTC
VirusTotal scanner detections updated from 9 to 10. Added scanner alerts: Gridinsoft.
VirusTotal Detections Update2026-09-10 04:39:14 UTC
VirusTotal scanner detections updated from 8 to 9. Added scanner alerts: SOCRadar.
VirusTotal Detections Update2026-09-09 13:56:16 UTC
VirusTotal scanner detections updated from 5 to 8. Added scanner alerts: BitDefender, Forcepoint ThreatSeeker, G-Data.
Threat First Observed2026-09-09 11:47:47 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 195.96.130.237.
脅威対応 Pipeline
ディスカバリー
Analysis
Monitoring
14 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.
Web Archive
Preserved in ウェイバック・マシン — historical evidence archived
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.
