An HTTP request to aarkedesign.shop on 2026-10-01 returned status 502, a dated observation of a gateway error rather than a served page. The domain was first observed on 2026-09-09, and a PhishDestroy internal listing was recorded for it.
Recorded Evidence
VirusTotal reported 13 detections across 89 scanners on 2026-09-10, while OTX listed 4 pulses on the same date. The PhishDestroy internal listing was recorded, and the HTTP check on 2026-10-01 returned status 502. The SSL certificate was issued by Let's Encrypt / YE2 and scanned on 2026-09-09, and the PageSpeed performance score was 87 on 2026-09-09.
Interpretation
The PhishDestroy listing, OTX pulses and VirusTotal detections were collected on separate dates, so a reader should compare them as distinct dated observations rather than a single snapshot. The HTTP 502 from 2026-10-01 and the 2026-09-09 PageSpeed and SSL scans also fall on different dates, which limits direct comparison of those records.
Recommended Actions
Retain the dated records for aarkedesign.shop so later checks can be compared against the 2026-09-09 and 2026-10-01 observations. When reviewing aarkedesign.shop, avoid submitting passwords, payment details or other sensitive information, and compare each new observation with the retained evidence rather than relying on any single dated result.
探测与规避分析
隐身和流量分配检查
尚未扫描目前尚未记录到爬虫与浏览器之间的差异
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
尚未扫描
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='aarkedesign.shop', port=80): Max retries exceeded with url: / (Caused by NewConnectionErro
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:14:23 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-09-10 22:17:32 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-10 22:17:32 UTC → 2026-09-30 16:14:55 UTC · 473.96hmidpoint estimate ≈ 2026-09-20 19:16:13 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.
Last analyzed First positive detection Previous stored snapshot: 13 detections
alphaMountain.ai
BitDefender
CRDF
ESET
Emsisoft
Fortinet
G-Data
Gridinsoft
LevelBlue
Lionic
Netcraft
SOCRadar
Webroot
网站性能分析
Google PageSpeed Insights — mobile performance audit of aarkedesign.shop· checked Sep 9, 2026
87
Needs Work
Performance
FCP
2.86s
First Contentful Paint
LCP
2.86s
Largest Contentful Paint
CLS
0.006
Cumulative Layout Shift
TBT
197ms
Total Blocking Time
SI
3.42s
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:06:40 UTC
Domain state transitioned from alive to dead.
VirusTotal Detections Update2026-09-09 03:32:16 UTC
VirusTotal scanner detections updated from 12 to 13. Added scanner alerts: SOCRadar.
Threat First Observed2026-09-09 02:25:57 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 212.52.28.181.
威胁响应 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.
