VirusTotal
3 / 91 engine detections
Відкрити звіт“Express”
домен у блоклистах: io-trader.online — Останній відомий активний (HTTP 200). Зведення доказів: VirusTotal 3/91 (alphaMountain.ai, Chong Lua Dao, Gridinsoft)…
Докладний аналіз PhishDestroy AI нижче залишено англійською, щоб зберегти оригінальний криміналістичний запис.
3 / 91 engine detections
Відкрити звіт2 threat-system alerts
Відкрити звітSuspicious
Відкрити звітchecked — no match recorded
23 community references
Відкрити звіт14 перевірено — блокувань немає
No threat flag
Відкрити звітNo malicious flag
Відкрити звітResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| Hagezi Threat Feed | io-trader.online |
malicious | Sinkholed |
| DNS4EU | io-trader.online |
malicious | Sinkholed |
PhishDestroy threat report
The domain io-trader.online was registered on March 10, 2026 through NameCheap, Inc. It resolves to the IPv4 address 68.65.123.154, which is assigned to AS22612, a Namecheap network located in the United States. The authoritative name servers are dns1.namecheaphosting.com and dns2.namecheaphosting.com. The site is currently active and returns HTTP 200 responses. A content inspection shows the page title “Express” and the web stack is identified as Node.js running on LiteSpeed with the Express framework. The TLS certificate is issued by Sectigo Limited under the Sectigo Public Server Authentication CA DV R36, indicating a valid‑looking HTTPS deployment. Mail exchange records include mx1-hosting.jellyfish.systems with priority 5 and another host with priority 10, suggesting a third‑party mail service. Reputation data classifies the site as a generic phishing operation. VirusTotal analysis flags the domain on 3 of 95 security engines, and the domain appears on three external blocklists. Additional defensive feeds have already blocked the domain, including PhishDestroy, MetaMask, and SEAL. Gridinsoft assigns a trust score of 0 out of 100, reinforcing the malicious assessment. Analysts should treat any communications originating from or referencing io-trader.online as hostile. Network defenders are advised to add the domain and its resolving IP to deny‑list rules, monitor DNS queries for the associated name servers, and enforce TLS inspection to capture potential credential submissions. Email gateways should block the listed MX hosts, and endpoint protection should flag any attempts to access the site, especially given the low trust score and confirmed phishing classification.
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.
dns1.namecheaphosting.comdns2.namecheaphosting.commx1-hosting.jellyfish.systemspriority 5mx2-hosting.jellyfish.systemspriority 10mx3-hosting.jellyfish.systemspriority 20Location describes the IP network.
61d54590f2ab8a0899dad6f98c420200f0ff532014311ee5bfb867c15d888039www.io-trader.onlineSaved 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.io-trader.onlineDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of io-trader.online · checked Mar 10, 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.
alive_content: raw=ok; http=200; via=https_proxy; server=LiteSpeed
io-trader.online
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
Невідомо→live_content
content_served
0→3
No threat flag
View source23 community references
View source3/91 engine detections
View sourcePage captured
View sourceio-trader.online
View sourceПовідомив 1 учасник спільноти; уперше помічено 10.03.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 ↗
io-trader.online)Навіть якщо ви не знаєте всіх подробиць — все одно подати заяву. Навіть неповна інформація все одно допомагає у розслідуванні.
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.