VirusTotal
9 / 91 engine detections
Відкрити звіт“Apyx”
фішинг: compensation-apyx.finance — Доступно · доступ обмежено (HTTP 403). Зведення доказів: VirusTotal 9/91 (alphaMountain.ai, BitDefender, CRDF, Forcepoint…
Докладний аналіз PhishDestroy AI нижче залишено англійською, щоб зберегти оригінальний криміналістичний запис.
9 / 91 engine detections
Відкрити звітSuspicious
Відкрити звітDBL_PHISH
2 community references
Відкрити звіт13 перевірено — блокувань немає
No threat flag
Відкрити звітResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
The domain compensation-apyx.finance is currently under investigation for its involvement in generic phishing activities. The domain's risk level is categorized as under investigation due to its potential use in misleading users to disclose sensitive information by masquerading as a legitimate financial service. The presence of technologies such as jsDelivr and crypto-js suggests attempts to enhance the site's functionality for malicious purposes.
The domain was created on June 09, 2026, and is registered with NICENIC INTERNATIONAL GROUP CO., LIMITED. It resolves to the IP address 172.67.165.183. While VirusTotal has not yet flagged the domain, with a 0/95 detection score, it appears on 3 security blocklists. The domain's trust score according to Gridinsoft is 0/100, indicating a complete lack of trustworthiness. Additionally, it has been blocked by several security solutions, including MetaMask and PhishDestroy, and is part of 2 threat intelligence pulses on AlienVault OTX. The SSL certificate is issued by Google Trust Services, which may lend a false sense of security to unsuspecting users.
To mitigate the risks associated with this phishing domain, users are advised to avoid engaging with any communications or transactions originating from this domain. Security measures such as updating browser security settings, employing comprehensive anti-phishing software, and ensuring that all sensitive transactions are conducted through verified and trusted websites are crucial. Organizations should also consider implementing DNS filtering to prevent access to known malicious domains and conduct regular security awareness training for staff to recognize phishing attempts.
Last checked
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
Репутація Edge-IP не пов’язана з цим доменом.
keaton.ns.cloudflare.comLocation describes the IP network.
b8e229d0b5fd033e1e8397e4aaafb5515975fc72d25c4a3212042f413715035fSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of compensation-apyx.finance · checked Jun 26, 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.
cloudflare_ban: raw=cf_phishing_block; http=403; via=https_proxy; server=cloudflare; provider_error=cloudflare_phishing_interstitial
compensation-apyx.finance
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Невідомо→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Невідомо→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Невідомо→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Невідомо→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Невідомо→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Невідомо→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Невідомо→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Невідомо→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Невідомо→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Невідомо→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Невідомо→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Невідомо→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Невідомо→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Невідомо→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Невідомо→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Невідомо→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Невідомо→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Невідомо→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Невідомо→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Невідомо→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Невідомо→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Невідомо→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Невідомо→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Невідомо→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Невідомо→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Невідомо→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Невідомо→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Невідомо→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Невідомо→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
Недоступно→Доступний
Доступний→Недоступно
5→Observation retained
9/91 engine detections
View sourceNo threat flag
View source2 community references
View sourcecompensation-apyx.finance
View sourceПовідомив 1 учасник спільноти; уперше помічено 09.06.2026
Listed 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 ↗
compensation-apyx.finance)Навіть якщо ви не знаєте всіх подробиць — все одно подати заяву. Навіть неповна інформація все одно допомагає у розслідуванні.
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.