On 2026-10-01, ajazzpro.shop returned an HTTP 502 response during a recorded check, indicating a server-side error at that time. The domain was first observed on 2026-09-25, giving a short window between initial sighting and the later HTTP check.
Recorded Evidence
A PhishDestroy internal listing for ajazzpro.shop was present as of the latest review. On 2026-09-25, a PageSpeed evaluation reported a performance score of 88, and an SSL scan on the same day identified Let's Encrypt / YE1 as the certificate issuer. VirusTotal, checked on 2026-09-27, showed 10 detections out of 91 scanners. OTX, reviewed on 2026-09-27, recorded 4 pulses for the domain.
Interpretation
The sources referenced, including PhishDestroy, VirusTotal, and OTX, each provide observations tied to specific dates, so their findings may reflect different states for ajazzpro.shop. The HTTP 502 response on 2026-10-01 is a point-in-time result and does not indicate the domain's availability or behavior at other times. Comparing these records requires attention to the timing of each source's observation, as the domain's status could change between checks.
Recommended Actions
Preserve the collected evidence for ajazzpro.shop, including the HTTP, PhishDestroy, VirusTotal, and OTX records, to support future comparisons. When conducting subsequent reviews of ajazzpro.shop, document the exact date and source of each new observation. Refrain from submitting sensitive information to the domain until its status is clarified through further analysis.
スキャナーに関する注記:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='ajazzpro.shop', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS 非アクティブreason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation不明Probe Inconclusive20%2026-10-11 01:32:17 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-09-27 22:03:14 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-27 22:03:14 UTC → 2026-09-30 16:14:55 UTC · 66.19hmidpoint estimate ≈ 2026-09-29 07:09:04 UTC · precision low · basis bounded
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 ajazzpro.shop· checked Sep 25, 2026
88
Needs Work
Performance
FCP
2.86s
First Contentful Paint
LCP
2.86s
Largest Contentful Paint
CLS
0.004
Cumulative Layout Shift
TBT
137ms
Total Blocking Time
SI
3.89s
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-28 10:02:41 UTC
Domain state transitioned from alive to dead.
VirusTotal Detections Update2026-09-25 06:25:29 UTC
VirusTotal scanner detections updated from 9 to 10. Added scanner alerts: Forcepoint ThreatSeeker, SOCRadar. Resolved alerts: CRDF.
Threat First Observed2026-09-25 02:24:48 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 162.222.90.59.
脅威対応 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.
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.
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.
