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

nexlares.shop

In short

PhishDestroy records the nexlares.shop account creation page, which invites visitors to register for guided AI-driven trading onboarding.

“nexlares | AI Trading Platform | Official Website”

Review the evidence
Registrar
United StatesDynadot
Resolved IP
Netherlands185.62.58.129Snel.com B.V.
Registered
Apr 12, 2026
First observed
Nov 1, 2026
PhishDestroy assessment Critical
100/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 18/92
VirusTotal
18 / 92
engine detections ·
OTX
1
community references
URLScan
Malicious
engine verdict · score 98
Cloudflare Radar
Phishing
Page captures
9
open gallery
Domain age
203 days
registered 2026-04-12 according to WHOIS
OTX: 1 ref Nov 1, 2026
X Telegram API

Analysis

Domain summary

PhishDestroy records the nexlares.shop account creation page, which invites visitors to register for guided AI-driven trading onboarding.

Critical
Status
Last known active
VirusTotal
18 / 92
Hosting
Netherlands185.62.58.129Snel.com B.V.
Registrar
United StatesDynadot
Registered
Apr 12, 2026
OTX
1 community ref
Page captures
9
Page captures Source results Registration record

PhishDestroy analysis, reviewed version

The captured nexlares.shop page presents an account creation form headed "Create your nexlares account," asking for name, email, and phone number alongside a human-verification checkbox before a "Launch onboarding" button. The page frames itself as an enterprise trading operations platform with policy-compliant controls and AI-driven automation, while a disclaimer banner at the bottom states the site functions solely as a marketing platform.

The stored VirusTotal domain result reports 18 detections out of 92 engines. CRDF reported "malicious"; DNS8 reported "suspicious".

Source evidenceVirusTotal 18 / 92 · OTX 1 references 8 sources

VirusTotal

18 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 9 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
44
Malicious
15
Suspicious
3
Undetected
30

Vendor labels

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

Reputation score

0

Categories

Sophos
phishing and fraud
Webroot
Phishing and Other Frauds
alphaMountain.ai
Information Technology, Phishing (alphaMountain.ai)
Forcepoint ThreatSeeker
phishing and other frauds

First seen

DNS records

  • TTL, seconds
    300
    Type
    A
    Value
    185.62.58.129
  • TTL, seconds
    1800
    Type
    SOA
    Responsible mailbox
    dns.cloudflare.com
    Value
    nena.ns.cloudflare.com
  • TTL, seconds
    21600
    Type
    NS
    Value
    reese.ns.cloudflare.com
  • TTL, seconds
    21600
    Type
    NS
    Value
    nena.ns.cloudflare.com

DNS records observed

JARM fingerprint

40d40d40d00000000043d43d00043d6aff5ab0f4fc31897186312c9e639319

Certificate

Subject alternative names
  • nexlares.shop
Issuer
ZeroSSL GmbH / ZeroSSL ECC DV SSL CA 2
Serial
c9d081d078b440756fb2d8b9e0d2d34f
SHA-256
7395f3e51576ef442167d0c42adddcf534ec21ad88b804123a7d6b509e91249e
Subject
nexlares.shop
Valid until
Valid from
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 44,
    "malicious": 15,
    "suspicious": 3,
    "undetected": 30
}
Vendor labels
{
    "CRDF": "malicious",
    "DNS8": "suspicious",
    "ESET": "suspicious",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Webroot": "malicious",
    "Fortinet": "phishing",
    "SOCRadar": "phishing",
    "Seclookup": "malicious",
    "Gridinsoft": "suspicious",
    "SafeToOpen": "phishing",
    "BitDefender": "phishing",
    "Chong Lua Dao": "malicious",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Categories
{
    "Sophos": "phishing and fraud",
    "Webroot": "Phishing and Other Frauds",
    "alphaMountain.ai": "Information Technology, Phishing (alphaMountain.ai)",
    "Forcepoint ThreatSeeker": "phishing and other frauds"
}
First seen
2026-04-12T08:22:54Z
DNS records
[
    {
        "ttl": 300,
        "type": "A",
        "value": "185.62.58.129"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "nena.ns.cloudflare.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "reese.ns.cloudflare.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "nena.ns.cloudflare.com"
    }
]
Dns at
2026-10-27T23:52:23Z
Jarm
40d40d40d00000000043d43d00043d6aff5ab0f4fc31897186312c9e639319
Certificate
{
    "san": [
        "nexlares.shop"
    ],
    "issuer": "ZeroSSL GmbH / ZeroSSL ECC DV SSL CA 2",
    "serial": "c9d081d078b440756fb2d8b9e0d2d34f",
    "sha256": "7395f3e51576ef442167d0c42adddcf534ec21ad88b804123a7d6b509e91249e",
    "subject": "nexlares.shop",
    "valid_to": "2026-11-30T23:59:59Z",
    "valid_from": "2026-09-01T00:00:00Z"
}
Separate source record · 15 malicious + 3 suspicious / 92 · 2026-10-27 23:52:00 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-27T23:52:00Z
fetched_at
2026-11-01T03:11:08Z
stats
{"timeout":0,"harmless":44,"malicious":15,"suspicious":3,"undetected":30}

Cloudflare Radar

Phishing

Open report
Cloudflare RadarOriginal source recordObserved: 13 fields

Observed: · Retrieved:

Report ID

4e426223-0e2c-4399-9665-73d1199df207

Final URL

https://nexlares.shop/

HTTP response

200

Navigation history

  • URL
    https://nexlares.shop/
    Status
    200

DOM structure hash

9c95222f9d778bd7e6202853c04770f5a5e221838138b60bd7bba440d2f0b03b

Document hash

1e41a18ee948fd5fa59f679e0e90b33b147db7057147035d73676bb38e551738

Phishing classifier result

  • phishing

Domain risk categories

  • Malware
  • Security threats
  • CIPA Filter
  • CIPA

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    nexlares.shop
    Type
    A
    Value
    185.62.58.129

DNSSEC valid

No

IP address

127.0.1.12

127.0.1.12 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
Original source fields · JSON
Uuid
4e426223-0e2c-4399-9665-73d1199df207
Final url
https://nexlares.shop/
Status
200
History
[
    {
        "url": "https://nexlares.shop/",
        "status": 200
    }
]
DOM structure hash
9c95222f9d778bd7e6202853c04770f5a5e221838138b60bd7bba440d2f0b03b
Document hash
1e41a18ee948fd5fa59f679e0e90b33b147db7057147035d73676bb38e551738
Phishing v2
[
    "phishing"
]
Domain risks
[
    "Malware",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "nexlares.shop",
        "type": "A",
        "value": "185.62.58.129"
    }
]
Dnssec valid
false
Ip
127.0.1.12

127.0.1.12 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"
    ]
}

URLScan

Malicious · engine verdict · score 98

SHA-256 26c6970eac66b9f845a78ae5989fe92cda30c3d69780f3effebbaa8737123ef0

Open report
URLScanOriginal source recordObserved: 21 fields

Observed: · Retrieved:

Report ID

01a07ff6-0fa6-71f8-9b39-fb0133e25ddf

Final URL

https://nexlares.shop/

HTTP response

200

IP address

185.62.58.129

Reverse DNS (PTR)

static-129-58-62-185.hosted-by-snel.com

Contacted domains

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

Contacted IP addresses

  • 104.17.208.5
  • 142.251.14.94
  • 104.16.124.96
  • 2606:4700::6811:cf05
  • 104.17.25.14
  • 2a00:1450:4001:c13::5f
  • 185.62.58.129

Autonomous systems (ASN)

  • 13335
  • 15169
  • 62370

Server countries

  • US
  • DE
  • NL

Document hash

5b3cb51af7240591fd4c1d4a897eedcb62cd3551de3e11120cc5c11180bc9079

Script hashes

  • dcffb692e1e6bda024f7830b7f5a3fa758c06ede0ac195daebf2c9fe01442f3f

JavaScript globals

  • toggleTermsPopup
  • intlTelInput
  • ClientJS
  • __visitorCountry

Browser storage keys

  • t_cfp

TLS session and certificate

Subject alternative names
  • nexlares.shop
Cipher
AES_128_GCM
Issuer
ZeroSSL ECC DV SSL CA 2
Subject
nexlares.shop
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

148

Registered domain age, days

148

Certificate age, days

7

Certificate validity, days

90

Page requests

20

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
98
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
01a07ff6-0fa6-71f8-9b39-fb0133e25ddf
Final url
https://nexlares.shop/
Status
200
Ip
185.62.58.129
Ptr
static-129-58-62-185.hosted-by-snel.com
Contacted domains
[
    "cdn.jsdelivr.net",
    "cdnjs.cloudflare.com",
    "fonts.gstatic.com",
    "www.cloudflare.com",
    "fonts.googleapis.com"
]
Contacted IP addresses
[
    "104.17.208.5",
    "142.251.14.94",
    "104.16.124.96",
    "2606:4700::6811:cf05",
    "104.17.25.14",
    "2a00:1450:4001:c13::5f",
    "185.62.58.129"
]
Asns
[
    "13335",
    "15169",
    "62370"
]
Countries
[
    "US",
    "DE",
    "NL"
]
Document hash
5b3cb51af7240591fd4c1d4a897eedcb62cd3551de3e11120cc5c11180bc9079
Script hashes
[
    "dcffb692e1e6bda024f7830b7f5a3fa758c06ede0ac195daebf2c9fe01442f3f"
]
Globals
[
    "toggleTermsPopup",
    "intlTelInput",
    "ClientJS",
    "__visitorCountry"
]
Storage keys
[
    "t_cfp"
]
Tls
{
    "san": [
        "nexlares.shop"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "ZeroSSL ECC DV SSL CA 2",
    "subject": "nexlares.shop",
    "protocol": "TLS 1.3",
    "valid_to": "2026-11-30T23:59:59Z",
    "valid_from": "2026-09-01T00:00:00Z"
}
Domain age days
148
Apex age days
148
Tls age days
7
Tls valid days
90
Requests
20
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 98,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "content-type": "text/html; charset=utf-8",
    "referrer-policy": "no-referrer-when-downgrade"
}

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

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
nexlares.shop AI Trading Platform Account Sign-Up Page
ai_description
PhishDestroy records the nexlares.shop account creation page, which invites visitors to register for guided AI-driven trading onboarding.
ai_summary
The captured nexlares.shop page presents an account creation form headed "Create your nexlares account," asking for name, email, and phone number alongside a human-verification checkbox before a "Launch onboarding" button. The page frames itself as an enterprise trading operations platform with policy-compliant controls and AI-driven automation, while a disclaimer banner at the bottom states the site functions solely as a marketing platform. The stored VirusTotal domain result reports 18 detections out of 92 engines. CRDF reported "malicious"; DNS8 reported "suspicious".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-11-01 04:17:01
revision
5703e784b9fb85dc339e4174ea95a0ecaa66a826b258f2ba89c4d32711724a52
mode
reviewed
interpretation
Selected public package; text generation time is separate from source 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: 24 fields

Mail configuration

SPF lookups
0

CAA records

Domain
nexlares.shop

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Web archive observations

Last observation
First observation
Recorded changes
1
Archived days
2
Snapshots per day
0.06
Average page size, bytes
12636

Crawler rules

User agents
  • *
Present
Yes
Sitemap URLs
  • https://nexlares.shop/sitemap.xml

Sitemap

Present
Yes
URL count
140

Page title and metadata

Open Graph URL
https://nexlares.shop/
Page title
nexlares | AI Trading Platform | Official Website
Open Graph type
website
Indexing directives
index, follow
Open Graph title
nexlares | premium AI-driven automation for trading operations
Open Graph site name
nexlares
Theme color
#0a1f0a
Description
nexlares delivers AI-driven automated trading workflows, precise execution controls, and risk-aware tooling for structured oversight and governance...
Twitter card
summary
Canonical URL
https://nexlares.shop/
Open Graph description
nexlares delivers AI-powered automated trading bot workflows, execution controls, and risk-aware tooling for structured monitoring, permissions, and governance.

Trackers

Requests
20
Observed services
  • Name
    Cloudflare
    Company
    Cloudflare
    Country
    US
    Category
    Hosting
    Requests
    7
  • Name
    Google Fonts
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    1
  • Name
    Google Static
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    2
  • 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
9
TLS
31
Waiting
26
Connection
68
Download
47
Response time, ms
181

TLS connection

ALPN
h2
Cipher
TLS_AES_128_GCM_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
47501
CO₂, grams
0.0017
Cleaner than, %
38

DNS servers

Nameservers
  • IP address
    172.64.35.117
    Host
    reese.ns.cloudflare.com
  • IP address
    108.162.194.161
    Host
    nena.ns.cloudflare.com
DNS zone
nexlares.shop

Location

IP address
185.62.58.129
ASN
62370
Organization
Snel.com B.V.
City
Schiedam
Country
NL

TLS certificate

Issuer
ZeroSSL GmbH / ZeroSSL ECC DV SSL CA 2
Subject
nexlares.shop

DNS records

A
  • 185.62.58.129
NS
  • nena.ns.cloudflare.com
  • reese.ns.cloudflare.com
SOA
Primary nameserver
nena.ns.cloudflare.com
Hostmaster
dns.cloudflare.com
Serial
2416813358
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.58.129
IP version
4

Redirects

Redirect chain
  • https://nexlares.shop

Page links

Internal links
37

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": "nexlares.shop"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2026-11-01T03:12:23Z",
    "first": "2026-10-16T02:08:37Z",
    "changes": 1,
    "days_archived": 2,
    "scans_per_day": 0.06,
    "avg_page_bytes": 12636
}
Crawler rules
{
    "agents": [
        "*"
    ],
    "present": true,
    "sitemaps": [
        "https://nexlares.shop/sitemap.xml"
    ]
}
Sitemap
{
    "present": true,
    "url_count": 140
}
Page title and metadata
{
    "ogUrl": "https://nexlares.shop/",
    "title": "nexlares | AI Trading Platform | Official Website",
    "ogType": "website",
    "robots": "index, follow",
    "ogTitle": "nexlares | premium AI-driven automation for trading operations",
    "ogSiteName": "nexlares",
    "themeColor": "#0a1f0a",
    "description": "nexlares delivers AI-driven automated trading workflows, precise execution controls, and risk-aware tooling for structured oversight and governance...",
    "twitterCard": "summary",
    "canonicalUrl": "https://nexlares.shop/",
    "ogDescription": "nexlares delivers AI-powered automated trading bot workflows, execution controls, and risk-aware tooling for structured monitoring, permissions, and governance."
}
Trackers
{
    "requests": 20,
    "trackers": [
        {
            "name": "Cloudflare",
            "company": "Cloudflare",
            "country": "US",
            "category": "Hosting",
            "requests": 7
        },
        {
            "name": "Google Fonts",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 1
        },
        {
            "name": "Google Static",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 2
        },
        {
            "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": 9,
        "tls": 31,
        "wait": 26,
        "connect": 68,
        "download": 47
    },
    "response_ms": 181
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_128_GCM_SHA256",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "ocsp_stapled": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443
    ]
}
Carbon
{
    "bytes": 47501,
    "co2_grams": 0.0017,
    "cleaner_than": 38
}
Dns server
{
    "ns": [
        {
            "ip": "172.64.35.117",
            "host": "reese.ns.cloudflare.com"
        },
        {
            "ip": "108.162.194.161",
            "host": "nena.ns.cloudflare.com"
        }
    ],
    "zone": "nexlares.shop"
}
Location
{
    "ip": "185.62.58.129",
    "asn": "62370",
    "org": "Snel.com B.V.",
    "city": "Schiedam",
    "country": "NL"
}
Ssl
{
    "issuer": "ZeroSSL GmbH / ZeroSSL ECC DV SSL CA 2",
    "subject": "nexlares.shop"
}
DNS records
{
    "A": [
        "185.62.58.129"
    ],
    "NS": [
        "nena.ns.cloudflare.com",
        "reese.ns.cloudflare.com"
    ],
    "SOA": "{\"nsname\": \"nena.ns.cloudflare.com\", \"hostmaster\": \"dns.cloudflare.com\", \"serial\": 2416813358, \"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.58.129",
    "family": 4
}
Redirects
{
    "chain": [
        "https://nexlares.shop"
    ]
}
Page links
{
    "internal_count": 37
}
HTTP headers
{
    "headers": {
        "content-type": "text/html; charset=utf-8",
        "referrer-policy": "no-referrer-when-downgrade"
    }
}
Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Security threats Malware Malware
View full Cloudflare Radar report

Questions about nexlares.shop

Is nexlares.shop legit?

PhishDestroy records the nexlares.shop account creation page, which invites visitors to register for guided AI-driven trading onboarding.

Is nexlares.shop safe to connect a wallet?

This report does not record which wallet requests nexlares.shop 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 nexlares.shop?

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

Checked, no match

Last checked

Stored Capture · 9 captures

Cloudflare Radar 1 / 9 Used in the analysis Source file SHA-256: 492ae95114d6d73b4c15a2f82ca8650a2290ad544cc21ad2685ae074d9d539e5 SHA-256 of the prepared copy given to the model: 054f1c66a0ab39b3ba2d4975b7f3a16f3e41aee0b4bfe55956e1a0fbd4c3fcf9
SourceCloudflare Radar
Recorded
StateStored capture
HTTP status200
Final URLhttps://nexlares.shop/
Position1 / 9
Open capture Source Report Wayback Download
All capture links and hashes (9)
Observed page title
nexlares | 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 29 days

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 98 report ↗
IP Reputation Netherlands185.62.58.129 abuse score 0/100 0 reports checked Nov 1, 2026
Registrar Dynadot US(US)
Abuse contact["abuse@dynadot.com"]
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for nexlares.shop →
Hosting abuse contact abuse@dynadot.com Snel.com B.V. · AS62370
RegistrationCreated Apr 12, 2026 (203d) — Expires Apr 12, 2027
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedNov 1, 2026
DOM Analysisanalyzed Nov 1, 2026score 25/1002 brand signals
Submitted URLhttp://nexlares.shop/
Favicon Hash
ICANN OVERSIGHT

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.

Accreditation is a contract, not a safety certification.

RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.

Accreditation is a contract, not a safety seal. Verify ICANN fees Read RAA §3.18 PHISHDESTROY INVESTIGATIONICANN funding, contracts, and DNS abuse oversight
Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
Netherlands185.62.58.129
Network ASN
AS62370
Organization
Snel.com B.V.
Observed location
NetherlandsSchiedam, NL

Nameservers 2

  • nena.ns.cloudflare.com
  • reese.ns.cloudflare.com

SOA

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

Location describes the IP network.

TLS certificate

Issuer
ZeroSSL GmbH / ZeroSSL ECC DV SSL CA 2
Valid from
2026-09-01 00:00:00
Valid until
2026-11-30 23:59:59
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint7395f3e51576ef442167d0c42adddcf534ec21ad88b804123a7d6b509e91249e
Certificate names · 1 SAN
  • nexlares.shop

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.62.58.129rapiddns.io

Latest Classified Outcome 2026-11-01 11:00:16 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-11-01 11:00:16 UTC
RDAP registration
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

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

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of nexlares.shop · checked Nov 1, 2026

94
Good
Performance
FCP
0.9 s
First Contentful Paint
LCP
0.9 s
Largest Contentful Paint
CLS
0.138
Cumulative Layout Shift
TBT
115 ms
Total Blocking Time
SI
1.7 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://nexlares.shop/
Final URL: https://nexlares.shop/
nexlares | AI Trading Platform | Official Website
nexlares delivers AI-driven automated trading workflows, precise execution controls, and risk-aware tooling for structured oversight and governance...
Response
HTTP 200
HTML body
46.4 KB
Compressed
11.2 KB
Links
53 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
Open Graph title: nexlares | premium AI-driven automation for trading operations
Open Graph description: nexlares delivers AI-powered automated trading bot workflows, execution controls, and risk-aware tooling for structured monitoring, permissions, and governance.
Twitter card: summary
Saved response-header values · 9
Alt-Svc
h3=":443"; ma=2592000
Content-Encoding
gzip
Content-Type
text/html; charset=utf-8
Date
Sun, 01 Nov 2026 03:15:32 GMT
Etag
"dm9jpe0amhcu10nh-gzip"
Last-Modified
Tue, 20 Oct 2026 09:07:45 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.

Archived

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-11-01 03:10 UTC.

Open this scan on URLScan 01a07ff6-0fa6-71f8-9b39-fb0133e25ddf ↗

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

    live_content

    content_served

All retained availability observations3

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-11-01 12:00:16.000000
    Evidence SHA-256
    44fd2d96914696d245e801515e4af8cca1eeb6033c3c6e80f35892c2a3329e1a
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 12:00:16
    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-01 12:00:16.000000
    Evidence SHA-256
    44fd2d96914696d245e801515e4af8cca1eeb6033c3c6e80f35892c2a3329e1a
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 12:00:16
    Evidence reason
    alive_content
  3. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    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-01 04:12:19.466817
    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
    nexlares.shop 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: 98
  • 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: 18/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 Security threats, malware
  • 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. AlienVault OTX

    1 community references

    View source
  2. Cloudflare Radar

    Phishing

    View source
  3. Wayback Machine

    Page archived

    View source
  4. Added to PhishDestroy

    nexlares.shop

    View source
  5. VirusTotal

    18/92 engine detections

    View source
  6. URLScan

    Malicious · engine verdict · score 98

    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.

nexlares.shop

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 18 det. ChainPatrol URLQuery SSL Labs Stored certificate dates valid CF Radar Malicious OTX 1 ref WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
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?

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.

Immediate steps Find reporting contacts

Official reporting routes

Chainabuse
Report a crypto wallet, transaction, or phishing URL
SEAL-ISAC
Security Alliance crypto threat intelligence
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.

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

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 nexlares.shop)
  • 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/nexlares.shop"
  title="PhishDestroy threat report for nexlares.shop"
  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>