Skip to security report
This domain has been flagged as malicious
Security engines reporting a detection: 3. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
cme-cmetrad.com favicon

cme-cmetrad.com

In short

PhishDestroy records the captured cme-cmetrad.com page, which presents itself as a Tokyo Commodity Exchange trading interface.

“cme-trading”

Registrar
Realtime
Resolved IP
United Kingdom188.114.96.3CloudFLARENET-EU · CDN
Registered
Oct 25, 2026
First observed
Nov 1, 2026
PhishDestroy assessment Critical
76/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
VirusTotal detections: 3/92 Stored blocklist matches: 2 Young domain: 6 days old
VirusTotal
engine detections ·
Blocklist matches
MetaMask, SEAL
OTX
community references
URLScan
engine verdict · score 98
Page captures
open gallery
Domain age
registered 2026-10-25 according to WHOIS
OTX: 2 refs Nov 1, 2026 CDN
X Telegram API

Analysis

Domain summary

PhishDestroy records the captured cme-cmetrad.com page, which presents itself as a Tokyo Commodity Exchange trading interface.

Critical
Status
Last known active
VirusTotal
3 / 92
Blocklist matches
2
Hosting
United Kingdom188.114.96.3CloudFLARENET-EU · CDN
Registrar
Realtime
Registered
Oct 25, 2026
OTX
2 community refs
Page captures
8

PhishDestroy analysis, reviewed version

The captured page presents itself as a Tokyo Commodity Exchange trading interface, headed by a banner reading "TOKYO COMMODITY EXCHANGE" with the subtitle "THE ESSENTIAL GUIDE." Below it, a panel shows three trading pairs with prices and percentage changes, followed by shortcut tiles for pledge mining, second contract, financing, and spot. Two prominent buttons offer quick coin charging and quick withdrawal of coins, and a tabbed list of popular coins repeats the BTC/USDT quote with its latest price and fluctuation range.

The stored VirusTotal domain result reports 3 detections out of 92 engines. CRDF reported "malicious"; LevelBlue reported "phishing".

Source evidenceVirusTotal 3 / 92 · OTX 2 references 7 sources

VirusTotal

3 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 15 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
52
Malicious
3
Suspicious
0
Undetected
37

Vendor labels

CRDF
malicious
LevelBlue
phishing
Forcepoint ThreatSeeker
phishing

Reputation score

0

Categories

alphaMountain.ai
Phishing (alphaMountain.ai)
Forcepoint ThreatSeeker
newly registered websites

Registrar

Realtime Register B.V.

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:3034::6815:5995
  • TTL, seconds
    300
    Type
    A
    Value
    172.67.160.226
  • TTL, seconds
    1800
    Type
    SOA
    Responsible mailbox
    dns.cloudflare.com
    Value
    fonzie.ns.cloudflare.com
  • TTL, seconds
    21600
    Type
    NS
    Value
    sloan.ns.cloudflare.com
  • TTL, seconds
    21600
    Type
    NS
    Value
    fonzie.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    A
    Value
    104.21.89.149
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:3031::ac43:a0e2

DNS records observed

JARM fingerprint

27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c

Certificate

Subject alternative names
  • *.cme-cmetrad.com
  • cme-cmetrad.com
Issuer
Let's Encrypt / YE1
Serial
63eeb6ae2e94fe9a9b7ac40e9195dc3ea39
SHA-256
0936e8805db5daf9faf244803f2ead81a9a2bdfd2552ebade86cf65139f7b14a
Subject
cme-cmetrad.com
Valid until
Valid from

Registration record

Registrar
Realtime Register B.V.
Registrar IANA ID
839
Registrar URL
http://www.realtimeregister.com
Registered
Updated
Expires
Status
  • clientTransferProhibited
Nameservers
  • fonzie.ns.cloudflare.com
  • sloan.ns.cloudflare.com
DNSSEC
unsigned

Registry data (RDAP)

Status
  • add period
Registry events
Expiration
Last changed
Registration
Registrar expiration
Last RDAP database update
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 52,
    "malicious": 3,
    "suspicious": 0,
    "undetected": 37
}
Vendor labels
{
    "CRDF": "malicious",
    "LevelBlue": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Categories
{
    "alphaMountain.ai": "Phishing (alphaMountain.ai)",
    "Forcepoint ThreatSeeker": "newly registered websites"
}
Registrar
Realtime Register B.V.
Created
2026-10-25T21:59:24Z
Expires
2027-10-25T21:59:24Z
Updated
2026-10-25T22:01:28Z
First seen
2026-10-25T22:09:18Z
DNS records
[
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3034::6815:5995"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "172.67.160.226"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "fonzie.ns.cloudflare.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "sloan.ns.cloudflare.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "fonzie.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "104.21.89.149"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3031::ac43:a0e2"
    }
]
Dns at
2026-10-31T03:21:28Z
Jarm
27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c
Certificate
{
    "san": [
        "*.cme-cmetrad.com",
        "cme-cmetrad.com"
    ],
    "issuer": "Let's Encrypt / YE1",
    "serial": "63eeb6ae2e94fe9a9b7ac40e9195dc3ea39",
    "sha256": "0936e8805db5daf9faf244803f2ead81a9a2bdfd2552ebade86cf65139f7b14a",
    "subject": "cme-cmetrad.com",
    "valid_to": "2027-01-23T21:05:43Z",
    "valid_from": "2026-10-25T21:05:44Z"
}
Registration record
{
    "registrar": "Realtime Register B.V.",
    "registrar_iana_id": "839",
    "registrar_url": "http://www.realtimeregister.com",
    "created": "2026-10-25T21:59:24Z",
    "updated": "2026-10-25T22:01:28Z",
    "expires": "2027-10-25T21:59:24Z",
    "status": [
        "clientTransferProhibited"
    ],
    "nameservers": [
        "fonzie.ns.cloudflare.com",
        "sloan.ns.cloudflare.com"
    ],
    "dnssec": "unsigned"
}
Registry data
{
    "status": [
        "add period"
    ],
    "events": {
        "expiration": "2027-10-25T21:59:24Z",
        "last changed": "2026-10-25T22:01:29Z",
        "registration": "2026-10-25T21:59:24Z",
        "registrar expiration": "2027-10-25T21:59:24Z",
        "last update of RDAP database": "2026-10-25T22:09:08Z"
    }
}
Separate source record · 3 malicious + 0 suspicious / 92 · 2026-10-31 03:11:16 UTC

The summary above and this provider record were collected at different times. Both remain available; malicious and suspicious classifications are shown separately.

record_source
collected_observations.vt
analysis_at
2026-10-31T03:11:16Z
fetched_at
2026-11-01T00:05:20Z
stats
{"timeout":0,"harmless":52,"malicious":3,"suspicious":0,"undetected":37}

URLScan

Malicious · engine verdict · score 98

SHA-256 2fa25a8e3f1bf8847ff8a7399c08daf99a5e96321941915192da5c0fb04204ad

Open report
URLScanOriginal source recordObserved: 23 fields

Observed: · Retrieved:

Report ID

01a1944f-1391-71a8-98e1-24c254cce78e

Final URL

https://cme-cmetrad.com/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://cme-cmetrad.com/
    From
    http://cme-cmetrad.com/
    Status
    307

IP address

172.67.160.226

Contacted domains

  • echo-hkp.oss-cn-hongkong.aliyuncs.com
  • w5.jiaoyisuo1688.com
  • static.cloudflareinsights.com

Contacted IP addresses

  • 8.210.242.86
  • 104.21.36.79
  • 104.16.79.73
  • 172.67.160.226

Autonomous systems (ASN)

  • 45102
  • 13335

Server countries

  • HK

Document hash

2fa25a8e3f1bf8847ff8a7399c08daf99a5e96321941915192da5c0fb04204ad

Script hashes

  • 95a320f6d338a2b0deede53d9db99046fc01a87027b9c2cf96ac2e4bc221c89f
  • cb0c6c9f1771d252eee7caa043bdd7cfffbd52c2cc4b18b7be7c4554ed069151
  • 25c3ab5c1876c19da76aad2c5bedae6c57a0f9fe4ddb33770bf4218e3cf38df9
  • 690eb766f2285650f4af1114f892957efc2934abb3952700cb0b10422d6b5894
  • 1c36f7ac92bf102c5cf7d8b806b33aa28c5a9aac2424822129fc3b1a85929b99
  • 31f629a740474aa63a645e1aca9efe599018af38f00059ca175f360a4ddf73aa
  • 30013130ac961a65b0e6ac8ccf8d1737c4860e4d371942d31b1adf2b0fad80d1
  • 56552a17be57ae23d53b95a3c0b017c41ed02333ac1bea5ac20958e8ecdf92d9
  • 3216f531b117b7745c3512d83dafd1b5811892b70312bec4ff11e8f284ea6fbf
  • 705df2d5d6464f66298782187f5357b83142fd0f768a367f68f045822cc20aeb

JavaScript globals

  • __openCmeSupport
  • __config
  • __theme
  • TradingView
  • addLink
  • addMeta
  • lib
  • rem
  • dpr
  • __VUE_INSTANCE_SETTERS__
  • __VUE_SSR_SETTERS__
  • __INTLIFY_PROD_DEVTOOLS__
  • __INTLIFY_JIT_COMPILATION__
  • __INTLIFY_DROP_MESSAGE_COMPILER__
  • __VUE_I18N_FULL_INSTALL__
  • __VUE_I18N_LEGACY_API__
  • setImmediate
  • clearImmediate
  • PubSub
  • __VUE__
  • __vite_is_modern_browser
  • __cfBeacon

Cookies

  • cme_language

Browser storage keys

  • dev_THEME
  • main
  • dev_LANGUAGE

TLS session and certificate

Subject alternative names
  • *.cme-cmetrad.com
  • cme-cmetrad.com
Cipher
AES_128_GCM
Issuer
YE1
Subject
cme-cmetrad.com
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

5

Registered domain age, days

5

Certificate age, days

6

Certificate validity, days

89

Page requests

74

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
98
Malicious
Yes
Overall verdict
Score
0
Malicious
No

HTTP headers

Server
cloudflare
Content-type
text/html
Strict-transport-security
max-age=31536000
Original source fields · JSON
Uuid
01a1944f-1391-71a8-98e1-24c254cce78e
Final url
https://cme-cmetrad.com/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://cme-cmetrad.com/",
        "from": "http://cme-cmetrad.com/",
        "status": 307
    }
]
Ip
172.67.160.226
Contacted domains
[
    "echo-hkp.oss-cn-hongkong.aliyuncs.com",
    "w5.jiaoyisuo1688.com",
    "static.cloudflareinsights.com"
]
Contacted IP addresses
[
    "8.210.242.86",
    "104.21.36.79",
    "104.16.79.73",
    "172.67.160.226"
]
Asns
[
    "45102",
    "13335"
]
Countries
[
    "HK"
]
Document hash
2fa25a8e3f1bf8847ff8a7399c08daf99a5e96321941915192da5c0fb04204ad
Script hashes
[
    "95a320f6d338a2b0deede53d9db99046fc01a87027b9c2cf96ac2e4bc221c89f",
    "cb0c6c9f1771d252eee7caa043bdd7cfffbd52c2cc4b18b7be7c4554ed069151",
    "25c3ab5c1876c19da76aad2c5bedae6c57a0f9fe4ddb33770bf4218e3cf38df9",
    "690eb766f2285650f4af1114f892957efc2934abb3952700cb0b10422d6b5894",
    "1c36f7ac92bf102c5cf7d8b806b33aa28c5a9aac2424822129fc3b1a85929b99",
    "31f629a740474aa63a645e1aca9efe599018af38f00059ca175f360a4ddf73aa",
    "30013130ac961a65b0e6ac8ccf8d1737c4860e4d371942d31b1adf2b0fad80d1",
    "56552a17be57ae23d53b95a3c0b017c41ed02333ac1bea5ac20958e8ecdf92d9",
    "3216f531b117b7745c3512d83dafd1b5811892b70312bec4ff11e8f284ea6fbf",
    "705df2d5d6464f66298782187f5357b83142fd0f768a367f68f045822cc20aeb"
]
Globals
[
    "__openCmeSupport",
    "__config",
    "__theme",
    "TradingView",
    "addLink",
    "addMeta",
    "lib",
    "rem",
    "dpr",
    "__VUE_INSTANCE_SETTERS__",
    "__VUE_SSR_SETTERS__",
    "__INTLIFY_PROD_DEVTOOLS__",
    "__INTLIFY_JIT_COMPILATION__",
    "__INTLIFY_DROP_MESSAGE_COMPILER__",
    "__VUE_I18N_FULL_INSTALL__",
    "__VUE_I18N_LEGACY_API__",
    "setImmediate",
    "clearImmediate",
    "PubSub",
    "__VUE__",
    "__vite_is_modern_browser",
    "__cfBeacon"
]
Cookies
[
    "cme_language"
]
Storage keys
[
    "dev_THEME",
    "main",
    "dev_LANGUAGE"
]
Tls
{
    "san": [
        "*.cme-cmetrad.com",
        "cme-cmetrad.com"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE1",
    "subject": "cme-cmetrad.com",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-23T21:05:43Z",
    "valid_from": "2026-10-25T21:05:44Z"
}
Domain age days
5
Apex age days
5
Tls age days
6
Tls valid days
89
Requests
74
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 98,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html",
    "strict-transport-security": "max-age=31536000"
}

OTX

2 community references

Open report

Cloudflare Radar

Scan report

Open report
Cloudflare RadarOriginal source recordObserved: 12 fields

Observed: · Retrieved:

Report ID

ac398d24-f108-4edd-981a-289a9970fa3e

Final URL

https://cme-cmetrad.com/

HTTP response

200

Navigation history

  • URL
    https://cme-cmetrad.com/
    Status
    200

DOM structure hash

69fc079bf314f9f494fc9f90a49a22e1a5d45dcf63bf4e96416b54b4649fbdd0

Document hash

2fa25a8e3f1bf8847ff8a7399c08daf99a5e96321941915192da5c0fb04204ad

Domain risk categories

  • Newly Seen Domains
  • Security Risks

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    cme-cmetrad.com
    Type
    A
    Value
    188.114.97.0
  • Name
    cme-cmetrad.com
    Type
    A
    Value
    188.114.96.0
  • Name
    cme-cmetrad.com
    Type
    AAAA
    Value
    2a06:98c1:3121::
  • Name
    cme-cmetrad.com
    Type
    AAAA
    Value
    2a06:98c1:3120::

DNSSEC valid

No

IP address

127.0.1.5

127.0.1.5 is not a public internet address. It is the value stored in this source record, not the site's hosting address.

Registration record

Registrar
Realtime Register B.V.
Registered
Updated
Expires
Nameservers
  • fonzie.ns.cloudflare.com
  • sloan.ns.cloudflare.com
Original source fields · JSON
Uuid
ac398d24-f108-4edd-981a-289a9970fa3e
Final url
https://cme-cmetrad.com/
Status
200
History
[
    {
        "url": "https://cme-cmetrad.com/",
        "status": 200
    }
]
DOM structure hash
69fc079bf314f9f494fc9f90a49a22e1a5d45dcf63bf4e96416b54b4649fbdd0
Document hash
2fa25a8e3f1bf8847ff8a7399c08daf99a5e96321941915192da5c0fb04204ad
Domain risks
[
    "Newly Seen Domains",
    "Security Risks"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "cme-cmetrad.com",
        "type": "A",
        "value": "188.114.97.0"
    },
    {
        "name": "cme-cmetrad.com",
        "type": "A",
        "value": "188.114.96.0"
    },
    {
        "name": "cme-cmetrad.com",
        "type": "AAAA",
        "value": "2a06:98c1:3121::"
    },
    {
        "name": "cme-cmetrad.com",
        "type": "AAAA",
        "value": "2a06:98c1:3120::"
    }
]
Dnssec valid
false
Ip
127.0.1.5

127.0.1.5 is not a public internet address. It is the value stored in this source record, not the site's hosting address.

Registration record
{
    "registrar": "Realtime Register B.V.",
    "created": "2026-10-25T21:59:24Z",
    "updated": "2026-10-25T22:01:28Z",
    "expires": "2027-10-25T21:59:24Z",
    "nameservers": [
        "fonzie.ns.cloudflare.com",
        "sloan.ns.cloudflare.com"
    ]
}

Google Safe Browsing

No threat flag

Open report

PhishDestroy DOM

0 / 100 · heuristic score · 0 brand references · 0 classifications

Open report

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.

ai_title
cme-cmetrad.com Tokyo Commodity Exchange trading page
ai_description
PhishDestroy records the captured cme-cmetrad.com page, which presents itself as a Tokyo Commodity Exchange trading interface.
ai_summary
The captured page presents itself as a Tokyo Commodity Exchange trading interface, headed by a banner reading "TOKYO COMMODITY EXCHANGE" with the subtitle "THE ESSENTIAL GUIDE." Below it, a panel shows three trading pairs with prices and percentage changes, followed by shortcut tiles for pledge mining, second contract, financing, and spot. Two prominent buttons offer quick coin charging and quick withdrawal of coins, and a tabbed list of popular coins repeats the BTC/USDT quote with its latest price and fluctuation range. The stored VirusTotal domain result reports 3 detections out of 92 engines. CRDF reported "malicious"; LevelBlue reported "phishing".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-11-01 01:08:12
revision
acbf36bb43c97a570a76c97d497889c8d928aa27f996fb1c0d68ca17609bf0c4
mode
reviewed
interpretation
Selected public package; text generation time is separate from source observation dates.

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

Every stored field, with its source and date
Website checksOriginal source recordRetrieved: 24 fields

Mail configuration

SPF lookups
0

CAA records

Domain
cme-cmetrad.com

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Web archive observations

Last observation
First observation
Recorded changes
0
Archived days
1
Average page size, bytes
3070

Page title and metadata

Page title
cme-trading
Indexing directives
all
Open Graph image
/platform/dev/logo_144.png?2.0.1747925505872
Open Graph title
cme-trading
Keywords
cme-trading
Theme color
#0b0e12

Trackers

Requests
66

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
2
TLS
60
Waiting
666
Connection
9
Download
0
Response time, ms
737

TLS connection

ALPN
h2
Cipher
TLS_AES_256_GCM_SHA384
Protocol
TLSv1.3
Supported versions
  • TLSv1
  • TLSv1.1
  • TLSv1.2
  • TLSv1.3
Certificate authorized
Yes
Forward secrecy
Yes

Ports

Open ports
  • 80
  • 443
  • 8080

Carbon estimate

Bytes
4931
CO₂, grams
0.0002
Cleaner than, %
87

DNS servers

Nameservers
  • IP address
    108.162.195.70
    Host
    fonzie.ns.cloudflare.com
  • IP address
    108.162.194.52
    Host
    sloan.ns.cloudflare.com
DNS zone
cme-cmetrad.com

Cookies

Cookies
  • Name
    cme_language
    SameSite
    Lax

Location

IP address
2a06:98c1:3120::3
ASN
13335
Organization
CloudFLARENET-EU
City
London
Country
GB

TLS certificate

Issuer
Let's Encrypt / YE1
Subject
cme-cmetrad.com

DNS records

A
  • 188.114.97.3
  • 188.114.96.3
NS
  • fonzie.ns.cloudflare.com
  • sloan.ns.cloudflare.com
SOA
Primary nameserver
fonzie.ns.cloudflare.com
Hostmaster
dns.cloudflare.com
Serial
2418920601
Refresh, seconds
10000
Retry, seconds
2400
Expiry, seconds
604800
Minimum TTL, seconds
1800
AAAA
  • 2a06:98c1:3120::3
  • 2a06:98c1:3121::3

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Header value
max-age=31536000
Observation
HSTS header does not include all subdomains.

HTTP security policies

X-Frame-Options
No
Referrer-Policy
No
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
No
Content-Security-Policy
No
Strict-Transport-Security
max-age=31536000
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

Web application firewall

WAF product
Cloudflare
WAF detected
Yes

IP lookup

IP address
2a06:98c1:3120::3
IP version
6

Redirects

Redirect chain
  • https://cme-cmetrad.com

Registration record

Registrar
Realtime Register B.V.
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
Nameservers
  • fonzie.ns.cloudflare.com
  • sloan.ns.cloudflare.com

HTTP headers

Response headers
Server
cloudflare
Content-type
text/html
Strict-transport-security
max-age=31536000
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "cme-cmetrad.com"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Web archive observations
{
    "last": "2026-10-31T23:34:55Z",
    "first": "2026-10-31T23:34:55Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 3070
}
Page title and metadata
{
    "title": "cme-trading",
    "robots": "all",
    "ogImage": "/platform/dev/logo_144.png?2.0.1747925505872",
    "ogTitle": "cme-trading",
    "keywords": "cme-trading",
    "themeColor": "#0b0e12"
}
Trackers
{
    "requests": 66
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 2,
        "tls": 60,
        "wait": 666,
        "connect": 9,
        "download": 0
    },
    "response_ms": 737
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1",
        "TLSv1.1",
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443,
        8080
    ]
}
Carbon
{
    "bytes": 4931,
    "co2_grams": 0.0002,
    "cleaner_than": 87
}
Dns server
{
    "ns": [
        {
            "ip": "108.162.195.70",
            "host": "fonzie.ns.cloudflare.com"
        },
        {
            "ip": "108.162.194.52",
            "host": "sloan.ns.cloudflare.com"
        }
    ],
    "zone": "cme-cmetrad.com"
}
Cookies
{
    "cookies": [
        {
            "name": "cme_language",
            "same_site": "Lax"
        }
    ]
}
Location
{
    "ip": "2a06:98c1:3120::3",
    "asn": "13335",
    "org": "CloudFLARENET-EU",
    "city": "London",
    "country": "GB"
}
Ssl
{
    "issuer": "Let's Encrypt / YE1",
    "subject": "cme-cmetrad.com"
}
DNS records
{
    "A": [
        "188.114.97.3",
        "188.114.96.3"
    ],
    "NS": [
        "fonzie.ns.cloudflare.com",
        "sloan.ns.cloudflare.com"
    ],
    "SOA": "{\"nsname\": \"fonzie.ns.cloudflare.com\", \"hostmaster\": \"dns.cloudflare.com\", \"serial\": 2418920601, \"refresh\": 10000, \"retry\": 2400, \"expire\": 604800, \"minttl\": 1800}",
    "AAAA": [
        "2a06:98c1:3120::3",
        "2a06:98c1:3121::3"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "header": "max-age=31536000",
    "message": "HSTS header does not include all subdomains."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": "max-age=31536000",
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Firewall
{
    "waf": "Cloudflare",
    "has_waf": true
}
Get ip
{
    "ip": "2a06:98c1:3120::3",
    "family": 6
}
Redirects
{
    "chain": [
        "https://cme-cmetrad.com"
    ]
}
Registration record
{
    "registrar": "Realtime Register B.V.",
    "created": "2026-10-25T21:59:24Z",
    "updated": "2026-10-25T22:01:28Z",
    "expires": "2027-10-25T21:59:24Z",
    "status": [
        "clientTransferProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "fonzie.ns.cloudflare.com",
        "sloan.ns.cloudflare.com"
    ]
}
HTTP headers
{
    "headers": {
        "server": "cloudflare",
        "content-type": "text/html",
        "strict-transport-security": "max-age=31536000"
    }
}

Questions about cme-cmetrad.com

Is cme-cmetrad.com legit?

PhishDestroy records the captured cme-cmetrad.com page, which presents itself as a Tokyo Commodity Exchange trading interface.

Is cme-cmetrad.com safe to connect a wallet?

This report does not record which wallet requests cme-cmetrad.com makes. Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions there. A confirmed blockchain transaction cannot be reversed.

What should I do if I used cme-cmetrad.com?

It depends on what you did. If you entered a password, change it, and also on every other site where you used the same password; turn on two-factor authentication where it is offered. If you paid or gave card or bank details, contact your bank or payment service through the contacts on your card or its official website. If you only connected a wallet, disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds. If you signed a token approval or permit, revoke it with a token-approval checker. If you shared a seed phrase or private key, treat the wallet as compromised and move the remaining funds to a new wallet with a new seed phrase. If you downloaded a file, do not open it and scan the device with security software. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority; a report does not guarantee that money is returned. Step-by-step help: emergency guide.

Explore

Blocklist matchesMetaMask · PhishDestroy · SEAL · no match in the other 9 3
MetaMask Listed View source
PhishDestroy PhishDestroy list View source
SEAL Listed View source

Last checked

Stored Capture · 8 captures

All capture links and hashes (8)

Domain details

Domain
IP Context United Kingdom188.114.96.3 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags activeblocklistcontentcryptodrainerfraudphishdestroyphishingscam
Registrar Realtime
RegistrationCreated Oct 25, 2026 (6d · Brand New!) — Expires Oct 25, 2027
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedNov 1, 2026
DOM Analysisanalyzed Nov 1, 2026score 0/100
Submitted URLhttp://cme-cmetrad.com/
Favicon Hash
Observed page title
cme-trading
TLS Certificate
Issued by YE1 · stored validity ends in 83 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
United Kingdom188.114.96.3
Network ASN
AS13335
Organization
CloudFLARENET-EU
Observed location
United KingdomLondon, GB
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • fonzie.ns.cloudflare.com
  • sloan.ns.cloudflare.com

SOA

  • nsname: fonzie.ns.cloudflare.com
  • hostmaster: dns.cloudflare.com
  • serial: 2418920601
  • refresh: 10000
  • retry: 2400
  • expire: 604800
  • minttl: 1800

Registrar abuse contact VirusTotal WHOIS

Location describes the IP network.

TLS certificate

Issuer
YE1
Valid from
2026-10-25 21:05:44
Valid until
2027-01-23 21:05:43
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint0936e8805db5daf9faf244803f2ead81a9a2bdfd2552ebade86cf65139f7b14a
Certificate names · 2 SANs
  • *.cme-cmetrad.com
  • cme-cmetrad.com

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

Report This Domain Submit evidence & help protect others

VirusTotal Analysis

3 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection
CRDF
Forcepoint ThreatSeeker
LevelBlue

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of cme-cmetrad.com · checked Nov 1, 2026

66
Needs Work
Performance
FCP
1.39 s
First Contentful Paint
LCP
11.32 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
11 ms
Total Blocking Time
SI
9.85 s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: http://cme-cmetrad.com/
cme-trading
Response
HTTP 200
HTML body
4.8 KB
Compressed
1.7 KB
Links
0 internal · 0 external
Detected technologies
cloudflare
Selected response headers
Content-Type: text/html
Server: cloudflare
CF-Cache-Status: DYNAMIC
Content-Encoding: gzip
Security headers present
Strict-Transport-Security
HSTS: observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Favicon fingerprint: 973c5a83c751f168437e3b261dbd6e939123a9908a711cbed65f18d74696a62d
Open Graph title: cme-trading
Saved response-header values · 14
Alt-Svc
h3=":443"; ma=86400
cf-cache-status
DYNAMIC
CF-RAY
a53678970a1ad2e3-FRA
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html
Date
Sat, 31 Oct 2026 23:34:33 GMT
Last-Modified
Sat, 31 Oct 2026 07:55:03 GMT
Nel
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=OB9oycCa4j7RKHEr5eoFx%2Fvx5TRXH9ifikpL5HBTgKyOBYeOZjVdnACvPqBlggN4lCzFoVf2UGUVgXHdzanToAfgKctZwnG%2B1ST19Ko0ne9pCQ3naMotHqJJEc4Gv6gWl%2Bw%3D"}]
Server
cloudflare
Strict-Transport-Security
max-age=31536000
Transfer-Encoding
chunked
Vary
Accept-Encoding

Values retained by the collector; long values may be shortened during collection.

Registration & observation details1

Availability observations

Last reachable observation

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

Captured network requests

Network requests: 74 SHA-256 hashes: 62 URLScan scan:

Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-10-31 23:34 UTC.

Open this scan on URLScan 01a1944f-1391-71a8-98e1-24c254cce78e ↗

Stored observation history1

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

  1. Domain monitor · First collection record

    Reachable

Separate monitor HTTP observation

Source: domain_monitor. This stored snapshot does not establish current availability.

Observed · UTC
Recorded HTTP status
200
Probe value as recorded
200
Original source timestamp
2026-11-01 00:28:17
All retained availability observations3

Source: availability monitor. Every retained observation remains separate, including records with the same date or evidence hash but different sources or DNS states. An unknown state is not proof that the site is offline.

  1. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    40
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 00:33:51.000000
    Evidence SHA-256
    44ce40635a37b34b5d78f142cf6eed82f5d6ccbd434227d077b5bd0359f2db5f
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 00:33:51
    Evidence reason
  2. http_observationunknown
    Observation source
    http_observation
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    40
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 00:33:51.000000
    Evidence SHA-256
    44ce40635a37b34b5d78f142cf6eed82f5d6ccbd434227d077b5bd0359f2db5f
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 00:33:51
    Evidence reason
  3. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 23:31:41.538396
    Evidence SHA-256
    d507886309fe7925b612af112c97b5593f8ff1d1bd6793149e30d59a14244ced
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-31 23:31:41.538396
    Evidence reason

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Monitoring · in progress

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

Pre-emptive Discovery & IngestionThreat Ingested Recorded: 1 of 1
  • Threat Ingested
    cme-cmetrad.com detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · Blocklist Detection · OTX Community References · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 9 of 9
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 98
  • Cloudflare Radar Report
    A stored Cloudflare Radar report is available. The report link alone does not mean that the domain was classified as malicious, and it does not prove that every network field was captured.
  • Web Archive
    Preserved in the Wayback Machine: historical evidence archived
  • VirusTotal
    Detections recorded on VirusTotal: 3/92
  • Blocklist Detection
    Found in blocklists: MetaMask, SEAL
  • OTX Community References
    Community publication references on AlienVault OTX: 2. References are not vendor verdicts and are excluded from the evidence score.
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
Publication & AvailabilityDestroyList Published · Monitoring Continues Recorded: 1 of 2
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.

Recorded activity

5 entries
  1. AlienVault OTX

    2 community references

    View source
  2. Wayback Machine

    Page archived

    View source
  3. Added to PhishDestroy

    cme-cmetrad.com

    View source
  4. URLScan

    Page captured

    View source
  5. VirusTotal

    3/92 engine detections

    View source
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.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

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.

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

cme-cmetrad.com

Evidence & External Reports

Deep Analysis
Help & reporting

Were You Affected by This Site?

4 evidence signal groups linked Last known active
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Silence is the scammer’s greatest advantage. Break it.
If credentials were compromised, report immediately. Do not engage with recovery scammers.

Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.

Official reporting routes

More official reporting routes
FTC ReportFraud United States

Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.

IdentityTheft.gov United States

Official identity theft report with a step-by-step recovery plan.

CISA United States

Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.

CSIRTs Network European Union

Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.

FIRST Worldwide

Worldwide directory of incident response teams, searchable by country and sector.

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

Report scams to the National Anti-Scam Centre run by the ACCC.

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

If you made a payment, contact your bank or payment service through its official contacts as soon as possible. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned.

Scammers are criminals. Filing a report creates a legal record and helps protect others.

97-country directory

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

Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website

What information should I collect for my report?

FBI guidelines

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.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including cme-cmetrad.com)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?

  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

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?

  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?

  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

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

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →
About this reportSources, observation dates and corrections

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.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html
<iframe
  src="https://phishdestroy.io/embed/domain/cme-cmetrad.com"
  title="PhishDestroy threat report for cme-cmetrad.com"
  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>