The domain ajmora.shop returned an HTTP status code 502 during a check on 2026-10-01, indicating a specific server response at that time. Additional monitoring sources recorded separate security and performance observations for this domain.
Recorded Evidence
On 2026-10-01, an HTTP check for ajmora.shop recorded a 502 status code. VirusTotal, checked on 2026-09-27, reported 16 detections out of 91 scanners. OTX, also checked on 2026-09-27, listed 4 pulses for the domain. A PageSpeed check on 2026-09-25 recorded a performance score of 66, and an SSL scan on the same date identified the issuer as Let's Encrypt / YE1. The domain was first observed on 2026-09-25, and a PhishDestroy internal listing is present.
Interpretation
These recorded observations provide a sequence of technical and security-related checks on ajmora.shop, each from a specific source and date. The HTTP 502 status reflects only the server's response at the time of that check, while the VirusTotal and OTX results represent independent security observations. The presence of a PhishDestroy internal listing, along with performance and SSL records, offers additional context for future reference.
Recommended Actions
For ajmora.shop, retain the HTTP response record, VirusTotal detection results, and OTX pulse count for future monitoring. Compare each source's findings against their own future observations to track any changes. Keep the PhishDestroy internal listing and performance data available for reference in subsequent reviews.
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:37:48 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: 16 detections
alphaMountain.ai
BitDefender
Chong Lua Dao
CRDF
CyRadar
ESET
Forcepoint ThreatSeeker
G-Data
Gridinsoft
LevelBlue
Lionic
ネットクラフト
SOCRadar
ソフォス
VIPRE
Webroot
サイトパフォーマンス分析
Google PageSpeed Insights — mobile performance audit of ajmora.shop· checked Sep 25, 2026
66
Needs Work
Performance
FCP
2.89s
First Contentful Paint
LCP
11.86s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
114ms
Total Blocking Time
SI
4.75s
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.
Domain Status Transition2026-09-25 10:56:10 UTC
Domain state transitioned from alive to dead.
VirusTotal Detections Update2026-09-25 06:22:49 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 188.244.119.61.
脅威対応 Pipeline
ディスカバリー
Analysis
Notifications
Monitoring
15 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.
