On 2026-10-01, akuvia.shop produced an HTTP 301 status code during an automated check, indicating a recorded response from the domain at that time. The domain was first observed in this source set on 2026-09-28, providing a reference point for its earliest recorded activity.
Recorded Evidence
A VirusTotal scan on 2026-09-27 reported 7 detections out of 91 scanners for akuvia.shop. OTX recorded 4 pulses as of 2026-10-01. The domain appeared in the PhishDestroy internal listing, and a PageSpeed check on 2026-09-28 measured a performance score of 63.
Interpretation
These observations are drawn from separate sources, each documenting a specific aspect of akuvia.shop at different times. The HTTP status code reflects only the response captured on its check date, while VirusTotal and OTX provide independent security-related records. The presence in the PhishDestroy internal listing and the PageSpeed score further illustrate the variety of data collected about the domain.
Recommended Actions
For akuvia.shop, retain the PhishDestroy internal listing, VirusTotal scan results, and OTX pulse records as distinct reference points. Compare the HTTP status code with the first observation date to monitor any changes in future checks. Continue to collect and preserve each source's output for accurate historical tracking.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observation활성 콘텐츠Ordinary HTTP content served90%2026-10-11 10:09:32 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-10-11 10:09:32 UTClast content: 2026-10-11 10:09:32 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 akuvia.shop· checked Sep 28, 2026
63
Needs Work
Performance
FCP
2.86s
First Contentful Paint
LCP
7.96s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
257ms
Total Blocking Time
SI
4.73s
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-10-01 00:42:39 UTC
VirusTotal scanner detections updated from 6 to 7. Added scanner alerts: SOCRadar.
Threat First Observed2026-09-28 01:33:36 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 195.96.130.236.
위협 대응 Pipeline
발견
Analysis
Monitoring
12 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
도메인은 계속 연결 가능하거나 액세스가 제한되어 있습니다. 향후 점검을 통해 이 관찰 내용이 업데이트될 수 있습니다.
How we investigate & report
Public scans, evidence and abuse channels
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.
