Skip to security report
Analytics Dashboard
This domain has been flagged as malicious
Security engines reporting a detection: 16. Exercise extreme caution — do not enter credentials or personal information.
Domain security and threat intelligence
crypto-legacy.org favicon

crypto-legacy.org

In short

crypto-legacy.org is a PayPal impersonation page detected by PhishDestroy on 2026-10-25.

“Crypto Legacy™ | The Official & Updated Website 2025 🥇”

Review the evidence
Registrar
Internet Domain Servic…
Resolved IP
185.98.60.138
Registered
Apr 18, 2023
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 16/92 Automated brand label: PayPal Scam type: Impersonation
VirusTotal
16 / 92
engine detections ·
OTX
1
community references
Cloudflare Radar
Phishing
Page captures
7
open gallery
Domain age
1286 days
Reports sent
1
view timeline
OTX: 1 ref Oct 25, 2026 1 Report Sent
X Telegram API
ABUSE NOTICE · 24H+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence

The sent-report ledger records the first outgoing report at . The recorded recipient is abuse@idealhosting.net.tr. The latest stored availability evidence still shows the domain reachable; 27 hours has elapsed since the first outgoing report.

ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.

Elapsed since first report
27 hours
Reports sent
1
Latest case ID
PD-20261025-5525DA
Current status
HTTP 200 at latest stored check

Analysis

Domain summary

crypto-legacy.org is a PayPal impersonation page detected by PhishDestroy on 2026-10-25. Risk: critical (100/100). Registrar: Internet Domain Servic…. Status: Last known active. Hosting: Ideal Hosting Teknoloji A.S. PhishDestroy sent 1 abuse report. VirusTotal: 16/92 engines flag it. Do not enter credentials or connect a wallet.

Critical
VirusTotal
16 / 92
OTX
1 community ref
Page captures
7
Page captures Source results Registration record

PhishDestroy threat report

Overview

PhishDestroy added crypto-legacy.org to its internal blocklist on 2026-10-25 after an intake review highlighted VirusTotal detections from 13 malicious vendors. The recorded page title claims "Crypto Legacy™ | The Official & Updated Website 2025" and the domain returned an HTTP 200 response when first observed on 2026-10-25.

How the scam works

The domain is flagged by multiple security engines for phishing or malware, a common indicator of fake‑exchange or credential‑harvesting sites, but no specific malicious payload was observed on the captured page.

Evidence

VirusTotal (analysis 2026-10-19, retrieved 2026-10-25) reported 13 malicious and 3 suspicious detections from 92 engines, including BitDefender, Fortinet and Kaspersky marking it as phishing. URLScan captured on 2026-07-31 gave an overall clean verdict yet its engine score was 93 with a malicious tag. Cloudflare Radar (2026-10-25) classified the domain as malicious under malware and phishing, while Google Safe Browsing (2026-10-25) reported no flag and external blocklists showed zero hits.

Infrastructure

The domain was registered on 2023-04-18 through Internet Domain Service BS Corp with nameservers ns1.cryptodns.co and ns2.cryptodns.co. The recorded hosting resolved to IP 185.98.60.138, which was identified as belonging to Ideal Hosting Teknoloji A.S. in Turkey, and a Let's Encrypt TLS certificate (valid 2026-09-18 to 2026-12-17) was observed.

What to do

Visitors should not submit credentials, personal data or cryptocurrency information on this site; if they have, they should change related passwords and monitor accounts. Defenders can block crypto-legacy.org at network perimeters, log DNS queries to 185.98.60.138, and add the domain to internal blocklists.

Useful links

urlscan.io scan and screenshotCloudflare Radar reportStored capture screenshotCloudflare Radar screenshot (2026-10-25T00:51:42Z)URLScan screenshot (2026-07-30T07:16:02Z)URLScan capture reportURLScan screenshot (2026-07-30T07:48:36Z)URLScan capture reportVirusTotal reportGoogle Safe Browsing statusReport phishing to GoogleSite owner? Request a review
Source evidenceVirusTotal 16 / 92 · OTX 1 references 9 sources

VirusTotal

16 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
44
Malicious
13
Suspicious
3
Undetected
32

Vendor labels

CRDF
malicious
DNS8
suspicious
ESET
suspicious
VIPRE
malware
G-Data
phishing
Lionic
phishing
Sophos
phishing
Emsisoft
malware
Fortinet
phishing
SOCRadar
phishing
Kaspersky
phishing
Seclookup
malicious
Gridinsoft
suspicious
BitDefender
phishing
alphaMountain.ai
phishing
Forcepoint ThreatSeeker
phishing

Reputation score

0

Registrar

Internet Domain Service BS Corp

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    300
    Type
    NS
    Value
    ns2.cryptodns.co
  • TTL, seconds
    300
    Type
    NS
    Value
    ns1.cryptodns.co
  • TTL, seconds
    300
    Type
    A
    Value
    185.98.60.138

DNS records observed

JARM fingerprint

1dd40d40d00040d00042d43d000000831b6af40378e2dd35eeac4e9311926e

Certificate

Subject alternative names
  • *.crypto-legacy.org
  • crypto-legacy.org
Issuer
Let's Encrypt / YE2
Serial
629090cf03fcf8ba3ae6b8da2f842af694c
SHA-256
991f52beeff3ac72b93ffa9768d81cb4f2ec73fe70c79718999bd5fb1e281637
Subject
crypto-legacy.org
Valid until
Valid from

Registration record

Registrar
Internet Domain Service BS Corp
Registrar IANA ID
2487
Registrar URL
http://www.internet.bs
Registered
Updated
Expires
Status
  • clientTransferProhibited
Nameservers
  • ns1.cryptodns.co
  • ns2.cryptodns.co
DNSSEC
unsigned

Registry data (RDAP)

Status
  • client transfer prohibited
Registry events
Expiration
Last changed
Registration
Registrar expiration
Last RDAP database update
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 44,
    "malicious": 13,
    "suspicious": 3,
    "undetected": 32
}
Vendor labels
{
    "CRDF": "malicious",
    "DNS8": "suspicious",
    "ESET": "suspicious",
    "VIPRE": "malware",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "Emsisoft": "malware",
    "Fortinet": "phishing",
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "Seclookup": "malicious",
    "Gridinsoft": "suspicious",
    "BitDefender": "phishing",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Registrar
Internet Domain Service BS Corp
Created
2023-04-18T14:12:40Z
Expires
2027-04-18T14:12:40Z
Updated
2026-08-12T00:14:21Z
First seen
2024-03-05T05:19:39Z
DNS records
[
    {
        "ttl": 300,
        "type": "NS",
        "value": "ns2.cryptodns.co"
    },
    {
        "ttl": 300,
        "type": "NS",
        "value": "ns1.cryptodns.co"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "185.98.60.138"
    }
]
Dns at
2026-10-19T08:49:11Z
Jarm
1dd40d40d00040d00042d43d000000831b6af40378e2dd35eeac4e9311926e
Certificate
{
    "san": [
        "*.crypto-legacy.org",
        "crypto-legacy.org"
    ],
    "issuer": "Let's Encrypt / YE2",
    "serial": "629090cf03fcf8ba3ae6b8da2f842af694c",
    "sha256": "991f52beeff3ac72b93ffa9768d81cb4f2ec73fe70c79718999bd5fb1e281637",
    "subject": "crypto-legacy.org",
    "valid_to": "2026-12-17T16:46:15Z",
    "valid_from": "2026-09-18T16:46:16Z"
}
Registration record
{
    "registrar": "Internet Domain Service BS Corp",
    "registrar_iana_id": "2487",
    "registrar_url": "http://www.internet.bs",
    "created": "2023-04-18T14:12:40Z",
    "updated": "2026-08-12T00:14:21Z",
    "expires": "2027-04-18T14:12:40Z",
    "status": [
        "clientTransferProhibited"
    ],
    "nameservers": [
        "ns1.cryptodns.co",
        "ns2.cryptodns.co"
    ],
    "dnssec": "unsigned"
}
Registry data
{
    "status": [
        "client transfer prohibited"
    ],
    "events": {
        "expiration": "2027-04-18T14:12:40Z",
        "last changed": "2026-05-20T13:56:26Z",
        "registration": "2023-04-18T14:12:40Z",
        "registrar expiration": "2027-04-18T14:12:40Z",
        "last update of RDAP database": "2026-10-19T08:49:11Z"
    }
}
Separate source record · 13 malicious + 3 suspicious / 92 · 2026-10-19 08:43:50 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-19T08:43:50Z
fetched_at
2026-10-25T00:49:43Z
stats
{"timeout":0,"harmless":44,"malicious":13,"suspicious":3,"undetected":32}

Cloudflare Radar

Phishing

Open report
Cloudflare RadarOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Report ID

f3321100-4a65-4f86-a003-9afc27ca882a

Final URL

https://crypto-legacy.org/

HTTP response

200

Navigation history

  • URL
    https://crypto-legacy.org/
    Status
    200

DOM structure hash

fb2d57fbc57401b2648794c29da1bfd1fa8f4355474c15dd7d871b2f4283cd1e

Document hash

9570c8332bd1b35a64e2bd81451050679c90ad343efbf4ae853c3ddf8f837b2d

Phishing classifier result

  • phishing

Domain risk categories

  • Malware
  • Security threats
  • CIPA Filter
  • CIPA

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    crypto-legacy.org
    Type
    A
    Value
    185.98.60.138

DNSSEC valid

No

IP address

185.98.60.138

Verdict

Tags
  • malware
Malicious
Yes
Categories
  • malware

Registration record

Registrar
Internet Domain Service BS Corp
Registered
Updated
Expires
Nameservers
  • ns1.cryptodns.co
  • ns2.cryptodns.co
Original source fields · JSON
Uuid
f3321100-4a65-4f86-a003-9afc27ca882a
Final url
https://crypto-legacy.org/
Status
200
History
[
    {
        "url": "https://crypto-legacy.org/",
        "status": 200
    }
]
DOM structure hash
fb2d57fbc57401b2648794c29da1bfd1fa8f4355474c15dd7d871b2f4283cd1e
Document hash
9570c8332bd1b35a64e2bd81451050679c90ad343efbf4ae853c3ddf8f837b2d
Phishing v2
[
    "phishing"
]
Domain risks
[
    "Malware",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "crypto-legacy.org",
        "type": "A",
        "value": "185.98.60.138"
    }
]
Dnssec valid
false
Ip
185.98.60.138
Verdict
{
    "tags": [
        "malware"
    ],
    "malicious": true,
    "categories": [
        "malware"
    ]
}
Registration record
{
    "registrar": "Internet Domain Service BS Corp",
    "created": "2023-04-18T14:12:40Z",
    "updated": "2026-08-12T00:14:21Z",
    "expires": "2027-04-18T14:12:40Z",
    "nameservers": [
        "ns1.cryptodns.co",
        "ns2.cryptodns.co"
    ]
}

URLScan

Malicious · engine verdict · score 97

Open report
URLScanOriginal source recordObserved: 22 fields

Observed: · Retrieved:

Report ID

01a17098-b202-753c-9e42-1d56e860cb6d

Final URL

https://crypto-legacy.org/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://crypto-legacy.org/
    From
    http://crypto-legacy.org/
    Status
    307

IP address

185.98.60.138

Contacted domains

  • fonts.gstatic.com
  • fonts.googleapis.com

Contacted IP addresses

  • 142.251.20.94
  • 142.251.13.95
  • 185.98.60.138

Autonomous systems (ASN)

  • 15169
  • 201064

Server countries

  • US
  • TR

Document hash

9570c8332bd1b35a64e2bd81451050679c90ad343efbf4ae853c3ddf8f837b2d

Script hashes

  • b1dc3a468eb8949e17762628c68205ee4ffad52ec1cdbe48e3456bf96c1c9603
  • 81a17cfaf5731292df919a903727b86550d2a57e1ad29893dc693ef9c2013113

JavaScript globals

  • __VUE__
  • switcher
  • switcherButton
  • modal
  • btn

Cookies

  • lang_fx

TLS session and certificate

Subject alternative names
  • *.crypto-legacy.org
  • crypto-legacy.org
Cipher
AES_128_GCM
Issuer
YE2
Subject
crypto-legacy.org
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

1284

Registered domain age, days

1284

Certificate age, days

36

Certificate validity, days

89

Page requests

53

Provider verdicts

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

HTTP headers

Server
nginx/1.30.1
Content-type
text/html
Original source fields · JSON
Uuid
01a17098-b202-753c-9e42-1d56e860cb6d
Final url
https://crypto-legacy.org/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://crypto-legacy.org/",
        "from": "http://crypto-legacy.org/",
        "status": 307
    }
]
Ip
185.98.60.138
Contacted domains
[
    "fonts.gstatic.com",
    "fonts.googleapis.com"
]
Contacted IP addresses
[
    "142.251.20.94",
    "142.251.13.95",
    "185.98.60.138"
]
Asns
[
    "15169",
    "201064"
]
Countries
[
    "US",
    "TR"
]
Document hash
9570c8332bd1b35a64e2bd81451050679c90ad343efbf4ae853c3ddf8f837b2d
Script hashes
[
    "b1dc3a468eb8949e17762628c68205ee4ffad52ec1cdbe48e3456bf96c1c9603",
    "81a17cfaf5731292df919a903727b86550d2a57e1ad29893dc693ef9c2013113"
]
Globals
[
    "__VUE__",
    "switcher",
    "switcherButton",
    "modal",
    "btn"
]
Cookies
[
    "lang_fx"
]
Tls
{
    "san": [
        "*.crypto-legacy.org",
        "crypto-legacy.org"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE2",
    "subject": "crypto-legacy.org",
    "protocol": "TLS 1.3",
    "valid_to": "2026-12-17T16:46:15Z",
    "valid_from": "2026-09-18T16:46:16Z"
}
Domain age days
1284
Apex age days
1284
Tls age days
36
Tls valid days
89
Requests
53
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 97,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "nginx/1.30.1",
    "content-type": "text/html"
}
Separate monitor record · date not recorded

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

record_source
domain_monitor.urlscan
uuid
019fb73c-16a8-73df-bd7b-8e0b09d60ce8
score
null
malicious
null
result_at
null
enriched_at
2026-10-25T09:13:04Z
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":"2026-10-25 10:13:04"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

1 community reference

Open report

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

93 / 100 · heuristic score · 4 brand references · 1 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
crypto-legacy.org — Suspicious Domain
ai_description
PhishDestroy flags crypto-legacy.org as a suspicious domain after multiple security vendors label it malicious, despite a clean URLScan verdict.
ai_generated_at
2026-10-25T01:56:53Z
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: 26 fields

Mail configuration

SPF lookups
0

CAA records

Domain
crypto-legacy.org

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Web archive observations

Last observation
First observation
Recorded changes
26
Archived days
29
Snapshots per day
0.02
Average page size, bytes
10679

Crawler rules

User agents
  • *
Present
Yes
Sitemap URLs
  • https://crypto-legacy.org/sitemap.xml

Sitemap

Present
Yes
URL count
128

Page title and metadata

Page title
Crypto Legacy™ | The Official & Updated Website 2025 🥇
Indexing directives
index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1
Description
Explore Crypto Legacy, your trusted trading platform for secure and reliable cryptocurrency transactions. Join a community built on trust and innovation.
Twitter card
summary
Canonical URL
https://crypto-legacy.org/

Trackers

Requests
48
Observed services
  • Name
    Google Fonts
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    1
  • Name
    Google Static
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    2

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
16
TLS
156
Waiting
29
Connection
15
Download
15
Response time, ms
231

TLS connection

ALPN
http/1.1
Cipher
TLS_AES_256_GCM_SHA384
Protocol
TLSv1.3
Supported versions
  • TLSv1.2
  • TLSv1.3
Certificate authorized
Yes
Forward secrecy
Yes

Ports

Open ports
  • 22
  • 53
  • 80
  • 443

Carbon estimate

Bytes
69312
CO₂, grams
0.0025
Cleaner than, %
30

DNS servers

Nameservers
  • IP address
    185.98.60.138
    Host
    ns2.cryptodns.co
  • IP address
    185.98.60.138
    Host
    ns1.cryptodns.co
DNS zone
crypto-legacy.org

Cookies

Cookies
  • Name
    lang_fx

Location

IP address
185.98.60.138
ASN
201064
Organization
Ideal Hosting Teknoloji A.S.
City
Mahmutbey
Country
TR

TLS certificate

Issuer
Let's Encrypt / YE2
Subject
crypto-legacy.org

DNS records

A
  • 185.98.60.138
NS
  • ns2.cryptodns.co
  • ns1.cryptodns.co
SOA
Primary nameserver
ns1.cryptodns.co
Hostmaster
admin.cryptodns.co
Serial
2026052113
Refresh, seconds
3600
Retry, seconds
1800
Expiry, seconds
604800
Minimum TTL, seconds
300

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

IP lookup

IP address
185.98.60.138
IP version
4

Redirects

Redirect chain
  • https://crypto-legacy.org

Page links

Internal links
37

Registration record

Registrar
Internet Domain Service BS Corp
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
Nameservers
  • ns1.cryptodns.co
  • ns2.cryptodns.co

HTTP headers

Response headers
Server
nginx/1.30.1
Content-type
text/html
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "crypto-legacy.org"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2026-10-25T00:48:15Z",
    "first": "2021-11-30T11:10:04Z",
    "changes": 26,
    "days_archived": 29,
    "scans_per_day": 0.02,
    "avg_page_bytes": 10679
}
Crawler rules
{
    "agents": [
        "*"
    ],
    "present": true,
    "sitemaps": [
        "https://crypto-legacy.org/sitemap.xml"
    ]
}
Sitemap
{
    "present": true,
    "url_count": 128
}
Page title and metadata
{
    "title": "Crypto Legacy™ | The Official & Updated Website 2025 🥇",
    "robots": "index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1",
    "description": "Explore Crypto Legacy, your trusted trading platform for secure and reliable cryptocurrency transactions. Join a community built on trust and innovation.",
    "twitterCard": "summary",
    "canonicalUrl": "https://crypto-legacy.org/"
}
Trackers
{
    "requests": 48,
    "trackers": [
        {
            "name": "Google Fonts",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 1
        },
        {
            "name": "Google Static",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 2
        }
    ]
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 16,
        "tls": 156,
        "wait": 29,
        "connect": 15,
        "download": 15
    },
    "response_ms": 231
}
TLS connection
{
    "alpn": "http/1.1",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        22,
        53,
        80,
        443
    ]
}
Carbon
{
    "bytes": 69312,
    "co2_grams": 0.0025,
    "cleaner_than": 30
}
Dns server
{
    "ns": [
        {
            "ip": "185.98.60.138",
            "host": "ns2.cryptodns.co"
        },
        {
            "ip": "185.98.60.138",
            "host": "ns1.cryptodns.co"
        }
    ],
    "zone": "crypto-legacy.org"
}
Cookies
{
    "cookies": [
        {
            "name": "lang_fx"
        }
    ]
}
Location
{
    "ip": "185.98.60.138",
    "asn": "201064",
    "org": "Ideal Hosting Teknoloji A.S.",
    "city": "Mahmutbey",
    "country": "TR"
}
Ssl
{
    "issuer": "Let's Encrypt / YE2",
    "subject": "crypto-legacy.org"
}
DNS records
{
    "A": [
        "185.98.60.138"
    ],
    "NS": [
        "ns2.cryptodns.co",
        "ns1.cryptodns.co"
    ],
    "SOA": "{\"nsname\": \"ns1.cryptodns.co\", \"hostmaster\": \"admin.cryptodns.co\", \"serial\": 2026052113, \"refresh\": 3600, \"retry\": 1800, \"expire\": 604800, \"minttl\": 300}"
}
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
}
Get ip
{
    "ip": "185.98.60.138",
    "family": 4
}
Redirects
{
    "chain": [
        "https://crypto-legacy.org"
    ]
}
Page links
{
    "internal_count": 37
}
Registration record
{
    "registrar": "Internet Domain Service BS Corp",
    "created": "2023-04-18T14:12:40Z",
    "updated": "2026-08-12T00:14:21Z",
    "expires": "2027-04-18T14:12:40Z",
    "status": [
        "clientTransferProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "ns1.cryptodns.co",
        "ns2.cryptodns.co"
    ]
}
HTTP headers
{
    "headers": {
        "server": "nginx/1.30.1",
        "content-type": "text/html"
    }
}
Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Malware Security threats Malware
View full Cloudflare Radar report

Questions about crypto-legacy.org

Is crypto-legacy.org legit?

No. PhishDestroy classifies crypto-legacy.org as a PayPal impersonation page (risk: critical, 100/100); it was first detected on 2026-10-25. VirusTotal: 16/92 engines flag it. Treat the site as unsafe.

Is crypto-legacy.org safe to connect a wallet?

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

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 · 7 captures

Primary capture 1 / 7
SourcePrimary capture
Recorded
StateStored capture
HTTP status200
Final URLhttps://crypto-legacy.org/
Position1 / 7
Open capture Wayback Download
All capture links and hashes (7)

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Reputation abuse score 0/100 0 reports checked Oct 25, 2026
Registrar Internet Domain Servic…
Abuse contactabuse@idealhosting.net.tr, registry@key-systems.net
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for crypto-legacy.org →
Hosting abuse contact abuse@idealhosting.net.tr Ideal Hosting Teknoloji A.S. · AS201064
RegistrationCreated Apr 18, 2023 — Expires Apr 18, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 25, 2026
DOM Analysisanalyzed Oct 25, 2026score 93/1004 brand signals
Submitted URLhttp://crypto-legacy.org/
Favicon Hash
Case ID
Observed page title
Crypto Legacy™ | The Official & Updated Website 2025 🥇
Automated brand references
Across PayPal Revolut Visa
TLS Certificate
Issued by Let's Encrypt / YE2 · stored validity ends in 52 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
185.98.60.138
Network ASN
AS201064
Organization
Ideal Hosting Teknoloji A.S.
Observed location
Mahmutbey, TR
Server header
nginx/1.30.1

Nameservers 2

  • ns1.cryptodns.co
  • ns2.cryptodns.co

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE2
Valid from
2026-09-18 16:46:16
Valid until
2026-12-17 16:46:15
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint991f52beeff3ac72b93ffa9768d81cb4f2ec73fe70c79718999bd5fb1e281637
Certificate names · 2 SANs
  • *.crypto-legacy.org
  • crypto-legacy.org

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

viewdns.info · 185.98.60.138rapiddns.io

Latest Classified Outcome 2026-10-25 23:00:47 UTC

The site was serving its pages at the latest check.

Technical details
Primary outcome Live content reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Unknown Content: Unknown DNS: Stale Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-10-25 23:00:47 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-25 00:08:59 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.
Recorded subdomains1

Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.

  • www.crypto-legacy.orgDomain record

The original observation time is not recorded for these hostnames.

Technologies · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

16 / 92 security vendors flagged this domain
View on VT
Last analyzed
alphaMountain.ai
BitDefender
CRDF
DNS8
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
Lionic
Seclookup
SOCRadar
Sophos
VIPRE

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of crypto-legacy.org · checked Oct 25, 2026

73
Needs Work
Performance
FCP
3.15 s
First Contentful Paint
LCP
5 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
4.84 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://crypto-legacy.org/
Final URL: https://crypto-legacy.org/
Crypto Legacy™ | The Official & Updated Website 2025 🥇
Explore Crypto Legacy, your trusted trading platform for secure and reliable cryptocurrency transactions. Join a community built on trust and innovation.
Response
HTTP 200
HTML body
67.7 KB
Compressed
14.0 KB
Links
42 internal · 0 external
Detected technologies
nginx
Selected response headers
Server: nginx/1.30.1
Content-Type: text/html
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Twitter card: summary
Saved response-header values · 8
Accept-Ranges
bytes
Connection
keep-alive
Content-Length
69312
Content-Type
text/html
Date
Sun, 25 Oct 2026 00:49:14 GMT
Etag
"678162ba-10ec0"
Last-Modified
Fri, 10 Jan 2025 18:11:06 GMT
Server
nginx/1.30.1

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 · Recorded state

    Unknown→live_content

    content_served

All retained availability observations7

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_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 00:00:47.000000
    Evidence SHA-256
    dd93c3b774f5a9dc98b95109756e28172cdf32ebc0d7fc8757c0418b3ee68ca7
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 00:00:47
    Evidence reason
    alive_content
  2. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 00:00:47.000000
    Evidence SHA-256
    dd93c3b774f5a9dc98b95109756e28172cdf32ebc0d7fc8757c0418b3ee68ca7
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 00:00:47
    Evidence reason
    alive_content
  3. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 12:00:53.000000
    Evidence SHA-256
    12ca7f78ba1823fafe7146aa87964fc979ad9334e87905051a805f2e54a6cf7c
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 12:00:53
    Evidence reason
    alive_content
  4. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 12:00:53.000000
    Evidence SHA-256
    12ca7f78ba1823fafe7146aa87964fc979ad9334e87905051a805f2e54a6cf7c
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 12:00:53
    Evidence reason
    alive_content
  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 02:54:11.935301
    Evidence SHA-256
    f3049ef8aa957a0c75d1f37b703ae6008630522768f5aca88bbd9915c9e1400b
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true
  6. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    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-10-25 02:08:59.000000
    Evidence SHA-256
    69e6dd4c6e973915813cf7b89e2c7dd254f16502a41c352b07815bbe8ea7901f
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 02:08:59
    Evidence reason
  7. 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-10-25 02:08:59.000000
    Evidence SHA-256
    69e6dd4c6e973915813cf7b89e2c7dd254f16502a41c352b07815bbe8ea7901f
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 02:08:59
    Evidence reason

Recorded activity

7 entries
  1. AlienVault OTX

    1 community references

    View source
  2. VirusTotal

    16/92 engine detections

    View source
  3. Added to PhishDestroy

    crypto-legacy.org

    View source
  4. Abuse report sent

    PD-20261025-5525DA

    abuse@idealhosting.net.tr
  5. URLScan

    Page captured

    View source
  6. Cloudflare Radar

    Phishing

    View source
  7. Wayback Machine

    Page archived

    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.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecSiteReview AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation

Check for cloaking

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

crypto-legacy.org

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 16 det. ChainPatrol URLQuery Report stored SSL Labs Stored certificate dates valid CF Radar Malicious OTX 1 ref WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20261025-5525DA Recipient: abuse@idealhosting.net.tr
PDF notice generated
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
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.

Immediate steps Find reporting contacts

Official reporting routes

Chainabuse
Report a crypto wallet, transaction, or phishing URL
SEAL-ISAC
Security Alliance crypto threat intelligence
PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect

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

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-legacy.org)
  • 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

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.

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-legacy.org"
  title="PhishDestroy threat report for crypto-legacy.org"
  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>