HEI

Historical Exchange Index

A quiet registry of crypto exchanges, active and gone.

Home / Active / DragonEX

Exchange record

DragonEX

Singapore-linked centralized cryptocurrency exchange launched on November 2, 2017. DragonEX suffered a major March 2019 cyberattack and is now marked by exchange trackers as inactive or no longer operational, but HEI does not assign a terminal shutdown date because no sufficiently strong official closure notice has been established.

CEXInactive
Also known as: DragonEx, DragonEX.io, DragonEx.io, DragonEX.in

Registry sequence

Key facts

Launch date
2017-11-02
Death date
Years
2017–—
Origin
Singapore
Confidence
medium
Last verified
2026-06-26

URL handling

Preferred action
Use current URL handling based on status below.
URL status
Unknown
Original URL
https://dragonex.io/
Archived URL

Summary

Singapore-linked centralized cryptocurrency exchange launched on November 2, 2017. DragonEX suffered a major March 2019 cyberattack and is now marked by exchange trackers as inactive or no longer operational, but HEI does not assign a terminal shutdown date because no sufficiently strong official closure notice has been established.

Timeline

DragonEX launched
2017-11-02launchedmedium

CoinMarketCap describes DragonEX as launched on 2017-11-02 in Singapore.

DragonEX suffered a major cyberattack
2019-03-24hackcritical

DragonEX announced that user and platform crypto assets were transferred and stolen in a March 2019 cyberattack, and temporarily closed platform services while investigating the incident.

Evidence

CoinMarketCap2026-04-29database_referencemedium reliabilityentityarchive
CoinDesk2019-03-26news_articlemedium reliabilityeventarchive
Distributed Networks Institute2019-03-24database_referencemedium reliabilityeventarchive
Internet Archive2026-04-29archive_capturemedium reliabilityurl_historyarchive
CoinCodexdatabase_referencemedium reliabilitystatusarchive
CoinMarketCapdatabase_referencemedium reliabilitylaunch_datearchive

Related records

Notes and record state

Record note
The existing launch and March 2019 hack events are not duplicated. Current DragonEX-branded domains on unrelated domains are not treated as proof that the original dragonex.io exchange resumed. Keep inactive rather than assigning a death_reason or death_date without stronger terminal evidence.
Revision state
Records may be incomplete, approximate, contested, or revised as better evidence becomes available.
This record may be incomplete or revised. Dead-side entries prefer archived URLs over original domains. Dates, causes, and classifications may change when stronger evidence becomes available. Contact / corrections

Navigation

Registry
Active-side
Contact / Corrections
GitHub Issues