The domain parik24-ukrain.com.ua is described with a VirusTotal detection record dated 2026-10-09, which documents scanner-based observations. On 2026-10-13, a PageSpeed performance score of 79 was recorded for the domain, providing a technical measurement relevant to its efficiency.
Recorded Evidence
VirusTotal checked parik24-ukrain.com.ua on 2026-10-09, recording 14 detections out of 92 total scanners. The domain appeared in the PhishDestroy internal listing as of 2026-10-13. A PageSpeed check on 2026-10-13 measured a performance score of 79 for the domain.
Interpretation
The VirusTotal record contains a dated measurement of detection engines that flagged the domain, offering a snapshot of scanner-based findings. The PhishDestroy internal listing documents the domain's presence in a publisher-maintained catalogue. The PageSpeed score reflects a technical performance metric, which is limited to efficiency at the time of observation and does not address security.
Recommended Actions
For parik24-ukrain.com.ua, retain the VirusTotal detection record and the PhishDestroy internal listing for ongoing reference. Keep the PageSpeed performance score for technical comparison. Compare any new source records to these stored observations to monitor changes in scanner-based security and technical measurements.
DOM Analysisanalyzed 2026年10月13日score 10/1001 brand signal
Submitted URLhttps://www.parik24-ukrain.com.ua/
Favicon Hash
Impersonates
Telegram
TLS 证书
Certificate hostname mismatch·
颁发者 Let's Encrypt / YR2· stored validity ends in 56 days
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
185.68.16.48
Network ASN
AS200000
Organization
DX-DC network
Observed location
Kyiv, UA
域名服务器 3
c.ns.services
d.ns.gold
e.ns.gold
Location describes the IP network.
TLS 证书
Issuer
Let's Encrypt / YR2
Valid from
2026-09-09 21:57:53
Valid until
2026-12-08 21:57:52
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-13 07:02:08 UTC
Collection source
PhishDestroy collector
Certificate fingerprint23c6a1478e219637ea9fe8745e14f01f39b02d16724beec6ed7fcab171b1136cCertificate names · 1 SANs
www.parik24-ukrain.com.ua
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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.
Google PageSpeed Insights — mobile performance audit of parik24-ukrain.com.ua· checked Oct 13, 2026
79
Needs Work
Performance
FCP
0.95s
First Contentful Paint
LCP
5.25s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
126ms
Total Blocking Time
SI
1.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.
Threat First Observed2026-10-13 05:49:38 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 185.68.16.104.
威胁响应 Pipeline
发现
Analysis
Monitoring
8 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.
