Stored registration data identifies NICENIC INTERNATIONAL GROUP CO., LIMITED (IANA 3765) as the registrar. PhishDestroy maintains separate NiceNIC abuse-report research; registrar association is contextual and is not an independent detection for this domain.
The domain app.merkl.exchange is identified as a fake cryptocurrency exchange platform. It poses a threat by attempting to deceive users into believing it is a legitimate trading service, likely to steal login credentials, funds, or personal information through social engineering.
Technical analysis shows the site is flagged by 13 out of 95 VirusTotal vendors, including ADMINUSLabs, ChainPatrol, BitDefender, CRDF, and CyRadar. Google Safe Browsing reports it as flagged for SOCIAL_ENGINEERING. The domain is registered with NiceNIC International Group Co., Limited, created on 2026-01-03, and hosted on IP 172.67.185.200 (US) under AS13335 Cloudflare, Inc. It has no SSL certificate and uses nameservers cloe.ns.cloudflare.com and mitch.ns.cloudflare.com. GridinSoft trust rating is 0 out of 100.
The site is currently offline. Based on the high detection rate, blocklist presence, and lack of SSL, the risk level is high. Users should avoid any interaction with this domain or its associated services.
探测与规避分析
隐身和流量分配检查
未观察到在存储的扫描图像中未观察到遮蔽现象
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
未观察到
伪装评分
0/6
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='app.merkl.exchange', port=80): Max retries exceeded with url: / (Caused by NewConnectionEr
For the registrable domain merkl.exchange behind this subdomain, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
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.
Primary outcomeRegistration hold observedreason: Registrar clientHold95% confidence
AttributionNICENIC INTERNATIONAL GROUP CO., LIMITEDmechanism: Registrar clientHoldsource: Rdap Status Collector
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Registrar clientHold
Latest HTTP observation未知Probe Inconclusive20%2026-10-12 02:34:09 UTC
RDAP registrationRegistrar clientHoldNICENIC INTERNATIONAL GROUP CO., LIMITED · IANA 3765RDAP HTTP 200source: Rdap Status CollectorclientDeleteProhibitedclientHoldclientTransferProhibitedexpires 2027-01-03 17:07:39 UTCchecked 2026-10-12 04:06:11 UTC
Registrar action markerverified clientHold markerNICENIC INTERNATIONAL GROUP CO., LIMITED · IANA 3765causal link to our report not established
Observed timelinelast reachable: 2026-05-16 14:56:55 UTCcurrent episode first observed: 2026-08-05 01:45:38 UTCobserved RIP window: 2026-05-16 14:56:55 UTC → 2026-08-05 01:45:38 UTC · 1,930.81hmidpoint estimate ≈ 2026-06-25 20:21:16 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.
Last analyzed Previous stored snapshot: 11 detections
ADMINUSLabs
ChainPatrol
BitDefender
CRDF
CyRadar
Forcepoint ThreatSeeker
Fortinet
G-Data
Google Safebrowsing
SOCRadar
Sophos
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.
11 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
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+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
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.
(RU)
PhishDestroy Investigation
