adasa.shop returned HTTP status 502 in an HTTP check dated 2026-10-01, a recorded response for that request on that date. The same domain was first observed on 2026-09-09, according to the recorded first-observation timestamp.
Recorded Evidence
A VirusTotal check dated 2026-09-12 recorded 7 detections across 89 scanners. OTX recorded 4 pulses for adasa.shop in a check dated 2026-09-10. The publisher-owned PhishDestroy catalogue listed adasa.shop as an internal listing. An SSL scan dated 2026-09-09 recorded the issuer as Let's Encrypt / YE1. A PageSpeed check dated 2026-09-09 recorded a performance score of 60.
Interpretation
The VirusTotal detections, OTX pulses and PhishDestroy listing are separate source records, each with its own scope, and they should be read as recorded observations rather than a combined verdict. The HTTP 502 describes only the response captured on 2026-10-01 and does not establish what the domain served on other dates. The first-observation date and the later checks fall on different dates, so the chronology shows when records were collected, not a measured change in the domain.
Recommended Actions
Preserve the VirusTotal record, the OTX record and the PhishDestroy listing for adasa.shop so they can be compared later. Compare those source records against future checks of adasa.shop rather than relying on any single entry. Retain the HTTP check result for adasa.shop alongside the other records to document the response captured on that date.
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:14:50 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-09-15 22:17:47 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 adasa.shop· checked Sep 9, 2026
60
Needs Work
Performance
FCP
2.86s
First Contentful Paint
LCP
7.21s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
356ms
Total Blocking Time
SI
4.61s
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-10 22:17:32 UTC
Domain state transitioned from dead to alive.
Domain Status Transition2026-09-10 22:07:11 UTC
Domain state transitioned from alive to dead.
VirusTotal Detections Update2026-09-10 15:50:45 UTC
VirusTotal scanner detections updated from 2 to 3. Added scanner alerts: Gridinsoft.
VirusTotal Detections Update2026-09-10 04:38:49 UTC
VirusTotal scanner detections updated from 1 to 2. Added scanner alerts: SOCRadar.
VirusTotal Detections Update2026-09-09 13:32:46 UTC
VirusTotal scanner detections updated from 0 to 1. Added scanner alerts: ネットクラフト.
Threat First Observed2026-09-09 11:58:01 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 188.244.119.61.
脅威対応 Pipeline
ディスカバリー
Analysis
Notifications
Monitoring
19 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.
