On 2026-10-01, akofg.shop returned an HTTP 301 status according to a recorded observation. The same domain was first observed on 2026-09-28, and a PhishDestroy internal listing was recorded for it.
Recorded Evidence
The HTTP check on 2026-10-01 recorded status 301 for akofg.shop, while the first observation of the domain is dated 2026-09-28. A PageSpeed check on 2026-09-28 returned a performance score of 61. VirusTotal recorded 10 detections across 91 scanners on 2026-10-01. OTX recorded 4 pulses on 2026-10-01, and the PhishDestroy internal listing is recorded as true.
Interpretation
The HTTP, VirusTotal and OTX observations all carry the same 2026-10-01 date, so they describe one point in time rather than a sequence. The 2026-09-28 first observation and PageSpeed score predate those checks, which means comparisons across the two dates involve different measurement types. The PhishDestroy listing and the OTX pulses are separate recorded sources, and neither duplicates the other.
Recommended Actions
Reviewers should retain the dated records for akofg.shop so later checks can be compared against the 2026-09-28 and 2026-10-01 observations. Any subsequent HTTP, VirusTotal or OTX result should be captured with its own date before conclusions are drawn. During review, avoid submitting credentials or other sensitive information to akofg.shop.
探测与规避分析
隐身和流量分配检查
尚未扫描目前尚未记录到爬虫与浏览器之间的差异
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
尚未扫描
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='akofg.shop', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("SOC
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 10:09:43 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-11 01:42:45 UTClast content: 2026-10-11 01:42:45 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 akofg.shop· checked Sep 28, 2026
61
Needs Work
Performance
FCP
2.98s
First Contentful Paint
LCP
11.94s
Largest Contentful Paint
CLS
0.011
Cumulative Layout Shift
TBT
278ms
Total Blocking Time
SI
4.8s
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-29 00:59:37 UTC
VirusTotal scanner detections updated from 8 to 10. Added scanner alerts: Forcepoint ThreatSeeker, LevelBlue.
VirusTotal Detections Update2026-09-28 06:31:11 UTC
VirusTotal scanner detections updated from 7 to 8. Added scanner alerts: SOCRadar.
Threat First Observed2026-09-28 01:26:53 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 195.96.130.197.
威胁响应 Pipeline
发现
Analysis
Monitoring
13 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.
