VirusTotal
13 / 91 engine detections
Відкрити звіт“403 Forbidden - Nginx”
фішинг: official-parik24.com.ua — Останній відомий активний (HTTP 301). Зведення доказів: VirusTotal 13/91 (alphaMountain.ai, Bfore.Ai PreCrime, BitDefender…
Докладний аналіз PhishDestroy AI нижче залишено англійською, щоб зберегти оригінальний криміналістичний запис.
13 / 91 engine detections
Відкрити звіт3 community references
Відкрити звітprovider verdict: clean
Відкрити звітNo threat flag
Відкрити звітNo malicious flag
Відкрити звітResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
official-parik24.com.ua borrows the Parik24 name and adds the word "official" to look like the brand's own site. The .com.ua address points it at Ukrainian users who would expect a local domain. PhishDestroy first flagged it on 2026-09-24 and classifies it as impersonation phishing. As of 2026-10-19 the domain was still alive and redirecting visitors elsewhere.
Impersonation sites like this copy a familiar brand and send visitors to a fake login, registration or payment page. Anyone who signs in or tops up an account there gives their username, password, card details or deposit to the operators instead of the real service. The "official" prefix is meant to reassure people who arrive from ads, search results or messages. The page currently shows the title "403 Forbidden - Nginx", a generic server error, while our classification is impersonation phishing. The domain still serves a working redirect.
On 2026-10-03, 13 of 91 VirusTotal engines flagged the domain. They include BitDefender, Fortinet, Forcepoint ThreatSeeker, G-Data, alphaMountain.ai, Bfore.Ai PreCrime, CRDF and CyRadar. That is a minority of engines, but the flags come from several independent vendors, including established names. The domain also appears in three AlienVault OTX threat pulses and on the PhishDestroy blocklist.
The domain was registered on 2026-04-30 through Hosting Ukraine LLC, about five months before PhishDestroy detected it. That gap fits a domain that was registered and then held until it was ready for use. Traffic passes through Cloudflare, Inc. at an address geolocated to Canada, which hides the actual origin server. The Google Trust Services certificate is the standard one issued for Cloudflare-fronted sites and reveals nothing about who runs it.
If you entered a Parik24 password on this domain, change it on the genuine service and on any other account that uses the same password, and turn on two-factor authentication. If you entered card details or made a deposit, contact your bank to block the card and dispute the charges, and watch for follow-up messages promising refunds. Reach Parik24 only by typing its known address yourself, never through links that add words like "official". Defenders should block official-parik24.com.ua at DNS and web proxies and report it to Cloudflare and Hosting Ukraine LLC for takedown.
Репутація Edge-IP не пов’язана з цим доменом.
sean.ns.cloudflare.comLocation describes the IP network.
8190957a56d5cc96372db3f16e19da3b21caaa068e08e17eaf3fe86ed9a31c11Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
ftp.official-parik24.com.uaDomain recordmail.official-parik24.com.uaDomain recordwww.official-parik24.com.uaDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of official-parik24.com.ua · checked Sep 24, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
redirect: raw=redirect_301; http=301; via=https_proxy; location=https://pari24.kyiv.ua/; server=cloudflare
official-parik24.com.ua
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Невідомо→redirected
http_redirect
Невідомо→redirected
http_redirect
Невідомо→redirected
http_redirect
Невідомо→redirected
http_redirect
Невідомо→redirected
http_redirect
Невідомо→redirected
http_redirect
Невідомо→redirected
http_redirect
Невідомо→redirected
http_redirect
Невідомо→redirected
http_redirect
Невідомо→redirected
http_redirect
Невідомо→redirected
http_redirect
Невідомо→redirected
http_redirect
Невідомо→redirected
http_redirect
Невідомо→redirected
http_redirect
Невідомо→redirected
http_redirect
Невідомо→redirected
http_redirect
Невідомо→redirected
http_redirect
Невідомо→redirected
http_redirect
No threat flag
View source13/91 engine detections
View source3 community references
View sourceofficial-parik24.com.ua
View sourceListed domains receive at least one abuse report; this entry has no retained notification history.
Якщо ви ввели облікові дані облікового запису, особисту чи платіжну інформацію або завантажили файл із цього домену, негайно вживіть заходів. Нижче наведено ресурси, які допоможуть вам повідомити про інцидент і захистити себе.
Виберіть свою країну, щоб отримати офіційні контакти кіберзлочинців або створити проект скарги →.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
official-parik24.com.ua)Навіть якщо ви не знаєте всіх подробиць — все одно подати заяву. Навіть неповна інформація все одно допомагає у розслідуванні.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Аналіз загроз за допомогою збереженого списку блокувань, WHOIS, DNS і загальнодоступних доказів сканування
Сканувати заразДодавайте підозрілі домени до нашої бази даних загроз — захищайте спільноту
ПовідомитиОстанні звіти про фішинг і помічені зміни доступності
ВідстежуватиСлідкуйте за актуальними загрозами або оскаржте цей запис, якщо вважаєте, що це помилкова тривога
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.