Skip to security report
Analytics Dashboard
Domain security and threat intelligence
crypto-connect.net favicon

crypto-connect.net

In short

crypto-connect.net is a phishing page detected by PhishDestroy on 2026-10-22. Risk: critical (100/100). Registrar: Dynadot. Status: Last known active. Hosting: Omegatech LTD. PhishDestroy sent 1 abuse report. VirusTotal: 17/92 engines flag it. Listed on Spamhaus DBL. Do not enter credentials or connect a wallet.

“Crypto Connect — AI Platform for Zero-Fee Financial Analysis”

Registrar
Dynadot
Resolved IP
158.94.210.119
Registered
Sep 10, 2026
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed · HTTP probe
Risk signals
VirusTotal detections: 17/92 Spamhaus DBL: DBL_PHISH
OTX: 4 refs Oct 22, 2026 1 Report Sent
API
This domain has been flagged as malicious
Security engines reporting a detection: 17. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
17 / 92
engine detections
Google Safe Browsing
No threat flag
OTX
4
community references
Page captures
8
open gallery
Domain age
42 days
Reports sent
1
view timeline
Source evidenceVirusTotal 17 / 92 · OTX 4 references 7 sources

VirusTotal

17 / 92 engine detections

Open report

Spamhaus DBL

DBL_PHISH

OTX

4 community references

Open report

Google Safe Browsing

No threat flag

Open report

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

Analysis

Critical
VirusTotal
17 / 92
OTX
4 community refs
Page captures
8
Page captures Source results Registration record

PhishDestroy threat report

Overview

PhishDestroy added crypto-connect.net to its internal blocklist on 2026-10-22 after VirusTotal reported 15 malicious detections. The recorded page title advertises an "AI Platform for Zero-Fee Financial Analysis" and the site returned HTTP 200 on the same date. The assessment is based on the observed detections and not on any confirmed theft or credential capture.

How the scam works

The listing does not confirm a specific attack vector; however, domains that promote financial analysis services are often used in phishing or fraud campaigns that attempt to harvest login credentials or convince users to transfer funds. Without concrete evidence of a particular mechanism, the risk remains that the site could be leveraged for credential harvesting, deceptive offers, or other financial fraud.

Evidence

VirusTotal scanned the domain on 2026-10-18 and marked it malicious by 15 vendors and suspicious by 2, with 17 detections out of 92 engines. Google Safe Browsing checked the domain on 2026-10-22 and did not flag it. URLScan captured the site twice: a 2026-10-13 scan returned a clean verdict, while a 2026-10-22 scan showed a high malicious score (95) from its engine model but an overall non‑malicious verdict. OTX listed the domain in four pulses as of 2026-10-22. PhishDestroy’s internal blocklist marks the domain as blocked, while external blocklists reported zero hits on the same day.

Infrastructure

The domain was registered with Dynadot Inc on 2026-09-10 and is hosted at IP 158.94.210.119, belonging to Omegatech LTD in the Netherlands. TLS is provided by a Let's Encrypt certificate valid from 2026-10-12 to 2027-01-10 for *.crypto-connect.net. Nameservers are ns1.dyna-ns.net and ns2.dyna-ns.net, and ports 22, 80, and 443 were observed open.

What to do

Do not enter any credentials or financial information on the site; if you have already done so, change passwords and monitor accounts for unauthorized activity. Network defenders should add crypto-connect.net to domain blocklists and continue monitoring security feeds for new indicators.

Useful links

urlscan.io scan and screenshotCloudflare Radar reportURLQuery reportStored capture screenshotCloudflare Radar screenshot (2026-10-22T17:42:35Z)URLQuery screenshotURLScan screenshot (2026-09-11T08:10:10Z)URLScan capture reportURLScan screenshot (2026-10-13T15:30:29Z)URLScan capture reportURLScan screenshot (2026-10-14T10:21:11Z)URLScan capture reportURLScan screenshot (2026-10-22T17:12:39Z)URLScan capture reportVirusTotal reportGoogle Safe Browsing statusReport phishing to GoogleSite owner? Request a review

Collected source details

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

URLScan · 2026-10-22T17:07:14Z

Observed: · Retrieved:

Uuid
01a16494-a9e1-70a9-97f5-3e843f025372
Final url
https://crypto-connect.net/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://crypto-connect.net/",
        "from": "http://crypto-connect.net/",
        "status": 307
    }
]
Ip
158.94.210.119
Contacted IP addresses
[
    "158.94.210.119"
]
Asns
[
    "202412"
]
Countries
[
    "NL"
]
Document hash
6d343e6f535aeded40971ca15d09d0bf4ac38f36ebe4e066f15874cbba81c318
Script hashes
[
    "8aa5f8f647356dcd4fc5dbbe0efd5bc0e8da74026bc61e24636e2e1f5749b0ce"
]
Globals
[
    "__dclq",
    "__dclOrig",
    "__dclFlush",
    "__smsCheckBeforeSubmit",
    "__isSmsEnabled",
    "__isSmsVerified",
    "intlTelInput"
]
Cookies
[
    "connect.sid"
]
Tls
{
    "san": [
        "*.crypto-connect.net",
        "crypto-connect.net"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE1",
    "subject": "crypto-connect.net",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-10T20:26:52Z",
    "valid_from": "2026-10-12T20:26:53Z"
}
Domain age days
2518
Apex age days
2518
Tls age days
9
Tls valid days
89
Requests
7
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 95,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "content-type": "text/html; charset=utf-8",
    "x-content-type-options": "nosniff",
    "referrer-policy": "same-origin"
}
Cloudflare Radar · 2026-10-22T17:42:35Z

Observed: · Retrieved:

Uuid
f62d7113-d189-4920-a086-5acc04300990
Final url
https://finsy9-praesentium22.cyou/
Status
200
History
[
    {
        "url": "https://crypto-connect.net/",
        "status": 200
    },
    {
        "url": "https://finsy9-praesentium22.cyou/",
        "status": 200
    }
]
DOM structure hash
5218f76926bdd93ab3478499a2ba4f040a6ac8941b4ef8e11c6c37074a0381a1
Document hash
1dd86b2d5ac7a2d33ddbbe163225d33f0bc6a83fbf60016e33b5a52e9c6d4c41
Phishing v2
[
    "phishing"
]
Domain risks
[
    "Newly Seen Domains",
    "Security Risks"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "finsy9-praesentium22.cyou",
        "type": "A",
        "value": "172.67.133.6"
    },
    {
        "name": "finsy9-praesentium22.cyou",
        "type": "A",
        "value": "104.21.5.59"
    },
    {
        "name": "finsy9-praesentium22.cyou",
        "type": "AAAA",
        "value": "2606:4700:3036::6815:53b"
    },
    {
        "name": "finsy9-praesentium22.cyou",
        "type": "AAAA",
        "value": "2606:4700:3037::ac43:8506"
    }
]
Dnssec valid
false
Ip
172.67.133.6
Registration record
{
    "registrar": "NameCheap, Inc.",
    "created": "2026-10-22T15:01:33Z",
    "updated": "2026-10-22T15:01:40Z",
    "expires": "2027-10-22T23:59:59Z",
    "nameservers": [
        "lilyana.ns.cloudflare.com",
        "rocky.ns.cloudflare.com"
    ]
}
VirusTotal · 2026-10-18T16:40:20Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 44,
    "malicious": 15,
    "suspicious": 2,
    "undetected": 31
}
Vendor labels
{
    "DNS8": "suspicious",
    "ESET": "phishing",
    "VIPRE": "malware",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Webroot": "malicious",
    "Fortinet": "phishing",
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "Seclookup": "malicious",
    "Gridinsoft": "suspicious",
    "BitDefender": "phishing",
    "Chong Lua Dao": "malicious",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Categories
{
    "Dr.Web": "not recommended site",
    "Sophos": "phishing and fraud",
    "Webroot": "Phishing and Other Frauds",
    "BitDefender": "financial",
    "Forcepoint ThreatSeeker": "phishing and other frauds"
}
Registrar
Dynadot Inc
Created
2026-09-10T10:19:51Z
Expires
2027-09-10T10:19:51Z
Updated
2026-09-14T05:25:06Z
First seen
2025-06-15T16:04:32Z
DNS records
[
    {
        "ttl": 300,
        "type": "SOA",
        "rname": "hostmaster.crypto-connect.net",
        "value": "ns1.dyna-ns.net"
    },
    {
        "ttl": 300,
        "type": "NS",
        "value": "ns2.dyna-ns.net"
    },
    {
        "ttl": 300,
        "type": "NS",
        "value": "ns1.dyna-ns.net"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "158.94.210.119"
    }
]
Dns at
2026-10-18T16:45:38Z
Jarm
40d40d40d00000000043d43d00043d6aff5ab0f4fc31897186312c9e639319
Certificate
{
    "san": [
        "*.crypto-connect.net",
        "crypto-connect.net"
    ],
    "issuer": "Let's Encrypt / YE1",
    "serial": "6917d28807d7529dd351d35ab20959992c8",
    "sha256": "469dc88d16b63eb448f408d01c019015fbdde9f83ede91023dac83d1786e8c00",
    "subject": "crypto-connect.net",
    "valid_to": "2027-01-10T20:26:52Z",
    "valid_from": "2026-10-12T20:26:53Z"
}
Registration record
{
    "registrar": "Dynadot Inc",
    "registrar_iana_id": "472",
    "registrar_url": "http://www.dynadot.com",
    "created": "2026-09-10T10:19:51Z",
    "updated": "2026-09-14T05:25:06Z",
    "expires": "2027-09-10T10:19:51Z",
    "status": [
        "clientTransferProhibited"
    ],
    "nameservers": [
        "bethany.ns.cloudflare.com",
        "norm.ns.cloudflare.com"
    ],
    "dnssec": "unsigned"
}
Registry data
{
    "status": [
        "transfer prohibited"
    ],
    "events": {
        "expiration": "2027-09-10T10:19:51Z",
        "last changed": "2026-10-12T21:25:32Z",
        "registration": "2026-09-10T10:19:51Z",
        "registrar expiration": "2027-09-10T10:19:51Z",
        "last update of RDAP database": "2026-10-12T21:33:53Z"
    }
}
Website checks · 2026-10-22T17:44:06Z
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "crypto-connect.net"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2026-10-22T17:09:14Z",
    "first": "2026-10-22T17:09:14Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 19784
}
Crawler rules
{
    "agents": [
        "*"
    ],
    "present": true,
    "sitemaps": [
        "https://crypto-connect.net/sitemap.xml"
    ]
}
Sitemap
{
    "present": true,
    "url_count": 5
}
Page title and metadata
{
    "title": "Crypto Connect — AI Platform for Zero-Fee Financial Analysis",
    "robots": "index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1",
    "description": "Crypto Connect offers predictive AI analysis of global market data, so you keep every gain with no commissions or hidden fees. Start your free analysis today.",
    "canonicalUrl": "https://crypto-connect.net/"
}
Trackers
{
    "requests": 55,
    "trackers": [
        {
            "name": "Cloudflare",
            "company": "Cloudflare",
            "country": "US",
            "category": "Hosting",
            "requests": 1
        },
        {
            "name": "jsDelivr",
            "company": "jsDelivr",
            "category": "Hosting",
            "requests": 4
        }
    ]
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 148,
        "tls": 75,
        "wait": 75,
        "connect": 70,
        "download": 131
    },
    "response_ms": 499
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_128_GCM_SHA256",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        22,
        80,
        443
    ]
}
Carbon
{
    "bytes": 67976,
    "co2_grams": 0.0025,
    "cleaner_than": 30
}
Dns server
{
    "ns": [
        {
            "ip": "162.159.27.158",
            "host": "ns1.dyna-ns.net"
        },
        {
            "ip": "162.159.24.5",
            "host": "ns2.dyna-ns.net"
        }
    ],
    "zone": "crypto-connect.net"
}
Location
{
    "ip": "158.94.210.119",
    "asn": "202412",
    "org": "Omegatech LTD",
    "city": "Amsterdam",
    "country": "NL"
}
Ssl
{
    "issuer": "Let's Encrypt / YE1",
    "subject": "crypto-connect.net"
}
DNS records
{
    "A": [
        "158.94.210.119"
    ],
    "NS": [
        "ns1.dyna-ns.net",
        "ns2.dyna-ns.net"
    ],
    "SOA": "{\"nsname\": \"ns1.dyna-ns.net\", \"hostmaster\": \"hostmaster.crypto-connect.net\", \"serial\": 2026101203, \"refresh\": 16384, \"retry\": 2048, \"expire\": 1209600, \"minttl\": 300}"
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": "same-origin",
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": "nosniff",
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "158.94.210.119",
    "family": 4
}
Redirects
{
    "chain": [
        "https://crypto-connect.net"
    ]
}
Tech stack
{
    "technologies": [
        "Node.js",
        "Express",
        "HTTP/3"
    ]
}
Page links
{
    "internal_count": 10
}
Registration record
{
    "registrar": "Dynadot Inc",
    "created": "2026-09-10T10:19:51Z",
    "updated": "2026-10-12T12:58:07Z",
    "expires": "2027-09-10T10:19:51Z",
    "status": [
        "clientTransferProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "ns1.dyna-ns.net",
        "ns2.dyna-ns.net"
    ]
}
HTTP headers
{
    "headers": {
        "content-type": "text/html; charset=utf-8",
        "x-content-type-options": "nosniff",
        "referrer-policy": "same-origin"
    }
}

Questions about crypto-connect.net

Is crypto-connect.net legit?

No. PhishDestroy classifies crypto-connect.net as a phishing page (risk: critical, 100/100); it was first detected on 2026-10-22. VirusTotal: 17/92 engines flag it. Listed on Spamhaus DBL. Treat the site as unsafe.

Is crypto-connect.net safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on crypto-connect.net. 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 crypto-connect.net?

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 1
PhishDestroy PhishDestroy list View source

Stored Capture · 8 captures

Primary capture 1 / 8
SourcePrimary capture
Recorded2026-10-22 17:09 UTC
StateStored capture
HTTP status at archiveHTTP 200
Final URLhttps://crypto-connect.net/
Position1 / 8
Open capture Wayback Download

Domain details

Domain
IP Reputation abuse score 10/100 10 reports PhishingOpen ProxyBad Web Bot checked Oct 22, 2026
OTX tags 2026-10activeall-domainsblocklistcontentcryptodomainsdrainerfraudmonthlyphishdestroyphishingscam
Registrar Dynadot US(US)
Abuse contactabuse@omegatech.sc, abuse@dynadot.com
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for crypto-connect.net →
RegistrationCreated Sep 10, 2026 (42d · New) — Expires Sep 10, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 22, 2026
DOM Analysisanalyzed Oct 22, 2026score 0/100
Submitted URLhttp://crypto-connect.net/
Favicon Hash
Case ID
Observed page title
Crypto Connect — AI Platform for Zero-Fee Financial Analysis
TLS Certificate
Issued by YE1 · stored validity ends in 80 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
158.94.210.119
Network ASN
AS202412
Organization
Omegatech LTD
Observed location
Amsterdam, NL

Nameservers 2

  • ns1.dyna-ns.net
  • ns2.dyna-ns.net

Location describes the IP network.

TLS certificate

Issuer
YE1
Valid from
2026-10-12 20:26:53
Valid until
2027-01-10 20:26:52
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint469dc88d16b63eb448f408d01c019015fbdde9f83ede91023dac83d1786e8c00
Certificate names · 2 SANs
  • *.crypto-connect.net
  • crypto-connect.net

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

viewdns.info · 158.94.210.119rapiddns.io
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

17 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection
alphaMountain.ai
BitDefender
Chong Lua Dao
CyRadar
DNS8
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
Lionic
Seclookup
SOCRadar
Sophos
VIPRE
Webroot
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of crypto-connect.net · checked Oct 22, 2026

100
Good
Performance
FCP
1s
First Contentful Paint
LCP
1.57s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
1.76s
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://crypto-connect.net/
Final URL: https://crypto-connect.net/
Response
HTTP 200
HTML body
781 B
Compressed
411 B
Links
0 internal · 0 external
Selected response headers
Cache-Control: no-cache, no-store, must-revalidate
Content-Encoding: gzip
Content-Type: text/html; charset=utf-8
X-Powered-By: Express
Security headers present
X-Content-Type-OptionsReferrer-Policy
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 11
Alt-Svc
h3=":443"; ma=2592000
Cache-Control
no-cache, no-store, must-revalidate
Content-Encoding
gzip
Content-Length
419
Content-Type
text/html; charset=utf-8
Date
Thu, 22 Oct 2026 17:06:48 GMT
Referrer-Policy
same-origin
Vary
Accept-Encoding
Via
1.1 Caddy
X-Content-Type-Options
nosniff
X-Powered-By
Express

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

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

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 · First collection record

    Reachable

Recorded activity

6 entries
  1. AlienVault OTX

    4 community references

    View source
  2. Google Safe Browsing

    No threat flag

    View source
  3. VirusTotal

    17/92 engine detections

    View source
  4. Abuse report sent

    PD-20261022-E9C6C3

    abuse@omegatech.sc
  5. Added to PhishDestroy

    crypto-connect.net

    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.

crypto-connect.net

Evidence & External Reports

Security Analysis
URLScan Stored capture VirusTotal 17 det. ChainPatrol URLQuery Report stored SSL Labs Stored certificate dates valid CF Radar Open report OTX 4 refs WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20261022-E9C6C3 Recipient: abuse@omegatech.sc
PDF notice generated Notice text archived (291 chars)
Abuse notice text as sent to the provider 
Registrar: Dynadot LLC / Dynadot Inc (United States)
Policy Violations: Acceptable Use forbids illegal content; Spam & Abuse Policy prohibits phishing, fraud, malware; Dynadot may disable DNS and suspend domains
Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis
Help & reporting

Were You Affected by This Site?

6 evidence signal groups linked 1 stored notification records Last known active
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.

Immediate steps Find reporting contacts

Official reporting routes

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect
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 crypto-connect.net)
  • 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

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

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.

Request a correction or appeal How PhishDestroy works
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/crypto-connect.net"
  title="PhishDestroy threat report for crypto-connect.net"
  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>