Skip to security report
Analytics Dashboard
Domain security and threat intelligence
wallet-defender.es favicon

wallet-defender.es

In short

wallet-defender.es is a phishing page detected by PhishDestroy on 2026-10-02. Risk: critical (87/100). Status: Last known active. Hosting: Cloudflare, Inc. VirusTotal: 9/91 engines flag it. Do not enter credentials or connect a wallet.

Resolved IP
188.114.96.1
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed · HTTP probe
Risk signals
VirusTotal detections: 9/91 Scam type: Impersonation
OTX: 1 ref Oct 2, 2026 CDN
API
This domain has been flagged as malicious
Security engines reporting a detection: 9. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
9 / 91
engine detections
Google Safe Browsing
No threat flag
OTX
1
community references
Page captures
3
open gallery
Source evidenceVirusTotal 9 / 91 · OTX 1 references 5 sources

VirusTotal

9 / 91 engine detections

Open report

OTX

1 community reference

Open report

Google Safe Browsing

No threat flag

Open report

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

Analysis

Critical
VirusTotal
9 / 91
OTX
1 community ref
Page captures
3
Page captures Source results

PhishDestroy threat report

Overview

wallet-defender.es is an impersonation phishing site whose name presents it as a wallet-protection or security service. It is aimed at cryptocurrency wallet users who are worried about the safety of their funds. PhishDestroy first detected it on 2026-10-02. On 2026-10-19 the site was still online and serving live content.

How the scam works

Sites like this rely on a reassuring name. A victim who thinks their wallet is at risk is invited to "secure", "verify" or "scan" it, and the process ends with a request for a recovery phrase or private key, or a prompt to connect the wallet and sign a transaction. A seed phrase gives the operator full control of every account derived from it, while a malicious signature or token approval lets them move assets out of the wallet. The page title reads "Just a moment...", which is a generic browser-check screen rather than branded content, but our analysis classifies the site as impersonation phishing.

Evidence

On 2026-10-06, VirusTotal showed nine of 91 security engines flagging the domain. Named detections came from alphaMountain.ai, BitDefender, CRDF, Forcepoint ThreatSeeker, G-Data, Gridinsoft, LevelBlue and SOCRadar. Several independent commercial and threat-intel vendors reached a malicious verdict, though most engines had not yet caught up. The domain also appears in one AlienVault OTX pulse and is listed on the PhishDestroy blocklist.

Infrastructure

The domain resolves to 188.114.96.1 on Cloudflare's network, with the address geolocated to Canada. That means the IP points to a shared proxy edge and does not reveal the real origin server. The HTTPS certificate is a free, automatically issued Let's Encrypt (YE2) certificate, so the padlock in the browser proves nothing about who runs the site. With content still live more than two weeks after first detection, the operation remains active.

What to do

If you entered a recovery phrase or private key on this site, treat that wallet as compromised. Create a new wallet on a trusted device and move any remaining funds to it immediately. If you connected a wallet or signed anything, use a token-approval checker to revoke permissions you do not recognise, and watch for unexpected outgoing transfers. No legitimate wallet or security service ever asks for your seed phrase. Defenders should block wallet-defender.es at DNS and proxy level, add it to mail and web filters, and report it to Cloudflare's abuse channel so the origin can be traced.

Useful links

urlscan.io scan and screenshotVirusTotal reportGoogle Safe Browsing statusReport phishing to GoogleSite owner? Request a review

Collected source details

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

URLScan · 2026-09-30T20:01:29Z

Observed: · Retrieved:

Uuid
01a0f3e8-4529-7368-9a6d-37ff33cafef4
Final url
https://wallet-defender.es/ledger/
Status
403
Redirected
off-domain
Redirects
[
    {
        "to": "https://ldgr-secure-link.s3-website.eu-north-1.amazonaws.com/",
        "from": "http://ldgr-secure-link.s3-website.eu-north-1.amazonaws.com/",
        "status": 307
    },
    {
        "to": "http://ldgr-secure-link.s3-website.eu-north-1.amazonaws.com/",
        "from": "https://ldgr-secure-link.s3-website.eu-north-1.amazonaws.com/",
        "status": 307
    },
    {
        "to": "https://wallet-defender.es/ledger/",
        "from": "http://ldgr-secure-link.s3-website.eu-north-1.amazonaws.com/"
    },
    {
        "to": "https://wallet-defender.es/ledger/",
        "from": "https://wallet-defender.es/ledger/",
        "status": 307
    }
]
Ip
188.114.97.3
Contacted domains
[
    "challenges.cloudflare.com",
    "ldgr-secure-link.s3-website.eu-north-1.amazonaws.com"
]
Contacted IP addresses
[
    "104.18.95.41",
    "188.114.97.3",
    "3.5.216.71"
]
Asns
[
    "13335",
    "16509"
]
Countries
[
    "SE"
]
Linked domains
[
    "www.cloudflare.com"
]
Document hash
617282963ee9d891f8ac1a7415e1ee153eed97c8fc2c18e420ea5292e94cb56d
Script hashes
[
    "5281a0160797c5b3bd1b98b37de898f8ec6a41be568f8e086db996d6b7108a73",
    "2121e62ba5e59326f1ddfa53ee67212f97ada989f486a49234be8fe70f326894"
]
Globals
[
    "requestResize",
    "_cf_chl_opt",
    "NIEP3",
    "pNSi5",
    "cVqg7",
    "mGhI7",
    "tnAvq1",
    "WCMuS9",
    "xdiN1",
    "SMMhU4",
    "naaL6",
    "BLJTh7",
    "hfBu8",
    "QIXeq5",
    "VNlR0",
    "igejn0",
    "VMrVP1",
    "SJTZs9",
    "BGgf6",
    "SSvM5",
    "HxNX2",
    "zaERg6",
    "dANz7",
    "FqKZG4",
    "runProgram",
    "RxhA2",
    "xPLd9",
    "PQak3",
    "nJcY5",
    "UJHyt4",
    "ivIh5",
    "angular",
    "OYfX3",
    "CPve4",
    "GWews8",
    "turnstile",
    "nbvy2",
    "IusvE4",
    "PhDm6",
    "EQXLS5"
]
Cookies
[
    "cf_clearance",
    "cf_chl_rc_ni"
]
Domain age days
6
Apex age days
6
Tls age days
6
Tls valid days
89
Requests
21
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 28,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "AmazonS3",
    "content-type": "text/html"
}
Cloudflare Radar · 2026-10-02T15:30:53Z

Observed: · Retrieved:

Uuid
5418b37f-6ea0-42f2-b99f-958937ac71f8
Final url
https://wallet-defender.es/
Document hash
98ccb30d01aa327c9505a302f509690225c7498331c08a1a864dbc7f705a9289
VirusTotal · 2026-10-19T08:58:29Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 55,
    "malicious": 0,
    "suspicious": 0,
    "undetected": 37
}
Reputation
0
First seen
2026-09-24T08:45:55Z
DNS records
[
    {
        "ttl": 900,
        "type": "A",
        "value": "185.53.179.136"
    },
    {
        "ttl": 900,
        "type": "SOA",
        "rname": "noreply.registrar.eu",
        "value": "ina1.registrar.eu"
    },
    {
        "ttl": 900,
        "type": "NS",
        "value": "ina1.registrar.eu"
    },
    {
        "ttl": 900,
        "type": "NS",
        "value": "ina2.registrar.eu"
    },
    {
        "ttl": 900,
        "type": "NS",
        "value": "ina3.registrar.eu"
    }
]
Dns at
2026-10-19T09:00:51Z
Jarm
27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c
Certificate
{
    "san": [
        "*.wallet-defender.es",
        "wallet-defender.es"
    ],
    "issuer": "Let's Encrypt / YE2",
    "serial": "50744a08c8e7e3e97a1b2f4368aa8aaaa22",
    "sha256": "12eb53ec8d4d92db2544c78e301a53df354958321b1082062ee80d32c83aeda6",
    "subject": "wallet-defender.es",
    "valid_to": "2026-12-23T07:14:15Z",
    "valid_from": "2026-09-24T07:14:16Z"
}

Questions about wallet-defender.es

Is wallet-defender.es legit?

No. PhishDestroy classifies wallet-defender.es as a phishing page (risk: critical, 87/100); it was first detected on 2026-10-02. VirusTotal: 9/91 engines flag it. Treat the site as unsafe.

Is wallet-defender.es safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on wallet-defender.es. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.

What should I do if I used wallet-defender.es?

Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.

Explore

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Stored Capture · 3 captures

Primary capture 1 / 3
SourcePrimary capture
Recorded2026-10-02 15:27 UTC
StateStored capture
Position1 / 3
Open capture Wayback Download

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags blocklistcryptodrainerfraudphishdestroyphishingscam
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 2, 2026
DOM Analysisanalyzed Oct 9, 2026score 83/100
Submitted URLhttps://wallet-defender.es/
Favicon Hash
TLS Certificate
Issued by Let's Encrypt / YE2 · stored validity ends in 61 days

Network & certificates

Stored technical evidence

Network & DNS

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

Edge-IP reputation is not attributed to this domain.

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE2
Valid from
2026-09-24 07:14:16
Valid until
2026-12-23 07:14:15
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection time
2026-10-21 07:02:37 UTC
Collection source
PhishDestroy collector
Certificate fingerprint12eb53ec8d4d92db2544c78e301a53df354958321b1082062ee80d32c83aeda6
Certificate names · 2 SANs
  • *.wallet-defender.es
  • wallet-defender.es

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

viewdns.info · 188.114.96.1rapiddns.io

Latest Classified Outcome 2026-10-22 10:00:52 UTC

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-10-22 10:00:52 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-22 10:00:52 UTC last content: 2026-10-22 10:00:52 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.
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

9 / 91 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 2 detections
alphaMountain.ai
BitDefender
CRDF
Forcepoint ThreatSeeker
G-Data
Gridinsoft
LevelBlue
SOCRadar
Webroot
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of wallet-defender.es · checked Oct 2, 2026

76
Needs Work
Performance
FCP
0.78s
First Contentful Paint
LCP
1.29s
Largest Contentful Paint
CLS
0.024
Cumulative Layout Shift
TBT
1186ms
Total Blocking Time
SI
1.69s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
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.

Stored observation history18

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  2. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  3. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  4. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  5. Availability monitor · Recorded state

    Unknown→live_content

    content_served

Earlier observations 13
  1. Availability monitor · Recorded state

    Unavailable→Reachable

  2. Availability monitor · Recorded state

    Unknown→blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  3. Availability monitor · Recorded state

    Unknown→blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  4. Availability monitor · Recorded state

    Unknown→blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  5. Availability monitor · Recorded state

    Unknown→blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  6. Availability monitor · Recorded state

    Reachable→Unavailable

  7. Availability monitor · Recorded state

    Unknown→protected

    cloudflare_challenge · Cloudflare · challenge

  8. Availability monitor · Recorded state

    Unknown→protected

    cloudflare_challenge · Cloudflare · challenge

  9. Availability monitor · Recorded state

    Unknown→protected

    cloudflare_challenge · Cloudflare · challenge

  10. Availability monitor · Recorded state

    Unknown→protected

    cloudflare_challenge · Cloudflare · challenge

  11. Availability monitor · Recorded state

    Unknown→protected

    cloudflare_challenge · Cloudflare · challenge

  12. Availability monitor · Recorded state

    Unknown→protected

    cloudflare_challenge · Cloudflare · challenge

  13. Availability monitor · Recorded state

    Unknown→protected

    cloudflare_challenge · Cloudflare · challenge

Recorded activity

4 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    9/91 engine detections

    View source
  3. AlienVault OTX

    1 community references

    View source
  4. Added to PhishDestroy

    wallet-defender.es

    View source

Check for cloaking

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

wallet-defender.es

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 9 det. ChainPatrol URLQuery SSL Labs Stored certificate dates valid CF Radar Open report 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 0 stored notification records Last known active

Listed domains receive at least one abuse report; this entry has no retained notification history.

If credentials were compromised, report immediately. Do not engage with recovery scammers.

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

Immediate steps Find reporting contacts

Official reporting routes

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →

Report to Your Local Authorities

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

97-country directory

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

Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

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

What should I do immediately?

Urgent

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

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

What information should I collect for my report?

FBI guidelines

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

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

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

Where should I report the scam?

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

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

How do phishing scams typically work?

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

How can I protect myself in the future?

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

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

Check Any Domain

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

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

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

Live Threat Feed Appeal This Listing
About this reportSources, observation dates and corrections

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

The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.

A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.

Request a correction or appeal How PhishDestroy works
Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html 
<iframe
  src="https://phishdestroy.io/embed/domain/wallet-defender.es"
  title="PhishDestroy threat report for wallet-defender.es"
  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>