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

kidamex.com

In short

kidamex.com is a MEXC impersonation page detected by PhishDestroy on 2026-10-25.

Registrar
Dynadot
Resolved IP
188.114.97.1
Registered
Oct 22, 2026
PhishDestroy assessment Critical
81/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
VirusTotal detections: 1/92 Automated brand label: MEXC Scam type: Impersonation Young domain: 4 days old
VirusTotal
engine detections ·
OTX
community references
Cloudflare Radar
source verdict
Page captures
open gallery
Domain age
Oct 25, 2026 CDN
X Telegram API

Analysis

Domain summary

kidamex.com is a MEXC impersonation page detected by PhishDestroy on 2026-10-25. Risk: critical (81/100). Registrar: Dynadot. Status: Last known active. Hosting: Cloudflare, Inc. VirusTotal: 1/92 engines flag it. Do not enter credentials or connect a wallet.

Critical
VirusTotal
1 / 92
Page captures
2

PhishDestroy threat report

Overview

PhishDestroy added kidamex.com to its internal blocklist on 2026-10-25. The intake reason cited a trusted report noting the domain was only two days old and that page content was insufficient for analysis. An HTTP request on the same day returned a 307 redirect from http to https and an unusual status code 666. A separate urlscan capture on 2026-10-24 reported the page as clean.

How the scam works

The listing is based on the domain’s recent creation, lack of visible content, and a single suspicious label from a security engine, which together raise the possibility of phishing, fraud or malware distribution. No specific malicious behavior was observed on the captured page, so the risk remains speculative and should be treated as a generic suspicious web resource.

Evidence

VirusTotal scanned the domain on 2026-10-24 and recorded one suspicious detection out of 92 engines, flagged by Gridinsoft. Google Safe Browsing checked the domain on 2026-10-25 and did not flag it. urlscan.io captured the site on 2026-10-24 and returned a clean verdict with no malicious score. OTX reported zero pulses as of 2026-10-25, and external blocklists showed no entries for the domain on that date. PhishDestroy’s own internal blocklist marks the domain as listed.

Infrastructure

The domain was registered with Dynadot Inc on 2026-10-22 and carried a clientTransferProhibited status. The recorded DNS records showed Cloudflare‑managed IP addresses 188.114.96.3 and 188.114.97.1, and the captured TLS 1.3 certificate from Let’s Encrypt was valid until 2027-01-20.

What to do

Treat kidamex.com as potentially malicious; avoid entering credentials, personal data, or cryptocurrency information on the site. If any credentials were submitted, change the associated passwords and monitor the accounts for unauthorized activity. Defenders should block the domain at the network perimeter, log DNS queries to the observed IPs, and keep the domain on threat‑intel watchlists.

Source evidenceVirusTotal 1 / 92 7 sources

VirusTotal

1 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
54
Malicious
0
Suspicious
1
Undetected
37

Vendor labels

Gridinsoft
suspicious

Reputation score

0

Registrar

Dynadot Inc

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    21600
    Type
    NS
    Value
    sonia.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    A
    Value
    172.67.195.138
  • TTL, seconds
    1800
    Type
    SOA
    Responsible mailbox
    dns.cloudflare.com
    Value
    bowen.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    A
    Value
    104.21.68.128
  • TTL, seconds
    21600
    Type
    NS
    Value
    bowen.ns.cloudflare.com

DNS records observed

JARM fingerprint

27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c

Certificate

Subject alternative names
  • *.kidamex.com
  • kidamex.com
Issuer
Let's Encrypt / YE1
Serial
661e0e27ab1c79abe24c086fc35f3104379
SHA-256
e547c3388c84e9a4acc89fd086aba4c85d00c2d4fa72c9784ace5196e07cad30
Subject
kidamex.com
Valid until
Valid from

Registration record

Registrar
Dynadot Inc
Registrar IANA ID
472
Registrar URL
http://www.dynadot.com
Registered
Updated
Expires
Status
  • clientTransferProhibited
Nameservers
  • bowen.ns.cloudflare.com
  • sonia.ns.cloudflare.com
DNSSEC
unsigned

Registry data (RDAP)

Status
  • transfer prohibited
Registry events
Expiration
Last changed
Registration
Registrar expiration
Last RDAP database update
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 54,
    "malicious": 0,
    "suspicious": 1,
    "undetected": 37
}
Vendor labels
{
    "Gridinsoft": "suspicious"
}
Reputation
0
Registrar
Dynadot Inc
Created
2026-10-22T16:14:51Z
Expires
2027-10-22T16:14:51Z
Updated
2026-10-22T16:25:44Z
First seen
2026-10-23T00:30:45Z
DNS records
[
    {
        "ttl": 21600,
        "type": "NS",
        "value": "sonia.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "172.67.195.138"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "bowen.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "104.21.68.128"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "bowen.ns.cloudflare.com"
    }
]
Dns at
2026-10-24T21:35:43Z
Jarm
27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c
Certificate
{
    "san": [
        "*.kidamex.com",
        "kidamex.com"
    ],
    "issuer": "Let's Encrypt / YE1",
    "serial": "661e0e27ab1c79abe24c086fc35f3104379",
    "sha256": "e547c3388c84e9a4acc89fd086aba4c85d00c2d4fa72c9784ace5196e07cad30",
    "subject": "kidamex.com",
    "valid_to": "2027-01-20T15:32:58Z",
    "valid_from": "2026-10-22T15:32:59Z"
}
Registration record
{
    "registrar": "Dynadot Inc",
    "registrar_iana_id": "472",
    "registrar_url": "http://www.dynadot.com",
    "created": "2026-10-22T16:14:51Z",
    "updated": "2026-10-22T16:25:44Z",
    "expires": "2027-10-22T16:14:51Z",
    "status": [
        "clientTransferProhibited"
    ],
    "nameservers": [
        "bowen.ns.cloudflare.com",
        "sonia.ns.cloudflare.com"
    ],
    "dnssec": "unsigned"
}
Registry data
{
    "status": [
        "transfer prohibited"
    ],
    "events": {
        "expiration": "2027-10-22T16:14:51Z",
        "last changed": "2026-10-22T16:25:45Z",
        "registration": "2026-10-22T16:14:51Z",
        "registrar expiration": "2027-10-22T16:14:51Z",
        "last update of RDAP database": "2026-10-22T16:26:08Z"
    }
}
Separate source record · 0 malicious + 1 suspicious / 92 · 2026-10-24 21:35:29 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-24T21:35:29Z
fetched_at
2026-10-25T03:49:50Z
stats
{"timeout":0,"harmless":54,"malicious":0,"suspicious":1,"undetected":37}

OTX

no community references

Open report

Cloudflare Radar

provider verdict: clean

Open report
Cloudflare RadarOriginal source recordObserved: 1 field

Observed: · Retrieved:

Report ID

2d048a40-491f-4e9b-a397-75df14f37b62
Original source fields · JSON
Uuid
2d048a40-491f-4e9b-a397-75df14f37b62

Google Safe Browsing

No threat flag

Open report

URLScan

No malicious flag

SHA-256 c7b006d298f44396f85e4ce96376dc37e4cb9d06340ccd5b890c6f737f967205

Open report
URLScanOriginal source recordObserved: 19 fields

Observed: · Retrieved:

Report ID

01a16fe4-b9e2-7144-9aca-20b1bc57c311

Final URL

https://kidamex.com/

HTTP response

666

Redirect type

https-only

Redirects

  • To
    https://kidamex.com/
    From
    http://kidamex.com/
    Status
    307

IP address

188.114.96.3

Contacted domains

  • static.cloudflareinsights.com
  • www.google.com

Contacted IP addresses

  • 104.16.80.73
  • 188.114.96.3

Autonomous systems (ASN)

  • 13335

Document hash

2cb7dea096dd8f36d1ecf9a45372216841aee434491abce61f59ad40b07efb10

Script hashes

  • 0bf32f6f5e0db7af1e5c2bf8701b0dda03b6b9fc7f09c66755a85200506b3a0b

TLS session and certificate

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

Domain age, days

0

Registered domain age, days

0

Certificate age, days

2

Certificate validity, days

89

Page requests

7

Provider verdicts

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

HTTP headers

Server
cloudflare
Content-type
text/html; charset=utf-8
Original source fields · JSON
Uuid
01a16fe4-b9e2-7144-9aca-20b1bc57c311
Final url
https://kidamex.com/
Status
666
Redirected
https-only
Redirects
[
    {
        "to": "https://kidamex.com/",
        "from": "http://kidamex.com/",
        "status": 307
    }
]
Ip
188.114.96.3
Contacted domains
[
    "static.cloudflareinsights.com",
    "www.google.com"
]
Contacted IP addresses
[
    "104.16.80.73",
    "188.114.96.3"
]
Asns
[
    "13335"
]
Document hash
2cb7dea096dd8f36d1ecf9a45372216841aee434491abce61f59ad40b07efb10
Script hashes
[
    "0bf32f6f5e0db7af1e5c2bf8701b0dda03b6b9fc7f09c66755a85200506b3a0b"
]
Tls
{
    "san": [
        "*.kidamex.com",
        "kidamex.com"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE1",
    "subject": "kidamex.com",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-20T15:32:58Z",
    "valid_from": "2026-10-22T15:32:59Z"
}
Domain age days
0
Apex age days
0
Tls age days
2
Tls valid days
89
Requests
7
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": -8,
        "malicious": false
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html; charset=utf-8"
}
Separate monitor record · 2026-10-25 04:30 UTC

Separate stored monitor snapshot; does not replace the primary report record or establish current availability.

record_source
domain_monitor.urlscan
uuid
01a16fe4-b9e2-7144-9aca-20b1bc57c311
score
0
malicious
false
result_at
2026-10-25T04:30:50Z
enriched_at
2026-10-26T09:20:16Z
source_timestamps
{"urlscan_result_at":"2026-10-25 05:30:50","urlscan_enriched_at":"2026-10-26 10:20:16"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

Spamhaus DBL

Check recorded; verdict not retained

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
kidamex.com — Suspicious Domain
ai_description
PhishDestroy flagged kidamex.com as a suspicious domain after it was first seen on 2026-10-25, with limited page content and a VirusTotal‑suspicious label.
ai_generated_at
2026-10-25T03:55:02Z
ai_generated_by
threat-v3-groq
interpretation
Narrative generation metadata, separate from provider 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: 15 fields

Mail configuration

SPF lookups
0

CAA records

Domain
kidamex.com

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

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

DNS servers

Nameservers
  • IP address
    172.64.34.190
    Host
    sonia.ns.cloudflare.com
  • IP address
    162.159.44.83
    Host
    bowen.ns.cloudflare.com
DNS zone
kidamex.com

Location

IP address
188.114.96.3
ASN
13335
Organization
Cloudflare, Inc.
City
Toronto
Country
CA

TLS certificate

Issuer
Let's Encrypt / YE1
Subject
kidamex.com

DNS records

A
  • 188.114.96.3
  • 188.114.97.3
NS
  • sonia.ns.cloudflare.com
  • bowen.ns.cloudflare.com
SOA
Primary nameserver
bowen.ns.cloudflare.com
Hostmaster
dns.cloudflare.com
Serial
2418197245
Refresh, seconds
10000
Retry, seconds
2400
Expiry, seconds
604800
Minimum TTL, seconds
1800

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Observation
Site does not serve any HSTS headers.

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
No
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
188.114.96.3
IP version
4

Registration record

Registrar
Dynadot Inc
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
Nameservers
  • bowen.ns.cloudflare.com
  • sonia.ns.cloudflare.com
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "kidamex.com"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
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
    ]
}
Dns server
{
    "ns": [
        {
            "ip": "172.64.34.190",
            "host": "sonia.ns.cloudflare.com"
        },
        {
            "ip": "162.159.44.83",
            "host": "bowen.ns.cloudflare.com"
        }
    ],
    "zone": "kidamex.com"
}
Location
{
    "ip": "188.114.96.3",
    "asn": "13335",
    "org": "Cloudflare, Inc.",
    "city": "Toronto",
    "country": "CA"
}
Ssl
{
    "issuer": "Let's Encrypt / YE1",
    "subject": "kidamex.com"
}
DNS records
{
    "A": [
        "188.114.96.3",
        "188.114.97.3"
    ],
    "NS": [
        "sonia.ns.cloudflare.com",
        "bowen.ns.cloudflare.com"
    ],
    "SOA": "{\"nsname\": \"bowen.ns.cloudflare.com\", \"hostmaster\": \"dns.cloudflare.com\", \"serial\": 2418197245, \"refresh\": 10000, \"retry\": 2400, \"expire\": 604800, \"minttl\": 1800}"
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Firewall
{
    "waf": "Cloudflare",
    "has_waf": true
}
Get ip
{
    "ip": "188.114.96.3",
    "family": 4
}
Registration record
{
    "registrar": "Dynadot Inc",
    "created": "2026-10-22T16:14:51Z",
    "updated": "2026-10-22T16:25:44Z",
    "expires": "2027-10-22T16:14:51Z",
    "status": [
        "clientTransferProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "bowen.ns.cloudflare.com",
        "sonia.ns.cloudflare.com"
    ]
}

Questions about kidamex.com

Is kidamex.com legit?

No. PhishDestroy classifies kidamex.com as a MEXC impersonation page (risk: critical, 81/100); it was first detected on 2026-10-25. VirusTotal: 1/92 engines flag it. Treat the site as unsafe.

Is kidamex.com safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on kidamex.com. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.

What should I do if I used kidamex.com?

Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.

Explore

Blocklist matchesPhishDestroy · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Last checked

Stored Capture · 2 captures

All capture links and hashes (2)
kidamex.com: Suspected MEXC impersonation — 1/92 VirusTotal engines. PhishDestroy risk score 81/100 (critical).
Social preview card kidamex.com: Suspected MEXC impersonation — 1/92 VirusTotal engines. PhishDestroy risk score 81/100 (critical). v f99244b00a90

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar Dynadot US(US)
RegistrationCreated Oct 22, 2026 (4d · Brand New!) — Expires Oct 22, 2027
HTTP Status301 Moved Permanently
Technical detailsProvenance & timestamps
First DetectedOct 25, 2026
Submitted URLhttp://kidamex.com/
Favicon Hash
TLS Certificate
Issued by Let's Encrypt / YE1 · stored validity ends in 85 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
188.114.97.1
Network ASN
AS13335
AS name
CLOUDFLARENET - Cloudflare, Inc., US
Organization
Cloudflare, Inc.
Observed location
Toronto, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • bowen.ns.cloudflare.com
  • sonia.ns.cloudflare.com

SOA

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

Registrar abuse contact VirusTotal WHOIS

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE1
Valid from
2026-10-22 15:32:59
Valid until
2027-01-20 15:32:58
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprinte547c3388c84e9a4acc89fd086aba4c85d00c2d4fa72c9784ace5196e07cad30
Certificate names · 2 SANs
  • *.kidamex.com
  • kidamex.com

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-25 23:00:36 UTC

The site was redirecting visitors elsewhere at the latest check.

Technical details
Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Redirecting Content: Unknown DNS: Stale Registration: Unknown
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-10-25 23:00:36 UTC
RDAP registration
Observed timeline last reachable: 2026-10-25 23:00:36 UTC
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.
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

1 / 92 security vendors flagged this domain
View on VT
Last analyzed
Gridinsoft
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
Requested URL: http://kidamex.com/
Final URL: https://kidamex.com/
HTML body
5.0 KB
Compressed
2.4 KB
Links
0 internal · 0 external
Detected technologies
cloudflare
Selected response headers
Content-Type: text/html; charset=utf-8
Server: cloudflare
Cache-Control: no-store, no-cache, must-revalidate, max-age=0
CF-Cache-Status: DYNAMIC
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Saved response-header values · 12
Cache-Control
no-store, no-cache, must-revalidate, max-age=0
CasT-Mode
default
cf-cache-status
DYNAMIC
CF-RAY
a4fe3cf71bdc9174-FRA
Connection
keep-alive
Content-Type
text/html; charset=utf-8
Date
Sun, 25 Oct 2026 03:47:08 GMT
Nel
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Pragma
no-cache
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=2Fv9a6qGTcpHKjiHNP%2FAobYGn8q1E1KwYw6dU3PecTbGGEhhhpu%2FpvAY1%2F398%2FCORfvV3BZzR32zOhQDPNKWrXJ0uLdIM53hkzjpgx%2BGM4i4XIZtqS9e4%2BjSK1YAnQ%3D%3
Server
cloudflare
Transfer-Encoding
chunked

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

Registration & observation details2

Availability observations

Last reachable observation
Estimate basis
Currently reachable

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

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. Availability monitor · Recorded state

    redirected

    http_redirect

All retained availability observations5

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_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 00:00:36.000000
    Evidence SHA-256
    0e2e0f7d465b1502a27b6ce4a7861a1f50470248f8a4c0acefbcf6c38fc71ac3
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-26 00:00:36
    Evidence reason
    redirect
  2. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 00:00:36.000000
    Evidence SHA-256
    0e2e0f7d465b1502a27b6ce4a7861a1f50470248f8a4c0acefbcf6c38fc71ac3
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-26 00:00:36
    Evidence reason
    redirect
  3. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 12:00:27.000000
    Evidence SHA-256
    9e31d46bfa757df42c87882b0dac5a6697fe93b96e6907c45628470b736fd50c
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-25 12:00:27
    Evidence reason
    redirect
  4. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 12:00:27.000000
    Evidence SHA-256
    9e31d46bfa757df42c87882b0dac5a6697fe93b96e6907c45628470b736fd50c
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-25 12:00:27
    Evidence reason
    redirect
  5. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 04:54:19.950362
    Evidence SHA-256
    f3049ef8aa957a0c75d1f37b703ae6008630522768f5aca88bbd9915c9e1400b
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true

Threat Response Pipeline

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

Recorded events: 7. 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
    kidamex.com detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · Cloudflare Radar Report · VirusTotal · Brand Impersonation · Forensic Evidence Collected Recorded: 5 of 5
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • 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.
  • VirusTotal
    Detections recorded on VirusTotal: 1/92
  • Brand Impersonation
    Automated brand label: MEXC
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
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

2 entries
  1. VirusTotal

    1/92 engine detections

    View source
  2. Added to PhishDestroy

    kidamex.com

    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.

kidamex.com

Evidence & External Reports

Deep Analysis
Help & reporting

Were You Affected by This Site?

3 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.

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

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 →.

Even if funds were frozen, they cannot be recovered without an official police report or court order. Submitting a complaint is the only path to potential recovery.

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.

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

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 kidamex.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/kidamex.com"
  title="PhishDestroy threat report for kidamex.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>