akazinmeytman.vercel.app returned an HTTP 404 status during a check on 2026-10-01, indicating that no page was found at the time. The domain was also listed in the PhishDestroy internal catalogue, providing another distinct observation from a publisher source.
Recorded Evidence
A check on 2026-10-01 recorded HTTP status 404 for akazinmeytman.vercel.app. The domain appeared in the PhishDestroy internal listing. VirusTotal recorded 15 detections out of 91 scanners on 2026-09-03. A PageSpeed check on 2026-09-02 showed a performance score of 100. The SSL issuer was noted as Google Trust Services / WR1 on 2026-09-02. The domain was first observed on 2026-08-26.
Interpretation
These records provide separate observations from HTTP, PhishDestroy, and VirusTotal sources, each with its own date. The HTTP status documents the response at one point, while the PhishDestroy and VirusTotal records reflect distinct catalogue and scan results. The chronology of these checks allows for comparison between source records without indicating a direct relationship between them.
Recommended Actions
Retain the HTTP response record and the PhishDestroy listing for akazinmeytman.vercel.app as distinct references. Compare the VirusTotal detection entry with the PhishDestroy listing in future reviews, preserving each source’s values. Keep the PageSpeed and SSL scan results for ongoing comparison in subsequent assessments.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationRedirectingHTTP redirect observed80%2026-10-13 22:05:29 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-13 22:05:29 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.
技术 · 2 identified
V
Vercel
PaaS
Vercel is a cloud platform for static frontends and serverless functions.
Last analyzed First positive detection Previous stored snapshot: 15 detections
alphaMountain.ai
BitDefender
CyRadar
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
卡巴斯基
Lionic
MalwareURL
Netcraft
Sophos
Webroot
网站性能分析
Google PageSpeed Insights — mobile performance audit of akazinmeytman.vercel.app· checked Sep 2, 2026
100
Good
Performance
FCP
0.79s
First Contentful Paint
LCP
0.79s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
0.79s
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-10-09 01:22:58 UTC
Domain state transitioned from dead to alive.
Domain Status Transition2026-09-02 22:00:22 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-02 11:33:11 UTC
Domain ingestion complete. Initial state is marked as alive.
威胁响应 Pipeline
发现
Analysis
Monitoring
10 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.
(US)
