VirusTotal
8 / 93 engine detections
Відкрити звіт“Parked Domain name on Hostinger DNS system”
підробка під Kamino: kaminoi.finance — Контент недоступний. Зведення доказів: VirusTotal 8/93 (ChainPatrol, alphaMountain.ai, CRDF, CyRadar, Forcepoint…
Докладний аналіз PhishDestroy AI нижче залишено англійською, щоб зберегти оригінальний криміналістичний запис.
8 / 93 engine detections
Відкрити звітno 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
The domain kaminoi.finance was registered on February 21, 2026 through Hostinger Operations, UAB. It is currently listed as offline but remains a known brand‑impersonation vector targeting the Kamino brand. Automated analysis shows the site presented a generic parking page titled "Parked Domain name on Hostifier DNS system" and served a Let's Encrypt certificate (R13) issued for the domain, indicating the presence of TLS without any extended validation. DNS resolution points to IP address 84.32.84.32, which belongs to AS47583 Hostinger International Limited located in Lithuania.
The host is fronted by Hostinger CDN and advertises support for HTTP/3, while Google Analytics scripts were detected, suggesting basic traffic monitoring capabilities. The domain is flagged by eight of ninety‑three VirusTotal scanners, and it appears on three public blocklists. Specific blocklisting services that have taken action include PhishDestroy, MetaMask, and SEAL. Nameserver records are ns1.dns-parking.com and ns2.dns-parking.com, both typical of parked domains.
Gridinsoft assigned a trust score of 0 out of 100, reinforcing the malicious classification. While the site currently returns no active content beyond the parking message, the infrastructure—particularly the use of a legitimate TLS certificate and reputable CDN—can be leveraged to lend credibility to future malicious campaigns. Defenders should continue to block the domain at perimeter filters, monitor for any changes in HTTP response or content, and correlate any outbound connections to 84.32.84.32 with internal user activity. Updating threat intelligence feeds with the domain’s indicator set and ensuring endpoint protection reflects the eight VirusTotal detections will reduce exposure to potential brand‑impersonation attempts.
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.
ns2.dns-parking.comLocation describes the IP network.
1260e0f4e0b027cee0cb2fddfe6b3142e1da2feb1ddff863e62e480c289225f7www.kaminoi.financeSaved 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.
www.kaminoi.financeDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of kaminoi.finance · checked Mar 2, 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.
kaminoi.finance
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
8/93 engine detections
View sourcePage captured
View sourceNo threat flag
View sourcekaminoi.finance
View sourceПовідомив 1 учасник спільноти; уперше помічено 21.01.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 ↗
kaminoi.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.