Skip to security report
Domain security and threat intelligence
crptmoy.com favicon

crptmoy.com

In short

crptmoy.com is a Crypto.com impersonation page detected by PhishDestroy on 2026-09-04. Risk: critical (100/100). Registrar: Realtime. Status: Content unavailable. Hosting: Cloudflare, Inc. PhishDestroy sent 1 abuse report. VirusTotal: 8/90 engines flag it. Google Safe Browsing flags it. Do not enter credentials or connect a wallet.

“Crypto.com”

Registrar
Realtime
Resolved IP
188.114.96.3
Registered
Jul 30, 2026
PhishDestroy assessment Critical
Availability Content unavailable Content was unavailable in the latest observation Observed · HTTP probe
VirusTotal detections: 8/90 Stored blocklist matches: 2 URLQuery threat systems: 1 alert Automated brand label: Crypto.com Google Safe Browsing: threat flag recorded
OTX: 6 refs Sep 4, 2026 1 Report Sent CDN
API
This domain has been flagged as malicious
Security engines reporting a detection: 8. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
engine detections
Google Safe Browsing
URLQuery
threat alerts
OTX
community references
Page captures
open gallery
Domain age
Reports sent
view timeline
Source evidenceVirusTotal 8 / 90 · Google Safe Browsing: flagged · OTX 6 references 6 sources

VirusTotal

8 / 90 engine detections

Open report

URLQuery

1 threat-system alert

Open report

Google Safe Browsing

Threat flag recorded

Open report

OTX

6 community references

Open report

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

Network Security Intelligence
Threat Detection Systems 1 alert
Detection System Indicator Verdict Alert
DNS4EU crptmoy.com malicious Sinkholed

Analysis

Critical
VirusTotal
8 / 90
OTX
6 community refs
Page captures
6

PhishDestroy threat report

Overview

crptmoy.com is an impersonation phishing page that presented itself simply as "Crypto.com", the title shown in the browser tab. Its name is a compressed misspelling of the brand, aimed at Crypto.com customers who mistype the address or follow a link without reading it closely. PhishDestroy first flagged it on 2026-09-04. The site has been dead since 2026-09-11, and on 2026-10-19 its domain no longer resolved in DNS.

How the scam works

Lookalike exchange pages like this copy the branding and login flow of the real service so the visitor believes they are signing in to Crypto.com. Anything typed in goes to the operators: email, password, one-time 2FA codes and sometimes a wallet recovery phrase. With those, attackers log in to the genuine account in real time, change security settings and withdraw the balance. A captured recovery phrase gives them the wallet outright.

Evidence

Eight of 90 VirusTotal engines flagged the domain on 2026-09-04: alphaMountain.ai, Forcepoint ThreatSeeker, Fortinet, Google Safe Browsing, Gridinsoft, LevelBlue, Lionic and SOCRadar. That is a modest count, but it includes Google Safe Browsing, which listed the site under SOCIAL_ENGINEERING and drives warnings in Chrome and other major browsers. urlscan.io returned a malicious verdict and tagged the page as a crypto scam. The domain is also on the MetaMask and SEAL blocklists alongside PhishDestroy, and it appears in six AlienVault OTX threat pulses.

Infrastructure

The domain was registered on 2026-07-30 through Realtime Register B.V. and sat for about five weeks before it surfaced as phishing, a gap that fits a domain bought ahead of a campaign. Traffic ran through Cloudflare, Inc. on an address geolocated to Canada. Cloudflare acts as a front, so this location reflects the proxy rather than the operators' own server.

What to do

If you entered your Crypto.com login on this site, open the official app right away. Change your password, reset 2FA, sign out all other sessions and review recent withdrawals and whitelisted addresses. Contact Crypto.com support about any activity you did not make. If you typed a recovery phrase, treat that wallet as compromised and move the funds to a new wallet created from a fresh phrase. If you connected a wallet, revoke any approvals granted around that time. Defenders should block the domain, search mail and proxy logs for earlier visits from their users, and watch for similarly compressed Crypto.com lookalikes.

Collected source details

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

URLScan · 2026-09-04T15:59:48Z

Observed: · Retrieved:

Uuid
01a06d25-a9a2-7624-9126-b4bbe53ac001
Final url
https://crptmoy.com/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://crptmoy.com/",
        "from": "http://crptmoy.com/",
        "status": 307
    }
]
Ip
188.114.97.3
Contacted domains
[
    "esch20.oss-ap-southeast-1.aliyuncs.com",
    "echang-bucket.oss-accelerate.aliyuncs.com"
]
Contacted IP addresses
[
    "47.79.49.183",
    "47.254.187.158",
    "188.114.97.3"
]
Asns
[
    "45102",
    "13335"
]
Countries
[
    "SG",
    "DE"
]
Document hash
129394071950b7f1044fe5cd73b20c40611ef59cdacd8c147a008e30f17608b7
Script hashes
[
    "bcee984fd52b4a82bd6b23543bb33f6472e076c125edbdd8756d29ca230628cb",
    "ba302acc88913f80066015d4a5fadec2a4e8e48316b09c7cca1949138da35701",
    "b18ac13a8d81ffbd5ed41226551cac5baa4c89922e2857009724e88099e22096",
    "0741e2d7016a49351dee13f11c13e251e3cf7f9dc6bd6e3c8239fc2e8b65ec7b",
    "711bcb3ed4a7b1490b4fb467f6b1553ad56d885e6020dc4e1a7f14d14742b87f",
    "19b6064253aa9f5cf884171dac000919f3826dd71574f9fd9aee37fe5f1db2a6",
    "89b58597a2ed145503723057e62be884247242c6216f8055e40bd3ad3063b39b",
    "7cacc8b54c2056ad18df4a0d3ee2161e520b54fc1e017a0f34eb5e4d80b0198a",
    "4abf2b61074bac344dfd0382faa443e7312f64db44cfdf12969cab179fe5b46d",
    "f0be27efd14854cda28c2c6b1b46da6b23675919e4c81eeec884bc34e58bc27e"
]
Globals
[
    "TradingView",
    "addLink",
    "addMeta",
    "lib",
    "rem",
    "dpr",
    "__VUE_INSTANCE_SETTERS__",
    "__INTLIFY_PROD_DEVTOOLS__",
    "__INTLIFY_JIT_COMPILATION__",
    "__INTLIFY_DROP_MESSAGE_COMPILER__",
    "__VUE_I18N_FULL_INSTALL__",
    "__VUE_I18N_LEGACY_API__",
    "setImmediate",
    "clearImmediate",
    "PubSub",
    "__config",
    "Buffer",
    "__theme",
    "__VUE__",
    "__vite_is_modern_browser"
]
Storage keys
[
    "Crypto.com_THEME",
    "main",
    "Crypto.com_LANGUAGE"
]
Tls
{
    "san": [
        "crptmoy.com",
        "*.crptmoy.com"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WE1",
    "subject": "crptmoy.com",
    "protocol": "QUIC",
    "valid_to": "2026-10-28T16:40:04Z",
    "valid_from": "2026-07-30T15:42:28Z"
}
Domain age days
35
Apex age days
35
Tls age days
36
Tls valid days
90
Requests
77
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 99,
        "malicious": true
    },
    "overall": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "cryptoscam"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    },
    "urlscan": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "Crypto Scam"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html"
}
Cloudflare Radar · 2026-09-04T16:36:22Z

Observed: · Retrieved:

Uuid
f9bf0d99-df9f-410d-b91d-7870e9637250
Final url
https://crptmoy.com/
Status
200
History
[
    {
        "url": "https://crptmoy.com/",
        "status": 200
    }
]
DOM structure hash
5b80b35bc5887aebef36a8cc4d26f12f5cea7b965ef900ec57de7b761908df5d
Document hash
655d73a444a17cbe84effb766b5b7ad8282823e3c4f9fe913204e2b3adc622dd
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "crptmoy.com",
        "type": "A",
        "value": "104.21.41.49"
    },
    {
        "name": "crptmoy.com",
        "type": "A",
        "value": "172.67.160.171"
    },
    {
        "name": "crptmoy.com",
        "type": "AAAA",
        "value": "2606:4700:3031::ac43:a0ab"
    },
    {
        "name": "crptmoy.com",
        "type": "AAAA",
        "value": "2606:4700:3037::6815:2931"
    }
]
Dnssec valid
false
Ip
104.21.41.49
Registration record
{
    "registrar": "Realtime Register B.V.",
    "created": "2026-07-30T16:38:19Z",
    "updated": "2026-07-30T16:39:20Z",
    "expires": "2027-07-30T16:38:19Z",
    "nameservers": [
        "pat.ns.cloudflare.com",
        "piers.ns.cloudflare.com"
    ]
}
VirusTotal · 2026-10-16T21:06:19Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 46,
    "malicious": 11,
    "suspicious": 1,
    "undetected": 34
}
Vendor labels
{
    "CRDF": "malicious",
    "ESET": "suspicious",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "malware",
    "Fortinet": "phishing",
    "SOCRadar": "phishing",
    "BitDefender": "phishing",
    "alphaMountain.ai": "phishing",
    "Google Safe Browsing": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Tags
[
    "dga"
]
Categories
{
    "alphaMountain.ai": "Phishing, Newly Registered (alphaMountain.ai)"
}
Registrar
Realtime Register B.V.
Created
2026-07-30T16:38:19Z
Expires
2027-07-30T16:38:19Z
Updated
2026-09-28T16:38:42Z
First seen
2026-07-30T17:42:22Z
DNS records
[
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3037::6815:2931"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "172.67.160.171"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3031::ac43:a0ab"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "piers.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "104.21.41.49"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "pat.ns.cloudflare.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "pat.ns.cloudflare.com"
    }
]
Dns at
2026-09-01T00:02:56Z
Jarm
27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c
Certificate
{
    "san": [
        "crptmoy.com",
        "*.crptmoy.com"
    ],
    "issuer": "Google Trust Services / WE1",
    "serial": "16fa96234d5c90d713b6787c25f27514",
    "sha256": "584f5616124b634a12e4860db2503a588c8cecf6a1ff5a1302e6ab70cbbf0300",
    "subject": "crptmoy.com",
    "valid_to": "2026-10-28T16:40:04Z",
    "valid_from": "2026-07-30T15:42:28Z"
}
Registration record
{
    "registrar": "Realtime Register B.V.",
    "registrar_iana_id": "839",
    "registrar_url": "http://www.realtimeregister.com",
    "created": "2026-07-30T16:38:19Z",
    "updated": "2026-09-28T16:38:42Z",
    "expires": "2027-07-30T16:38:19Z",
    "status": [
        "clientHold"
    ],
    "nameservers": [
        "pat.ns.cloudflare.com",
        "piers.ns.cloudflare.com"
    ],
    "dnssec": "unsigned"
}
Registry data
{
    "status": [
        "active"
    ],
    "events": {
        "expiration": "2027-07-30T16:38:19Z",
        "last changed": "2026-09-28T16:38:43Z",
        "registration": "2026-07-30T16:38:19Z",
        "registrar expiration": "2027-07-30T16:38:19Z",
        "last update of RDAP database": "2026-10-12T11:02:44Z"
    }
}

Questions about crptmoy.com

Is crptmoy.com legit?

No. PhishDestroy classifies crptmoy.com as a Crypto.com impersonation page (risk: critical, 100/100); it was first detected on 2026-09-04. VirusTotal: 8/90 engines flag it. Google Safe Browsing flags it. Treat the site as unsafe.

Is crptmoy.com safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on crptmoy.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 crptmoy.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 matchesMetaMask · PhishDestroy · SEAL 3
MetaMask Listed View source
PhishDestroy PhishDestroy list View source
SEAL Listed View source

Last checked

Stored Capture · 6 captures

Domain details

Domain
URLScan verdict Malicious score 100 Phishing report ↗
Google Safe Browsing Flagged Social engineering checked Sep 11, 2026
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags 2026-09activeall-domainsblocklistcontentcryptocrypto scamcyrpto scamdomainsdrainerfraudlivemonthlyphishdestroy+2 more
Registrar Realtime (Unknown)
RegistrationCreated Jul 30, 2026 (85d · New) — Expires Jul 30, 2027
Time to First Unavailability 6 days
What we count Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedSep 4, 2026
Submitted URLhttp://crptmoy.com/
Favicon Hash
Case ID
Observed page title
Crypto.com
Automated brand references
Crypto.com
TLS Certificate
Issued by Google Trust Services · stored validity ends in 53 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
188.114.96.3
Network ASN
AS13335
Organization
CloudFlare, Inc.
Observed location
Toronto, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • pat.ns.cloudflare.com
  • piers.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services
Valid from
2026-07-30 15:42:28
Valid until
2026-10-28 16:40:04
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection time
2026-09-04 16:02:10 UTC
Collection source
PhishDestroy collector
Certificate fingerprint584f5616124b634a12e4860db2503a588c8cecf6a1ff5a1302e6ab70cbbf0300
Certificate names · 2 SANs
  • crptmoy.com
  • *.crptmoy.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-22 20:55:15 UTC

Primary outcome DNS inactive reason: DNS NXDOMAIN 80% confidence
Attribution source: Dns Cache
Evidence layers Availability: DNS inactive Content: Unreachable DNS: NXDOMAIN Registration: Unknown
Latest HTTP observation Unknown Probe Inconclusive 20% 2026-10-23 01:23:18 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-09-07 22:14:20 UTC current episode first observed: 2026-09-30 16:14:55 UTC observed RIP window: 2026-09-07 22:14:20 UTC → 2026-09-30 16:14:55 UTC · 546.01h midpoint estimate ≈ 2026-09-19 07:14:37 UTC · precision 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.
Technologies · 4 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

8 / 90 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 8 detections
alphaMountain.ai
Forcepoint ThreatSeeker
Fortinet
Google Safe Browsing
Gridinsoft
LevelBlue
Lionic
SOCRadar
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of crptmoy.com · checked Sep 4, 2026

60
Needs Work
Performance
FCP
3.87s
First Contentful Paint
LCP
7.32s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
124ms
Total Blocking Time
SI
7.79s
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
546.01
Estimate basis
Bounded by observations
Estimate precision
Low

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

Stored observation history14

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

    Unknown→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

Earlier observations 9
  1. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  6. Availability monitor · Recorded state

    dns_inactive

    dns_nxdomain

  7. Availability monitor · Recorded state

    Reachable→Unavailable

  8. Google Safe Browsing · Threat flag

    No flag recorded→Flag recorded

  9. Availability monitor · First collection record

    Reachable

Recorded activity

6 entries
  1. Google Safe Browsing

    Threat flag recorded

    View source
  2. AlienVault OTX

    6 community references

    View source
  3. VirusTotal

    8/90 engine detections

    View source
  4. Abuse report sent

    PD-20260904-72E79F

    rtr-security-threats@realtimeregister.com
  5. Added to PhishDestroy

    crptmoy.com

    View source
  6. URLScan

    Page captured

    View source

Check for cloaking

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

crptmoy.com

Evidence & External Reports

Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20260904-72E79F Recipient: rtr-security-threats@realtimeregister.com
Page title stored with report: Crypto.com
PDF notice generated
Deep Analysis
Help & reporting

Were You Affected by This Site?

6 evidence signal groups linked 1 stored notification records Content unavailable
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

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 →

Report to Your Local Authorities

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

97-country directory

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

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

Live Threat Feed Appeal This Listing
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/crptmoy.com"
  title="PhishDestroy threat report for crptmoy.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>