Skip to security report
Recorded security signals
Stored VirusTotal result: 17/92 engines flagged. malicious: 14. suspicious: 3. Analysis time (as stored): 2026-10-27T19:16:31Z. Retrieved (as stored): 2026-10-31T00:18:31Z. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
legacybitfundexengine.com favicon

legacybitfundexengine.com

In short

PhishDestroy first recorded legacybitfundexengine.com on 2026-10-31. Stored VirusTotal result: 17/92 engines flagged. malicious: 14. suspicious: 3. Analysis time (as stored): 2026-10-27T19:16:31Z. Retrieved (as stored): 2026-10-31T00:18:31Z.

“Legacy Bitfundex | AI Trading Platform | Official Website”

Registrar
MainReg
Resolved IP
Netherlands185.62.57.10Snel.com B.V.
Registered
Jul 16, 2026
First observed
Oct 31, 2026
PhishDestroy assessment Critical
100/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
VirusTotal detections: 17/92
VirusTotal
engine detections ·
OTX
community references
URLScan
engine verdict · score 99
Cloudflare Radar
Page captures
open gallery
Domain age
registered 2026-07-16 according to WHOIS
OTX: 1 ref Oct 31, 2026
X Telegram API

Analysis

Domain summary

PhishDestroy first recorded legacybitfundexengine.com on 2026-10-31. Stored VirusTotal result: 17/92 engines flagged. malicious: 14. suspicious: 3. Analysis time (as stored): 2026-10-27T19:16:31Z. Retrieved (as stored): 2026-10-31T00:18:31Z. Risk: critical (100/100). Registrar: MainReg. Status: Last known active. Hosting: Snel.com B.V. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
17 / 92
Hosting
Netherlands185.62.57.10Snel.com B.V.
Registrar
MainReg
Registered
Jul 16, 2026
OTX
1 community ref
Page captures
5

Recorded source summary

PhishDestroy stores a record for legacybitfundexengine.com. Source observations are dated separately; missing checks do not establish safety.

A reviewed analysis is not available for this text revision. Consult the dated source records below.

Source evidenceVirusTotal 17 / 92 · OTX 1 references 7 sources

VirusTotal

17 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
44
Malicious
14
Suspicious
3
Undetected
31

Vendor labels

DNS8
suspicious
ESET
suspicious
VIPRE
phishing
G-Data
phishing
Lionic
phishing
Sophos
phishing
CyRadar
phishing
Webroot
malicious
Fortinet
phishing
SOCRadar
phishing
Kaspersky
phishing
Seclookup
malicious
Gridinsoft
suspicious
SafeToOpen
phishing
BitDefender
phishing
alphaMountain.ai
phishing
Forcepoint ThreatSeeker
phishing

Reputation score

0

Registrar

MainReg Inc.

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    21600
    Type
    NS
    Value
    coraline.ns.cloudflare.com
  • TTL, seconds
    1800
    Type
    SOA
    Responsible mailbox
    dns.cloudflare.com
    Value
    coraline.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    A
    Value
    185.62.57.10
  • TTL, seconds
    21600
    Type
    NS
    Value
    toby.ns.cloudflare.com

DNS records observed

JARM fingerprint

40d40d40d00000000043d43d00043d6aff5ab0f4fc31897186312c9e639319

Certificate

Subject alternative names
  • legacybitfundexengine.com
Issuer
ZeroSSL GmbH / ZeroSSL ECC DV SSL CA 2
Serial
4ffbb6075bd485cb71e74cb5df0d812
SHA-256
9bd5b8d3899bc90ae9a4b6c8be16d3745181b36607fd1866bc9087450f3db05a
Subject
legacybitfundexengine.com
Valid until
Valid from

Registration record

Registrar
MainReg Inc.
Registrar IANA ID
1917
Registrar URL
http://www.mainreg.com
Registered
Updated
Expires
Status
  • ok
Nameservers
  • coraline.ns.cloudflare.com
  • toby.ns.cloudflare.com
DNSSEC
unsigned

Registry data (RDAP)

Status
  • active
Registry events
Last changed
Registration
Registrar expiration
Last RDAP database update
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 44,
    "malicious": 14,
    "suspicious": 3,
    "undetected": 31
}
Vendor labels
{
    "DNS8": "suspicious",
    "ESET": "suspicious",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Webroot": "malicious",
    "Fortinet": "phishing",
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "Seclookup": "malicious",
    "Gridinsoft": "suspicious",
    "SafeToOpen": "phishing",
    "BitDefender": "phishing",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Registrar
MainReg Inc.
Created
2026-07-16T14:51:05Z
Expires
2027-07-16T14:51:05Z
Updated
2026-07-16T16:25:03Z
First seen
2026-07-16T17:08:33Z
DNS records
[
    {
        "ttl": 21600,
        "type": "NS",
        "value": "coraline.ns.cloudflare.com"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "coraline.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "185.62.57.10"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "toby.ns.cloudflare.com"
    }
]
Dns at
2026-10-27T19:22:22Z
Jarm
40d40d40d00000000043d43d00043d6aff5ab0f4fc31897186312c9e639319
Certificate
{
    "san": [
        "legacybitfundexengine.com"
    ],
    "issuer": "ZeroSSL GmbH / ZeroSSL ECC DV SSL CA 2",
    "serial": "4ffbb6075bd485cb71e74cb5df0d812",
    "sha256": "9bd5b8d3899bc90ae9a4b6c8be16d3745181b36607fd1866bc9087450f3db05a",
    "subject": "legacybitfundexengine.com",
    "valid_to": "2026-12-18T23:59:59Z",
    "valid_from": "2026-09-19T00:00:00Z"
}
Registration record
{
    "registrar": "MainReg Inc.",
    "registrar_iana_id": "1917",
    "registrar_url": "http://www.mainreg.com",
    "created": "2026-07-16T14:51:05Z",
    "updated": "2026-07-16T16:25:03Z",
    "expires": "2027-07-16T14:51:05Z",
    "status": [
        "ok"
    ],
    "nameservers": [
        "coraline.ns.cloudflare.com",
        "toby.ns.cloudflare.com"
    ],
    "dnssec": "unsigned"
}
Registry data
{
    "status": [
        "active"
    ],
    "events": {
        "last changed": "2026-07-16T00:00:00Z",
        "registration": "2026-07-16T00:00:00Z",
        "registrar expiration": "2027-07-16T00:00:00Z",
        "last update of RDAP database": "2026-10-27T19:22:00Z"
    }
}
Separate collector summary

This is a separate stored result. Its counts, vendors and dates do not replace the provider observation above. A retrieval date is not an analysis date.

source
VirusTotal
scope
unknown
result_state
observed
numerator
17
denominator
92
malicious
null
suspicious
null
vendors
["alphaMountain.ai","BitDefender","CyRadar","DNS8","ESET","Forcepoint ThreatSeeker","Fortinet","G-Data","Gridinsoft","Kaspersky","Lionic","SafeToOpen","Seclookup","SOCRadar","Sophos","VIPRE","Webroot"]
observed_at
2026-10-27 19:16:31
checked_at
2026-10-31 01:18:46
fetched_at
2026-10-31 00:18:47
time_basis
as stored; legacy timezone not established

Cloudflare Radar

Phishing

Open report
Cloudflare RadarOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Report ID

47e9e953-66a9-4181-8929-c9212319f266

Final URL

https://legacybitfundexengine.com/

HTTP response

200

Navigation history

  • URL
    https://legacybitfundexengine.com/
    Status
    200

DOM structure hash

6f80c91f92f2305dd91d1a7cc190197b0b6ff870b7e0fa5fed954758f35806dc

Document hash

1af52df16a4c78b326a13307a97c33a44dbec367751a1d7e0b68e777a5848791

Phishing classifier result

  • phishing

Domain risk categories

  • Malware
  • Security threats
  • CIPA Filter
  • CIPA

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    legacybitfundexengine.com
    Type
    A
    Value
    185.62.57.10

DNSSEC valid

No

IP address

127.0.1.25

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

Verdict

Tags
  • malware
Malicious
Yes
Categories
  • malware

Registration record

Registrar
MainReg Inc.
Registered
Updated
Expires
Nameservers
  • coraline.ns.cloudflare.com
  • toby.ns.cloudflare.com
Original source fields · JSON
Uuid
47e9e953-66a9-4181-8929-c9212319f266
Final url
https://legacybitfundexengine.com/
Status
200
History
[
    {
        "url": "https://legacybitfundexengine.com/",
        "status": 200
    }
]
DOM structure hash
6f80c91f92f2305dd91d1a7cc190197b0b6ff870b7e0fa5fed954758f35806dc
Document hash
1af52df16a4c78b326a13307a97c33a44dbec367751a1d7e0b68e777a5848791
Phishing v2
[
    "phishing"
]
Domain risks
[
    "Malware",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "legacybitfundexengine.com",
        "type": "A",
        "value": "185.62.57.10"
    }
]
Dnssec valid
false
Ip
127.0.1.25

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

Verdict
{
    "tags": [
        "malware"
    ],
    "malicious": true,
    "categories": [
        "malware"
    ]
}
Registration record
{
    "registrar": "MainReg Inc.",
    "created": "2026-07-16T14:51:05Z",
    "updated": "2026-07-16T16:25:03Z",
    "expires": "2027-07-16T14:51:05Z",
    "nameservers": [
        "coraline.ns.cloudflare.com",
        "toby.ns.cloudflare.com"
    ]
}

URLScan

Malicious · engine verdict · score 99

SHA-256 d5ec1a87289634066eab8e003dab1e90d5f01d4163f3115b2f3e789a114622e1

Open report
URLScanOriginal source recordObserved: 23 fields

Observed: · Retrieved:

Report ID

019f8911-8089-717e-b8cf-5a6f2fd7b00d

Final URL

https://legacybitfundexengine.com/

HTTP response

200

Redirect type

https-only

Redirects

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

IP address

185.62.57.10

Reverse DNS (PTR)

s46026.hosted-by-snel.com

Contacted domains

  • cdn.jsdelivr.net
  • fonts.gstatic.com
  • cdnjs.cloudflare.com
  • www.cloudflare.com
  • fonts.googleapis.com

Contacted IP addresses

  • 142.251.20.94
  • 104.17.208.5
  • 104.16.123.96
  • 2606:4700::6811:d005
  • 104.17.25.14
  • 2a00:1450:400a:1001::5f
  • 185.62.57.10

Autonomous systems (ASN)

  • 15169
  • 13335
  • 62370

Server countries

  • US
  • CH
  • NL

Document hash

f94cdd9ea82248204c6d5a44b1c91bc55483d49733d61fcfebf6861b9487c7ac

Script hashes

  • e776c8e03ae39686bf5344edf2667ee34a517077e47c1b709c3cc2c8dd1792c3

JavaScript globals

  • toggleTermsPopup
  • intlTelInput
  • FingerprintJS
  • __visitorCountry

Browser storage keys

  • t_fingerprint

TLS session and certificate

Subject alternative names
  • legacybitfundexengine.com
Cipher
CHACHA20_POLY1305
Issuer
ZeroSSL ECC DV SSL CA 2
Subject
legacybitfundexengine.com
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

5

Registered domain age, days

5

Certificate age, days

1

Certificate validity, days

90

Page requests

20

Provider verdicts

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

HTTP headers

Content-type
text/html; charset=utf-8
Referrer-policy
no-referrer-when-downgrade
Original source fields · JSON
Uuid
019f8911-8089-717e-b8cf-5a6f2fd7b00d
Final url
https://legacybitfundexengine.com/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://legacybitfundexengine.com/",
        "from": "http://legacybitfundexengine.com/",
        "status": 307
    }
]
Ip
185.62.57.10
Ptr
s46026.hosted-by-snel.com
Contacted domains
[
    "cdn.jsdelivr.net",
    "fonts.gstatic.com",
    "cdnjs.cloudflare.com",
    "www.cloudflare.com",
    "fonts.googleapis.com"
]
Contacted IP addresses
[
    "142.251.20.94",
    "104.17.208.5",
    "104.16.123.96",
    "2606:4700::6811:d005",
    "104.17.25.14",
    "2a00:1450:400a:1001::5f",
    "185.62.57.10"
]
Asns
[
    "15169",
    "13335",
    "62370"
]
Countries
[
    "US",
    "CH",
    "NL"
]
Document hash
f94cdd9ea82248204c6d5a44b1c91bc55483d49733d61fcfebf6861b9487c7ac
Script hashes
[
    "e776c8e03ae39686bf5344edf2667ee34a517077e47c1b709c3cc2c8dd1792c3"
]
Globals
[
    "toggleTermsPopup",
    "intlTelInput",
    "FingerprintJS",
    "__visitorCountry"
]
Storage keys
[
    "t_fingerprint"
]
Tls
{
    "san": [
        "legacybitfundexengine.com"
    ],
    "cipher": "CHACHA20_POLY1305",
    "issuer": "ZeroSSL ECC DV SSL CA 2",
    "subject": "legacybitfundexengine.com",
    "protocol": "TLS 1.3",
    "valid_to": "2026-10-19T23:59:59Z",
    "valid_from": "2026-07-21T00:00:00Z"
}
Domain age days
5
Apex age days
5
Tls age days
1
Tls valid days
90
Requests
20
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 99,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "content-type": "text/html; charset=utf-8",
    "referrer-policy": "no-referrer-when-downgrade"
}
Separate monitor record · 2026-10-31 04:30 UTC

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

record_source
domain_monitor.urlscan
uuid
019f8911-8089-717e-b8cf-5a6f2fd7b00d
score
0
malicious
false
result_at
2026-10-31T04:30:13Z
enriched_at
2026-10-31T09:10:57Z
source_timestamps
{"urlscan_result_at":"2026-10-31 05:30:13","urlscan_enriched_at":"2026-10-31 10:10:57"}
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

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

Open report
Separate monitor score · 25 / 100 · 2026-10-31T00:37:23Z

This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.

record_source
domain_monitor.dom_analysis
heuristic_score
25
analyzed_at
2026-10-31T00:37:23Z
source_timestamp
2026-10-31 01:37:23
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

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: 25 fields

Mail configuration

SPF lookups
0

CAA records

Domain
legacybitfundexengine.com

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Web archive observations

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

Crawler rules

User agents
  • *
Present
Yes
Sitemap URLs
  • https://legacybitfundexengine.com/sitemap.xml

Sitemap

Present
Yes
URL count
140

Page title and metadata

Page title
Legacy Bitfundex | AI Trading Platform | Official Website
Indexing directives
index, follow
Theme color
#0f0f1a
Description
Legacy Bitfundex delivers a premium, AI-enhanced trading assistant and automation toolkit, outlining streamlined workflows, precise controls, and execution strategies designed for disciplined, data-driven investing.
Canonical URL
https://legacybitfundexengine.com/

Trackers

Requests
20
Observed services
  • Name
    Cloudflare
    Company
    Cloudflare
    Country
    US
    Category
    Hosting
    Requests
    6
  • Name
    Google Fonts
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    1
  • Name
    Google Static
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    3
  • Name
    jsDelivr
    Company
    jsDelivr
    Category
    Hosting
    Requests
    3

Forms and mixed content

Scripts without SRI
  • https://cdn.jsdelivr.net/npm/intl-tel-input@23/build/js/intlTelInput.min.js
Third-party scripts
1

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
27
TLS
32
Waiting
15
Connection
18
Download
42
Response time, ms
134

TLS connection

ALPN
h2
Cipher
TLS_CHACHA20_POLY1305_SHA256
Protocol
TLSv1.3
Supported versions
  • TLSv1.2
  • TLSv1.3
Certificate authorized
Yes
OCSP stapling
Yes
Forward secrecy
Yes

Ports

Open ports
  • 80
  • 443

Carbon estimate

Bytes
44638
CO₂, grams
0.0016
Cleaner than, %
39

DNS servers

Nameservers
  • IP address
    172.64.34.88
    Host
    coraline.ns.cloudflare.com
  • IP address
    108.162.193.239
    Host
    toby.ns.cloudflare.com
DNS zone
legacybitfundexengine.com

Location

IP address
185.62.57.10
ASN
62370
Organization
Snel.com B.V.
City
Rotterdam
Country
NL

TLS certificate

Issuer
ZeroSSL GmbH / ZeroSSL ECC DV SSL CA 2
Subject
legacybitfundexengine.com

DNS records

A
  • 185.62.57.10
NS
  • coraline.ns.cloudflare.com
  • toby.ns.cloudflare.com
SOA
Primary nameserver
coraline.ns.cloudflare.com
Hostmaster
dns.cloudflare.com
Serial
2415310617
Refresh, seconds
10000
Retry, seconds
2400
Expiry, seconds
604800
Minimum TTL, seconds
1800

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Observation
Site does not serve any HSTS headers.

HTTP security policies

X-Frame-Options
No
Referrer-Policy
no-referrer-when-downgrade
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.62.57.10
IP version
4

Redirects

Redirect chain
  • https://legacybitfundexengine.com

Page links

Internal links
11

Registration record

Registrar
MainReg Inc.
Registered
Updated
Expires
Status
  • ok https://icann.org/epp
Nameservers
  • coraline.ns.cloudflare.com
  • toby.ns.cloudflare.com

HTTP headers

Response headers
Content-type
text/html; charset=utf-8
Referrer-policy
no-referrer-when-downgrade
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "legacybitfundexengine.com"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2026-10-12T08:11:52Z",
    "first": "2026-10-12T08:11:52Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 12446
}
Crawler rules
{
    "agents": [
        "*"
    ],
    "present": true,
    "sitemaps": [
        "https://legacybitfundexengine.com/sitemap.xml"
    ]
}
Sitemap
{
    "present": true,
    "url_count": 140
}
Page title and metadata
{
    "title": "Legacy Bitfundex | AI Trading Platform | Official Website",
    "robots": "index, follow",
    "themeColor": "#0f0f1a",
    "description": "Legacy Bitfundex delivers a premium, AI-enhanced trading assistant and automation toolkit, outlining streamlined workflows, precise controls, and execution strategies designed for disciplined, data-driven investing.",
    "canonicalUrl": "https://legacybitfundexengine.com/"
}
Trackers
{
    "requests": 20,
    "trackers": [
        {
            "name": "Cloudflare",
            "company": "Cloudflare",
            "country": "US",
            "category": "Hosting",
            "requests": 6
        },
        {
            "name": "Google Fonts",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 1
        },
        {
            "name": "Google Static",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 3
        },
        {
            "name": "jsDelivr",
            "company": "jsDelivr",
            "category": "Hosting",
            "requests": 3
        }
    ]
}
Forms and mixed content
{
    "no_sri": [
        "https://cdn.jsdelivr.net/npm/intl-tel-input@23/build/js/intlTelInput.min.js"
    ],
    "third_party_scripts": 1
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 27,
        "tls": 32,
        "wait": 15,
        "connect": 18,
        "download": 42
    },
    "response_ms": 134
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_CHACHA20_POLY1305_SHA256",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "ocsp_stapled": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443
    ]
}
Carbon
{
    "bytes": 44638,
    "co2_grams": 0.0016,
    "cleaner_than": 39
}
Dns server
{
    "ns": [
        {
            "ip": "172.64.34.88",
            "host": "coraline.ns.cloudflare.com"
        },
        {
            "ip": "108.162.193.239",
            "host": "toby.ns.cloudflare.com"
        }
    ],
    "zone": "legacybitfundexengine.com"
}
Location
{
    "ip": "185.62.57.10",
    "asn": "62370",
    "org": "Snel.com B.V.",
    "city": "Rotterdam",
    "country": "NL"
}
Ssl
{
    "issuer": "ZeroSSL GmbH / ZeroSSL ECC DV SSL CA 2",
    "subject": "legacybitfundexengine.com"
}
DNS records
{
    "A": [
        "185.62.57.10"
    ],
    "NS": [
        "coraline.ns.cloudflare.com",
        "toby.ns.cloudflare.com"
    ],
    "SOA": "{\"nsname\": \"coraline.ns.cloudflare.com\", \"hostmaster\": \"dns.cloudflare.com\", \"serial\": 2415310617, \"refresh\": 10000, \"retry\": 2400, \"expire\": 604800, \"minttl\": 1800}"
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": "no-referrer-when-downgrade",
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "185.62.57.10",
    "family": 4
}
Redirects
{
    "chain": [
        "https://legacybitfundexengine.com"
    ]
}
Page links
{
    "internal_count": 11
}
Registration record
{
    "registrar": "MainReg Inc.",
    "created": "2026-07-16T14:51:05Z",
    "updated": "2026-07-16T16:25:03Z",
    "expires": "2027-07-16T14:51:05Z",
    "status": [
        "ok https://icann.org/epp"
    ],
    "nameservers": [
        "coraline.ns.cloudflare.com",
        "toby.ns.cloudflare.com"
    ]
}
HTTP headers
{
    "headers": {
        "content-type": "text/html; charset=utf-8",
        "referrer-policy": "no-referrer-when-downgrade"
    }
}
Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Malware Malware Security threats

Questions about legacybitfundexengine.com

Is legacybitfundexengine.com legit?

PhishDestroy rates legacybitfundexengine.com as critical risk (100/100) from the recorded evidence; it was first recorded on 2026-10-31. Stored VirusTotal result: 17/92 engines flagged. malicious: 14. suspicious: 3. Analysis time (as stored): 2026-10-27T19:16:31Z. Retrieved (as stored): 2026-10-31T00:18:31Z. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is legacybitfundexengine.com safe to connect a wallet?

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

What should I do if I used legacybitfundexengine.com?

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

Explore

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

Last checked

Stored Capture · 5 captures

All capture links and hashes (5)

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 99 report ↗
IP Reputation Netherlands185.62.57.10 abuse score 1/100 1 report PhishingBad Web Bot checked Oct 31, 2026 last reported
Registrar MainReg
Hosting abuse contact complain@mainreg.com Snel.com B.V. · AS62370
RegistrationCreated Jul 16, 2026 (114d) — Expires Jul 16, 2027
WHOIS statusok
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedOct 31, 2026
DOM Analysisanalyzed Oct 31, 2026score 25/1002 brand signals
Submitted URLhttp://legacybitfundexengine.com/
Favicon Hash
Observed page title
Legacy Bitfundex | AI Trading Platform | Official Website
Automated brand references
Across Argent
TLS Certificate
Issued by ZeroSSL GmbH / ZeroSSL ECC DV SSL CA 2 · stored validity ends in 40 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
Netherlands185.62.57.10
Network ASN
AS62370
AS name
Snel Snel.com B.V., NL
Organization
Snel.com B.V.
Observed location
NetherlandsRotterdam, NL
Server header
ESF

Nameservers 2

  • coraline.ns.cloudflare.com
  • toby.ns.cloudflare.com

SOA

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

Registrar abuse contact VirusTotal WHOIS

Location describes the IP network.

TLS certificate

Issuer
ZeroSSL GmbH / ZeroSSL ECC DV SSL CA 2
Valid from
2026-09-19 00:00:00
Valid until
2026-12-18 23:59:59
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint9bd5b8d3899bc90ae9a4b6c8be16d3745181b36607fd1866bc9087450f3db05a
Certificate names · 1 SAN
  • legacybitfundexengine.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-11-07 23:35:05 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: Content serving Content: Content served at root DNS: Resolved Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-11-07 23:35:05 UTC
RDAP registration
Observed timeline last reachable: 2026-11-07 23:35:05 UTC last content: 2026-11-07 23:35:05 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.
Technologies · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

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

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of legacybitfundexengine.com · checked Oct 31, 2026

81
Needs Work
Performance
FCP
0.79 s
First Contentful Paint
LCP
0.79 s
Largest Contentful Paint
CLS
0.306
Cumulative Layout Shift
TBT
205 ms
Total Blocking Time
SI
0.96 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://legacybitfundexengine.com/
Final URL: https://legacybitfundexengine.com/
Legacy Bitfundex | AI Trading Platform | Official Website
Legacy Bitfundex delivers a premium, AI-enhanced trading assistant and automation toolkit, outlining streamlined workflows, precise controls, and execution strategies designed for disciplined, data-driven investing.
Response
HTTP 200
HTML body
43.6 KB
Compressed
11.1 KB
Links
29 internal · 0 external
Selected response headers
Content-Encoding: gzip
Content-Type: text/html; charset=utf-8
Security headers present
Referrer-Policy
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Saved response-header values · 9
Alt-Svc
h3=":443"; ma=2592000
Content-Encoding
gzip
Content-Type
text/html; charset=utf-8
Date
Sat, 31 Oct 2026 00:18:00 GMT
Etag
"dm9jlkwb0rugyfy-gzip"
Last-Modified
Tue, 20 Oct 2026 09:02:47 GMT
Referrer-Policy
no-referrer-when-downgrade
Transfer-Encoding
chunked
Vary
Accept-Encoding

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

Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

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

Captured network requests

Network requests: 20 SHA-256 hashes: 20 URLScan scan:

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

Open this scan on URLScan 019f8911-8089-717e-b8cf-5a6f2fd7b00d ↗

Stored observation history8

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

    live_content

    content_served

  2. Availability monitor · Recorded state

    live_content

    content_served

  3. Availability monitor · Recorded state

    live_content

    content_served

  4. Availability monitor · Recorded state

    live_content

    content_served

  5. Availability monitor · Recorded state

    live_content

    content_served

Earlier observations 3
  1. Availability monitor · Recorded state

    live_content

    content_served

  2. Availability monitor · Recorded state

    live_content

    content_served

  3. Availability monitor · Recorded state

    live_content

    content_served

All retained availability observations35

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
    resolved
    DNS response code
    NOERROR
    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-11-08 00:35:05.000000
    Evidence SHA-256
    434439dbb3b95bb2e0bcce56494731fb03a3f07f63f3a815c9ebe0f432c8bc63
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-08 00:35:05
    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-11-08 00:35:05.000000
    Evidence SHA-256
    434439dbb3b95bb2e0bcce56494731fb03a3f07f63f3a815c9ebe0f432c8bc63
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-08 00:35:05
    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
    resolved
    DNS response code
    NOERROR
    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-11-07 12:33:19.000000
    Evidence SHA-256
    d961d4640de6ce8b7c1b6dede0875c8a46d8df71ed37df53291f16b72c85a313
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-07 12:33:19
    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-11-07 12:33:19.000000
    Evidence SHA-256
    d961d4640de6ce8b7c1b6dede0875c8a46d8df71ed37df53291f16b72c85a313
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-07 12:33:19
    Evidence reason
    alive_content
  5. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-07 11:22:04.554093
    Evidence SHA-256
    d0d729b70687a3b7d23361551b91f9c7b204c4eac655fb0a10da8512b094b9d2
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-07 11:22:04.554093
    Evidence reason
  6. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    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-11-07 04:10:44.000000
    Evidence SHA-256
    7f689fc376eaebf24737e6c231df8464764b7713822208daa6f0fcf6e0568429
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-07 04:10:44
    Evidence reason
    alive_content
  7. 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-11-07 04:10:44.000000
    Evidence SHA-256
    7f689fc376eaebf24737e6c231df8464764b7713822208daa6f0fcf6e0568429
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-07 04:10:44
    Evidence reason
    alive_content
  8. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    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-11-07 00:02:52.000000
    Evidence SHA-256
    d2ded13d53b5750b209c20c1c17e3b56fb99bdb0b39f041147e28dff4c15e0d5
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-07 00:02:52
    Evidence reason
    alive_content
  9. 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-11-07 00:02:52.000000
    Evidence SHA-256
    d2ded13d53b5750b209c20c1c17e3b56fb99bdb0b39f041147e28dff4c15e0d5
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-07 00:02:52
    Evidence reason
    alive_content
  10. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-06 11:21:21.802256
    Evidence SHA-256
    1f12882395a474d0dfb24be8d84353a7af90bb8bd997a0dda9b412ed89cd7a3f
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-06 11:21:21.802256
    Evidence reason
  11. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-05 11:21:21.318386
    Evidence SHA-256
    547991b570db3c8269bee0185b7fa12df05c0b418f4b7a797fb4d0bb740e4f46
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-05 11:21:21.318386
    Evidence reason
  12. 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-11-05 01:09:36.000000
    Evidence SHA-256
    8c207c02bdd2e339007550eb108dfcb152e8148bac01d41cb3852e366aa1cc71
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-05 01:09:36
    Evidence reason
    alive_content
  13. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-05 01:09:36.000000
    Evidence SHA-256
    c63968c3b1c6f137c62d0fe46d36b6603d40f63d345b514574cb3b5b07c118c7
    Evidence timestamp as recorded
    2026-11-05 01:09:36
    DNS evidence marked stale
    false
    HTTP evidence marked stale
    true
  14. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    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-11-04 13:11:10.000000
    Evidence SHA-256
    ab989f9bc07b87d94578931625d0d6fe2d18a6cd48dd5135fec586653045492a
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-04 13:11:10
    Evidence reason
    alive_content
  15. 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-11-04 13:11:10.000000
    Evidence SHA-256
    ab989f9bc07b87d94578931625d0d6fe2d18a6cd48dd5135fec586653045492a
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-04 13:11:10
    Evidence reason
    alive_content
  16. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-04 11:21:00.849465
    Evidence SHA-256
    94a9ae3d707b6cefa8168740bcb51c53137079a19bc0cd5bd77154e93c534a76
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-04 11:21:00.849465
    Evidence reason
  17. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-03 11:20:42.213040
    Evidence SHA-256
    7f511289ea6b6d1520a698f000d7fb3be1609f5f14dbf5ab5bf1c58eb4dbb974
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-03 11:20:42.213040
    Evidence reason
  18. current_http_probeunknown
    Observation source
    current_http_probe
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 12:31:22.000000
    Evidence SHA-256
    3ea72b423cc84182f6ca5d5422dbde6d099f0c92c700ce5b719c05c23cbc1dd8
    Evidence timestamp as recorded
    2026-11-02 12:31:22
    DNS evidence marked stale
    false
    HTTP evidence marked stale
    true
  19. 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-11-02 12:31:22.000000
    Evidence SHA-256
    cd7af256ae6f4bc05ad601e9d6c8b2952a12567bbb1b2f7238098c19dca75766
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 12:31:22
    Evidence reason
    alive_content
  20. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-02 11:20:40.834886
    Evidence SHA-256
    6b72dd67b3184766be6163de1e7b9604e36c85641b1d2618e2bdbe21069459a2
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-02 11:20:40.834886
    Evidence reason
  21. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    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-11-02 00:05:28.000000
    Evidence SHA-256
    ebabb47ba86a7ec6fc6ada2b8a8baf3219306d1e8d74575c6ca6463a7d51ec8d
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 00:05:28
    Evidence reason
    alive_content
  22. 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-11-02 00:05:28.000000
    Evidence SHA-256
    ebabb47ba86a7ec6fc6ada2b8a8baf3219306d1e8d74575c6ca6463a7d51ec8d
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-02 00:05:28
    Evidence reason
    alive_content
  23. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    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-11-01 12:06:16.000000
    Evidence SHA-256
    16e0b8bb78120739860606767dcf4d5df91ddcbb302489a8506d1502747e4b63
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 12:06:16
    Evidence reason
    alive_content
  24. 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-11-01 12:06:16.000000
    Evidence SHA-256
    16e0b8bb78120739860606767dcf4d5df91ddcbb302489a8506d1502747e4b63
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 12:06:16
    Evidence reason
    alive_content
  25. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 11:20:10.198716
    Evidence SHA-256
    b2987bb7a7acc32f1f9011b7a56a5a9a8539c203c0dded9abde43c0e22a9adeb
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-01 11:20:10.198716
    Evidence reason
  26. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    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-11-01 03:49:41.000000
    Evidence SHA-256
    c7a28fb2befbbeb0ce08533526f2b7fb89ddeade65a068f449d6b611f6b35632
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 03:49:41
    Evidence reason
    alive_content
  27. 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-11-01 03:49:41.000000
    Evidence SHA-256
    c7a28fb2befbbeb0ce08533526f2b7fb89ddeade65a068f449d6b611f6b35632
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 03:49:41
    Evidence reason
    alive_content
  28. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    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-11-01 00:04:35.000000
    Evidence SHA-256
    f9753f9640a800fb6b57ab6fdf4da738888afa7513179eb0f34186d487056bcc
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 00:04:35
    Evidence reason
    alive_content
  29. 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-11-01 00:04:35.000000
    Evidence SHA-256
    f9753f9640a800fb6b57ab6fdf4da738888afa7513179eb0f34186d487056bcc
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 00:04:35
    Evidence reason
    alive_content
  30. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    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-31 12:04:54.000000
    Evidence SHA-256
    c71d495c8714f907fa823d23d631178a89015794cd44e9b6f83c76036f1ec800
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 12:04:54
    Evidence reason
    alive_content
  31. 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-31 12:04:54.000000
    Evidence SHA-256
    c71d495c8714f907fa823d23d631178a89015794cd44e9b6f83c76036f1ec800
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 12:04:54
    Evidence reason
    alive_content
  32. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 11:20:09.112163
    Evidence SHA-256
    b5c6551e799cfe4d3cb298004536f14652a7bd27158039d9a8bde93b0611124a
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-31 11:20:09.112163
    Evidence reason
  33. 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-31 03:00:13.000000
    Evidence SHA-256
    c43e44fc0ebaa1477b9967b81c98c0627fe84e0ffcefe0ebf7398b0b33d8b06f
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 03:00:13
    Evidence reason
    alive_content
  34. 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-31 03:00:13.000000
    Evidence SHA-256
    c43e44fc0ebaa1477b9967b81c98c0627fe84e0ffcefe0ebf7398b0b33d8b06f
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 03:00:13
    Evidence reason
    alive_content
  35. 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-31 01:19:51.795542
    Evidence SHA-256
    f3049ef8aa957a0c75d1f37b703ae6008630522768f5aca88bbd9915c9e1400b
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true

Threat Response Pipeline

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

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

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

Recorded activity

6 entries
  1. Wayback Machine

    Page archived

    View source
  2. AlienVault OTX

    1 community references

    View source
  3. Cloudflare Radar

    Phishing

    View source
  4. Added to PhishDestroy

    legacybitfundexengine.com

    View source
  5. VirusTotal

    17/92 engine detections

    View source
  6. URLScan

    Malicious · engine verdict · score 99

    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.

All stored records by source

Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.

Download all records as JSON

Check for cloaking

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

legacybitfundexengine.com

Evidence & External Reports

Deep Analysis
Help & reporting

Were You Affected by This Site?

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

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

Official reporting routes

More official reporting routes
FTC ReportFraud United States

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

IdentityTheft.gov United States

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

CISA United States

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

CSIRTs Network European Union

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

FIRST Worldwide

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

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

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

Report to Your Local Authorities

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

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

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

97-country directory

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

Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

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

What should I do immediately?

Urgent

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

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

What information should I collect for my report?

FBI guidelines

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including legacybitfundexengine.com)
  • Communications — emails, texts, phone numbers, usernames the scammer used

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

Where should I report the scam?

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

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

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

How can I protect myself in the future?

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

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

Stay Informed, Stay Safe

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

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

This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.

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