VirusTotal
1 / 94 engine detections
Відкрити звіткриптоінвестиційне шахрайство: cryptofather.company — Контент недоступний. Зведення доказів: VirusTotal 1/94 (SOCRadar); URLQuery 1 det.; PhishDestroy score…
Докладний аналіз PhishDestroy AI нижче залишено англійською, щоб зберегти оригінальний криміналістичний запис.
1 / 94 engine detections
Відкрити звіт1 det.
Відкрити звітchecked — no match recorded
no community references
Відкрити звіт12 перевірено — блокувань немає
85/100
Відкрити звітScan report
Відкрити звіт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
PhishDestroy identifies cryptofather.company as an active cryptocurrency phishing domain posing as a legitimate crypto platform. The threat type has been classified as generic phishing with the domain currently marked as active and under investigation.
This domain was flagged by 1 of 95 VirusTotal vendors, registered through HOSTINGER operations, UAB, and resolves to IP address 88.223.85.35 using a Let's Encrypt SSL certificate. The domain was created on February 03, 2026, making it a very recent registration with minimal historical trust or reputation metrics available at this time.
The current status of cryptofather.company remains active with no known blocklist entries or vendor detections at the time of this assessment. Users should immediately avoid interacting with this domain, especially any requests for cryptocurrency deposits, account credentials, or personal financial information. If exposure has occurred, users are advised to revoke any shared credentials, monitor financial accounts, and report the incident to relevant authorities. Domain owners and security teams should consider immediate network-level blocking of IP 88.223.85.35 and domain cryptofather.company to prevent further compromise.
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.
ns1.dns-parking.comns2.dns-parking.comLocation describes the IP network.
Saved 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 cryptofather.company · checked Apr 5, 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.
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='cryptofather.company', port=80): Max retries exceeded with url: / (Caused by NewConnection
cryptofather.company
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
Невідомо→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
1/94 engine detections
View sourceNo threat flag
View sourcecryptofather.company
View sourcePD-20260405-40FA30
Повідомив 1 учасник спільноти; уперше помічено 05.04.2026
PD-20260405-40FA30 Recipient: abuse@hostinger.com Registrar: Hostinger Operations UAB (Lithuania (EU)) Policy Violations: AUP prohibits illegal activity including fraud, phishing, malware hosting; Hostinger may suspend/terminate services and domains Applicable Laws: Lithuanian Criminal Code (Ch. XXX, §§196–198 data/system crimes; §§214–215 electronic fraud); EU Directive 2013/40/EU
Якщо ви ввели облікові дані облікового запису, особисту чи платіжну інформацію або завантажили файл із цього домену, негайно вживіть заходів. Нижче наведено ресурси, які допоможуть вам повідомити про інцидент і захистити себе.
Виберіть свою країну, щоб отримати офіційні контакти кіберзлочинців або створити проект скарги →.
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 ↗
cryptofather.company)Навіть якщо ви не знаєте всіх подробиць — все одно подати заяву. Навіть неповна інформація все одно допомагає у розслідуванні.
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.