ajmstudio.shop returned HTTP status 502 in a check recorded on 2026-10-01, indicating the server could not supply a valid response at that moment. The same domain was first observed on 2026-09-25, and a PhishDestroy internal listing was also recorded for it.
Recorded Evidence
VirusTotal recorded 11 detections across 91 scanners on 2026-09-27. OTX listed 4 pulses on 2026-09-27. The HTTP check on 2026-10-01 returned status 502, while the first observation of the domain was logged on 2026-09-25. PageSpeed recorded a performance score of 64 on 2026-09-25, and the SSL scan on that date named Let's Encrypt / YE1 as the issuer.
Interpretation
The VirusTotal and OTX figures come from separate sources measured on the same calendar date, so they should be read as independent observations rather than a combined score. The HTTP 502 response describes only the reply captured during that check, not the domain's content or behavior at other times. Because the first observation and the PageSpeed and SSL scans share a date, they may reflect the same early window, while the later HTTP and OTX checks fall on different dates and cannot be treated as a trend.
Recommended Actions
Preserve the PhishDestroy internal listing, the VirusTotal record, and the OTX record for ajmstudio.shop so future checks can be compared against them. Compare the recorded HTTP status against a fresh request to see whether the response changes. Review the VirusTotal and OTX records separately rather than merging their figures into one judgment. Recheck the domain and keep each source's output distinct for later comparison.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observation不明Probe Inconclusive20%2026-10-11 01:32:02 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-09-25 02:36: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.
Last analyzed First positive detection Previous stored snapshot: 11 detections
alphaMountain.ai
BitDefender
CRDF
CyRadar
ESET
G-Data
Gridinsoft
LevelBlue
ネットクラフト
SOCRadar
Webroot
サイトパフォーマンス分析
Google PageSpeed Insights — mobile performance audit of ajmstudio.shop· checked Sep 25, 2026
64
Needs Work
Performance
FCP
2.86s
First Contentful Paint
LCP
10.28s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
201ms
Total Blocking Time
SI
4.71s
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-27 14:11:47 UTC
VirusTotal scanner detections updated from 10 to 11. Added scanner alerts: CyRadar.
Domain Status Transition2026-09-25 10:54:44 UTC
Domain state transitioned from alive to dead.
VirusTotal Detections Update2026-09-25 06:22:52 UTC
VirusTotal scanner detections updated from 9 to 10. Added scanner alerts: SOCRadar.
Threat First Observed2026-09-25 02:36:22 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 188.244.119.61.
脅威対応 Pipeline
ディスカバリー
Analysis
Notifications
Monitoring
16 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.
PDF notice generated Notice text archived (650 chars)
Abuse notice text as sent to the provider
Policy Violations:
Illegal Activities: Active phishing operation targeting victims
Fraud & Deception: Impersonation of legitimate services
Identity Theft: Collection of credentials under false pretenses
Applicable Laws (Unknown):
International Anti-Cybercrime Regulations
Budapest Convention on Cybercrime
Universal Fraud Prevention Laws
Phishing activities violate international cybercrime conventions and Unknown's domestic fraud laws.
Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
