跳转到安全报告
Domain security report
idexs.io favicon

idexs.io

“IDEX-CRYPTO”

威胁判定
Assessment sources

Assessment based on the stored source evidence below. Review sources →

可用性 内容不可用 最新观察中的内容不可用 观察到 · HTTP probe
病毒检测总数:13/91 诈骗类型:Impersonation
OTX: 23 refs 2025年11月28日 CDN
API
注册商
Gname
Resolved IP
38.60.250.187
Registered
2025年7月18日
2 sources
In this reportGet help
该域名已被标记为恶意域名
安全引擎报告检测:13。 请格外小心——不要输入凭据或个人信息。
报告概览

idexs.io — 内容不可用. 诈骗类型:Impersonation. 证据摘要: VirusTotal 13/91 (alphaMountain.ai, BitDefender, CRDF, CyRadar, Fortinet); PhishDestroy score 89/100. 注册商: Gname.

为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。

Additional indicators at a glance

VirusTotal
VirusTotal
13 det.
OTX references
URLScan
URLScan
Gridinsoft
72/100Clean
TLS 证书
Within stored validity dates
Google Trust Services · Hostname coverage not recorded
年龄
1.2 yr
观测状态
内容不可用
PhishDestroy
DestroyList
已列入

Source evidence

8 · sources

These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.

VirusTotal

13 / 91

报告
Interpretation & limits

Engine detections from this stored analysis. Vendors and collection times may differ from other sources.

OTX

23 community references

报告
Interpretation & limits

Community publication references, not a vendor verdict or evidence of a common operator.

CF雷达

provider verdict: clean

Observation time not recorded
报告
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

URLScan capture

存储的报告

View stored capture ↗
报告
Interpretation & limits

A preserved page image documents what the collector received; a capture is not a safety verdict.

URLScan verdict

分析完成

报告
Interpretation & limits

This is the recorded automated analysis. Completion alone is not a safety verdict.

Gridinsoft

72/100

Observation time not recorded
报告
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Google Safe Browsing

Checked; no threat flag recorded

报告
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Public blocklists

0 external matches

详情
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

安全信号
GS Gridinsoft Analysis 72 / 100
Hosting SSL Certificate Young Domain

证据摘要

关键
VirusTotal
13/91
OTX
23 community refs
URLScan
Stored capture

AI-assisted analysis Stored narrative · generated . Provider checks below retain their own observation dates. This narrative is an interpretation of collected evidence, not an independent source verdict.

This domain, idexs.io, is flagged as an active cryptocurrency-themed phishing site based on observable technical indicators. Registered on July 18, 2025, through Gname.com Pte. Ltd., the domain currently resolves to IP address 38.60.250.187, hosted under AS138915 (Kaopu Cloud HK Limited) in Germany. The page title, 'IDEX-CRYPTO,' suggests an attempt to impersonate a cryptocurrency exchange or trading platform, though the exact content and target brand remain unverified due to lack of direct analysis. Infrastructure analysis reveals the use of Cloudflare nameservers (felipe.ns.cloudflare.com and mary.ns.cloudflare.com) and SSL certification issued by Google Trust Services (WE1), alongside detected technologies including Vue.js and HTTP/3. The domain is actively blocked by at least one security provider and appears on 23 threat intelligence pulses in AlienVault OTX. VirusTotal reports 9 detections from security vendors, reinforcing its classification as malicious. A 301 HTTP redirect is present, which may indicate an attempt to funnel victims to a secondary malicious endpoint. Defenders should treat this domain as high-risk, particularly in environments involving cryptocurrency transactions or financial services. Immediate blocking at the DNS and network level is recommended, alongside monitoring for related domains using similar naming conventions or infrastructure patterns. Further investigation into associated IP ranges and certificate reuse may uncover additional linked threats.

Data coverage & collection

21 · datasets with records / 10 · not recorded

What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.

Recorded dataPartial recordUTC
VirusTotal
13 / 91 · engine detections
URLScan analysis
Automated verdict retained
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
23 · community references
External blocklists
0 · external matches
Cloudflare Radar
无异常Collection time not recorded
Gridinsoft
72/100 · provider trust scoreCollection time not recorded
Spamhaus DBL
Collection time retained; verdict missing
Domain registration
Gname.com Pte. Ltd.Collection time not recorded
Network & DNS
38.60.250.187 · 2 · nameserversCollection time not recorded
TLS 证书
Google Trust Services
Page captures
2 · retained captures
Page analysis
0 · automated brand labels
Observed indicators
0 · wallet / Telegram indicators
Detection & evasion
Stored browser and crawler comparison
PageSpeed performance
62/100 · mobile performance
Availability history
16 · stored state changes
Source observation history
1 · stored source events
社区报告
Aggregate report counts and dates
IP reputation
Network-level observations
Wayback archive
Archive link retained
Not recorded in this report 10

These checks have no retained result. This does not mean they passed or that a scan is running.

  • URLQuery
  • PhishStats
  • DNS security filters
  • Scamadviser
  • HTML archives
  • Site configuration files
  • Response records
  • Recorded subdomains
  • Lookalike relationships
  • Chainabuse records
Download the dated observations and supporting metadata.

Blocklist records

0 · external source matches

公共封禁名单状态

Domain, network & archive

Gname.com Pte. Ltd. · 38.60.250.187 · DNS, TLS and retained responses

Domain details

域名
URLScan verdict 分析完成 score 0 report ↗
IP Context CDN shared edge origin IP hidden Edge-IP 声誉不属于此域。
OTX tags 2025-11activeall-domainsblocklistcontentcrypto域名drainerfraudlivemonthlyphishdestroyphishingscam
注册商 Gname SG(SG)
滥用举报联系方式abuse@idexs.io
ICANN 注册管理机构ICANN Lookup (RDAP) →
注册信息创建 2025年7月18日
首次不可用所需时间 108 days
统计口径 从第一个存储的滥用报告到第一次观察到内容不可用所经过的时间。这并不能确定原因。
每份报告包含哪些内容 存储的传出报告记录可以参考当时可用的证据,例如供应商判决、注册数据、托管详细信息、分类或屏幕截图。此页面无法推断收件人交付、接收、确认或操作的确切有效负载。
技术详情Provenance & timestamps
首次发现2025年11月28日
DOM Analysisanalyzed 2026年3月11日score 83/100
Submitted URLhttp://idexs.io/

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
38.60.250.187
Network ASN
AS138915
Organization
Kaopu Cloud HK Limited
Observed location
Frankfurt am Main, DE
Server header
nginx

Edge-IP 声誉不属于此域。

域名服务器 2
  • felipe.ns.cloudflare.com
  • mary.ns.cloudflare.com

Location describes the IP network.

TLS 证书

Issuer
Google Trust Services
Valid from
2026-03-11 16:15:27
Valid until
2026-06-09 17:13:07
Hostname coverage
Hostname coverage not recorded
Validity
Stored certificate expired
Collection time
2026-03-11 19:30:50 UTC
Collection source
PhishDestroy collector
Certificate fingerprintdbc8aeb4cb6777241d2c97a4912f760c97e2259bddd7d5525afe4f549244c619

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Latest Classified Outcome 2026-10-16 20:22:38 UTC

Primary outcome DNS 非活动 reason: DNS NXDOMAIN 80% confidence
Attribution source: Dns Cache
Evidence layers Availability: DNS inactive Content: Unreachable DNS: NXDOMAIN Registration: Unknown
Latest HTTP observation 未知 Probe Inconclusive 20% 2026-10-17 01:11:09 UTC
RDAP registration 未知
Observed timeline last reachable: 2026-08-17 22:15:51 UTC current episode first observed: 2026-09-30 16:14:55 UTC observed RIP window: 2026-08-17 22:15:51 UTC → 2026-09-30 16:14:55 UTC · 1,049.98h midpoint estimate ≈ 2026-09-08 19:15:23 UTC · precision very low · basis bounded
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
技术 · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
举报此域名 提交证据,帮助保护他人

VirusTotal 分析

13 / 91 安全供应商标记了该域
View on VT
Last analyzed Previous stored snapshot: 9 detections
alphaMountain.ai
BitDefender
CRDF
CyRadar
Fortinet
G-Data
Gridinsoft
卡巴斯基
LevelBlue
Lionic
SafeToOpen
SOCRadar
Sophos

存档证据

Wayback Machine Snapshot
历史快照可供证据审查
View Archive
网站性能分析

Google PageSpeed Insights — mobile performance audit of idexs.io · checked Jul 12, 2026

62
Needs Work
Performance
FCP
3.18s
First Contentful Paint
LCP
6.52s
Largest Contentful Paint
CLS
0.002
Cumulative Layout Shift
TBT
287ms
Total Blocking Time
SI
4.72s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details8

Availability observations

Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
1049.98
Estimate basis
Bounded by observations
Estimate precision
very_low

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Detection & evasion checks

Stored browser and crawler observations

探测与规避分析

隐身和流量分配检查

未观察到 在存储的扫描图像中未观察到遮蔽现象

针对该主机的爬虫与浏览器观察记录,以及针对“Keitaro”式流量分配系统的实时指纹检测。

存储的隐身标志
未观察到
伪装评分
0/6
上次隐形扫描

扫描说明: unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='idexs.io', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("SOCKS

TDS指纹识别实时演示
检查七项 Keitaro 特征,并比较浏览器与爬虫的响应。只有点击按钮后才会开始新的扫描。
已保存的结果
无法访问

Timeline & response

Collection history, report status and investigation channels

Forensic History & Detection Timeline

ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
  1. VirusTotal Detections Update 2026-07-12 17:22:04 UTC
    Source: VirusTotal
    Event details
    VirusTotal scanner detections updated from 1 to 9. Added scanner alerts: BitDefender, CRDF, CyRadar, Fortinet, G-Data, Gridinsoft, Kaspersky, alphaMountain.ai.
Stored observation history17

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    dns_inactive→未知

    probe_inconclusive

  2. Availability monitor · Recorded state

    未知→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    dns_inactive→未知

    probe_inconclusive

  4. Availability monitor · Recorded state

    未知→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    dns_inactive→未知

    probe_inconclusive

Earlier observations 12
  1. Availability monitor · Recorded state

    未知→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    dns_inactive→未知

    probe_inconclusive

  3. Availability monitor · Recorded state

    未知→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    dns_inactive→未知

    probe_inconclusive

  5. Availability monitor · Recorded state

    未知→dns_inactive

    dns_nxdomain

  6. Availability monitor · Recorded state

    dns_inactive→未知

    origin_unreachable · http_5xx

  7. Availability monitor · Recorded state

    未知→dns_inactive

    dns_nxdomain

  8. Availability monitor · Recorded state

    dns_inactive→未知

    origin_unreachable · http_5xx

  9. Availability monitor · Recorded state

    未知→dns_inactive

    dns_nxdomain

  10. Availability monitor · Recorded state

    dns_inactive→未知

    origin_unreachable · http_5xx

  11. Availability monitor · Recorded state

    dns_inactive

    dns_nxdomain

  12. VirusTotal · Detection count

    1→9

威胁响应 Pipeline

发现
Analysis
Monitoring

12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

已捕获威胁
idexs.io 已检测到并排入队,待进行全面分析
2025年11月28日
URLScan.io Capture
已存储 URLScan report with capture artifacts
2026年2月27日
Cloudflare Radar Report
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
Web Archive
Preserved in 互联网档案馆 — historical evidence archived
2026年3月14日
VirusTotal
13/91 recorded on VirusTotal
2026年8月12日
OTX Community References
23 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
2026年7月12日
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
2026年2月27日
Technical Analysis Recorded
该报告包含存储的技术或取证分析结果。
2026年10月18日
VT Detection +8
+8 new detections (1 → 9): BitDefender, CRDF, CyRadar, Fortinet +4
2026年7月12日
DestroyList 已发布
2025年11月28日
Content Observed Unavailable
最新存储的检查表明报告的内容不可用;这并不能确定是谁或什么原因造成了这种变化。
2026年3月17日
首次不可用所需时间
2603 从检测到第一次不可用的观察经过了几个小时。
How we investigate & report

Public scans, evidence and abuse channels

We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.

01Public scans & evidence collection10 sources and tool groups
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.

Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.

Related infrastructure

Shared hosting, registrar records and related domains

Community records

Retained community reports and observations

社区报告

由 1 名社区成员报告;首次发现于 2025年11月28日

已存储报告
1
已报告的唯一 URL
1
已接受1

Evidence & investigation tools

Original reports, independent checks and evidence links

Help & reporting

Recovery steps, reporting contacts and complaint drafts

Help & reporting

您是否受到本网站的影响?

6 evidence signal groups linked 0 stored notification records 内容不可用

Listed domains receive at least one abuse report; this entry has no retained notification history.

If credentials were compromised, report immediately. Do not engage with recovery scammers.

如果您输入了帐户凭据、个人或付款信息,或者从此域下载了文件,请立即采取措施。以下资源可帮助您报告事件并保护自己。

Official reporting routes
警惕“数据恢复”诈骗! 犯罪分子可能会冒充调查员、律师或追债员再次联系受害者。 请勿支付预付费用或共享凭证。 了解有关康复欺诈的更多信息 →
向当地主管部门报告

选择您所在的国家/地区以获取 官方网络犯罪联系人 或 创建投诉草稿 →。

97个国家目录

Template-based draft · optional AI wording assistance requires separate consent

AI辅助草稿——事件详细信息由AI提供商处理 · 自行审核并提交
After a phishing incident

针对受害者的建议与指导

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.

  • 更改所有密码 — 电子邮件、Exchange 账户,以及任何使用同一密码的账户
  • 启用双因素认证 使用身份验证器应用(而非短信)。禁用基于短信的恢复功能
  • 冻结卡片 如果您在钓鱼网站上输入了银行信息

我应该为报告收集哪些信息?

联邦调查局(FBI)指南

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • 确切日期和时间 — 每笔交易的详情以及与诈骗者的首次接触
  • 屏幕截图 — 诈骗网站、聊天消息、电子邮件、钱包交易、社交媒体
  • 所有网址和域名 诈骗者使用的(包括 idexs.io)
  • 通信 — 诈骗者使用的电子邮件、短信、电话号码、用户名

即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。

我应该向哪里举报这起诈骗?

  • 联邦调查局(FBI)IC3 — 互联网犯罪投诉中心(美国联邦举报渠道)
  • 欧洲刑警组织 — 欧洲网络犯罪报告(欧盟)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • 当地警方 — 即使无法立即采取行动,也能留下正式记录

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • 虚假网站 — 与正规网站完全一致的克隆网站,仅域名略有改动
  • 猪的屠宰 — 通过Telegram/WhatsApp/交友软件花数周时间建立信任,随后钱被骗走
  • 退款诈骗 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • 利用人工智能实施的诈骗 — 深度伪造、自动化网络钓鱼以及人工智能生成的网站,使得欺诈行为更难被察觉

将来我该如何保护自己?

  • 将官方网站添加到书签 — 切勿点击来自电子邮件、私信或广告中的链接
  • 验证域名 — 查看 PhishDestroy 在进行互动之前,请检查HTTPS、拼写和域名注册时间。
  • “好得令人难以置信”=骗局 — 保证收益、名人代言、紧迫的截止日期

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

随时掌握最新信息,确保安全

请实时监控威胁,或者如果您认为这是误报,请对该条目提出异议

实时威胁动态 对该列表提出异议
Read the evidence in context

关于本报告:idexs.io

该报告提供了 PhishDestroy 可用的最新存储证据。如果有的话,会显示源时间戳;收集后可用性和供应商判断可能会发生变化。

捕获的站点显示页面标题 “IDEX-CRYPTO”。

截至 2026-08-12 02:29:50 UTC,idexs.io 已检测到 13 安全引擎。

Each source records a particular observation. A screenshot, an available website, or a result with no detections does not establish that a site is safe. Source results can change after they are collected.

Embed this report

A compact widget with a link to the evidence

HTML · IFRAME

嵌入此报告

在您的网站或博客上分享此威胁情报

embed.html
<iframe
  src="https://phishdestroy.io/zh/embed/domain/idexs.io"
  title="PhishDestroy threat report for idexs.io"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>