Skip to security report
Domain security and threat intelligence
en-leger.org favicon

en-leger.org

“en-leger.org | 522: Connection timed out”

Registrar
Key-Systems
Resolved IP
188.114.97.1
Registered
Oct 14, 2026
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed · HTTP probe
VirusTotal detections: 5/92 Spamhaus DBL: DBL_PHISH Stored blocklist matches: 2 Automated brand label: Ledger Young domain: 5 days old
OTX: 2 refs Oct 19, 2026 CDN
API
This domain has been flagged as malicious
Security engines reporting a detection: 5. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
engine detections
Google Safe Browsing
OTX
community references
Page captures
open gallery
Domain age
Source evidenceVirusTotal 5 / 92 · OTX 2 references 6 sources

VirusTotal

5 / 92 engine detections

Open report

Spamhaus DBL

DBL_PHISH

OTX

2 community references

Open report

Google Safe Browsing

No threat flag

Open report

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

Analysis

Critical
VirusTotal
5 / 92
OTX
2 community refs
Page captures
1

PhishDestroy threat report

Overview

en-leger.org is a newly registered domain that shows no clear legitimate branding and has been placed on PhishDestroy’s blocklist. The site appears to be aimed at cryptocurrency users, particularly those who connect web wallets. PhishDestroy first observed the domain on 2026-10-19 and its operational status was listed as unknown on that date.

How the scam works

The page likely lures visitors into linking a crypto wallet or entering private keys, after which malicious code can initiate unauthorized transfers. By capturing wallet credentials or approval signatures, attackers can move any assets held in the compromised wallet. Victims therefore risk total loss of their cryptocurrency holdings.

Evidence

VirusTotal scanned the domain on 2026-10-19 and five of its 92 engines flagged it as malicious, including detections from alphaMountain.ai, CRDF, Fortinet, Gridinsoft and SOCRadar. The domain also appears in two OTX pulses and is listed on the PhishDestroy, MetaMask and SEAL blocklists. These independent detections collectively support the classification as a suspicious crypto‑related site.

Infrastructure

The domain was registered on 2026-10-14 through Key-Systems GmbH, giving it only five days of existence before PhishDestroy’s first sighting. Hosting is provided from the IP address 188.114.97.1, indicating a single‑point infrastructure. The short registration window and use of a reputable registrar suggest a fast‑flux operation typical of opportunistic attackers.

What to do

If you visited en-leger.org, entered any wallet credentials, or approved transactions, immediately revoke all approvals in your wallet and change any associated passwords. Monitor your blockchain addresses for unauthorized activity and consider moving funds to a new, secure wallet. Report the incident to your wallet provider and to PhishDestroy so the domain can be further mitigated. Security teams should add the domain to internal blocklists, monitor DNS queries for the IP address, and watch for similar registrations from the same registrar.

Blocklist matchesMetaMask · PhishDestroy · SEAL 3
MetaMask Listed View source
PhishDestroy PhishDestroy list View source
SEAL Listed View source

Last checked

Stored Capture · 1 capture

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 brand-ledgercredential-theftphishingscam
Registrar Key-Systems DE(DE)
RegistrationCreated Oct 14, 2026 (5d · Brand New!) — Expires Oct 14, 2027
HTTP Status301 Moved Permanently
Technical detailsProvenance & timestamps
First DetectedOct 19, 2026
DOM Analysisanalyzed Oct 20, 2026score 100/100
Submitted URLhttps://en-leger.org/
Observed page title
en-leger.org | 522: Connection timed out
TLS Certificate
Issued by Let's Encrypt / YE2 · stored validity ends in 84 days

Network & certificates

Stored technical evidence

Network & DNS

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

Edge-IP reputation is not attributed to this domain.

Nameservers 1

  • raina.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE2
Valid from
2026-10-14 19:42:44
Valid until
2027-01-12 19:42:43
Validity
Within stored validity dates
Collection time
2026-10-19 22:02:04 UTC
Collection source
PhishDestroy collector
Certificate fingerprint8be05aa2516b24bcec6a67eb3071573ea63dde4dc04993d14a4b85900176c375

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-10-20 10:00:48 UTC

Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Redirecting Content: Unknown DNS: Resolved Registration: Unknown
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-10-20 10:00:48 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-20 10:00:48 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

5 / 92 security vendors flagged this domain
View on VT
Last analyzed
alphaMountain.ai
CRDF
Fortinet
Gridinsoft
SOCRadar
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 522
Requested URL: https://en-leger.org/
en-leger.org | 522: Connection timed out
Response
HTTP 522
HTML body
7.1 KB
Compressed
2.1 KB
Links
4 internal · 1 external
Detected technologies
cloudflare
Selected response headers
Content-Type: text/html; charset=UTF-8
Cache-Control: private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Server: cloudflare
Security headers present
X-Frame-OptionsReferrer-Policy
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Saved response-header values · 13
alt-svc
h3=":443"; ma=86400
Cache-Control
private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0
CF-RAY
a4d0d5fd8f7b151b-EWR
Connection
keep-alive
Content-Length
7224
Content-Type
text/html; charset=UTF-8
Date
Mon, 19 Oct 2026 15:32:50 GMT
Expires
Thu, 01 Jan 1970 00:00:01 GMT
Referrer-Policy
same-origin
Retry-After
120
Server
cloudflare
Server-Timing
cfEdge;dur=19478,cfOrigin;dur=0
X-Frame-Options
SAMEORIGIN

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

Registration & observation details2

Availability observations

Last reachable 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.

Check for cloaking

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

Page titles differ

redirect: raw=redirect_301; http=301; via=http_proxy; location=https://en-leger.org/; server=cloudflare

Browser
en-leger.org | 522: Connection timed out
Crawler
301 Moved Permanently
en-leger.org
Stored observation history1

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

  1. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

Recorded activity

4 entries
  1. AlienVault OTX

    2 community references

    View source
  2. Google Safe Browsing

    No threat flag

    View source
  3. VirusTotal

    5/92 engine detections

    View source
  4. Added to PhishDestroy

    en-leger.org

    View source

Lookalike domains

151 stored lookalike domains

Show all (88)
eldger.com transposition kedger.com replacement kledger.com insertion l3dger.com replacement ldeger.com transposition ldger.com omission le.dger.com subdomain lecger.com replacement ledber.com replacement ledegr.com transposition leder.com omission ledg3r.com replacement ledge.com omission ledged.com replacement ledgedr.com insertion ledgee.com replacement ledgeer.com repetition ledgercom.com various ledget.com replacement ledgewr.com insertion ledgger.com repetition ledgir.com vowel-swap ledgor.com vowel-swap ledgr.com omission ledgre.com transposition ledgrer.com insertion ledgsr.com replacement ledgwer.com insertion ledgwr.com replacement ledher.com replacement ledhger.com insertion ledsger.com insertion ledtger.com insertion ledyer.com replacement ledzer.com replacement leedger.com insertion legder.com transposition leger.com omission lerdger.com insertion lerger.com replacement lesger.com replacement lewdger.com insertion lidger.com vowel-swap lledger.com repetition lodger.com vowel-swap lrdger.com replacement lsdger.com replacement oedger.com replacement pedger.com replacement pledger.com insertion dedger.com bitsquatting hedger.com bitsquatting iedger.com homoglyph l-edger.com hyphenation ladger.com bitsquatting lcdlger.com homoglyph lddger.com bitsquatting lebger.com homoglyph leclger.com homoglyph ledcer.com bitsquatting leddger.com insertion ledeer.com bitsquatting ledeger.com insertion ledfer.com bitsquatting ledg-er.com hyphenation ledgar.com bitsquatting ledger0.com addition ledger1.com addition ledger4.com addition ledger5.com addition ledger6.com addition ledgerb.com addition ledgerc.com addition ledgerf.com addition ledgeri.com addition ledgern.com addition ledgerq.com addition ledgerx.com addition ledges.com bitsquatting ledgez.com bitsquatting ledgur.com bitsquatting lediger.com homoglyph ledqer.com homoglyph leeger.com bitsquatting leelger.com homoglyph lefger.com bitsquatting letger.com bitsquatting ludger.com bitsquatting

Showing 100 of 151

Community intelligence

3 community reports

CategoryPHISHING

Dear Team, We are writing to report a phishing website operating at en-leger[.]org. On 16 October 2026 a Bing search for site:en-leger[.]org returned four indexed pages, and every one of them is published under the Ledger name: "Ledger — Hardware wallet for crypto security™", "L

Evidence & External Reports

Community Scam Report — ChainAbuse
3 reports filed for en-leger.org (1 written by a person) · category: Phishing · source checked
“Dear Team, We are writing to report a phishing website operating at en-leger[.]org. On 16 October 2026 a Bing search for site:en-leger[.]org returned four indexed pages, and every one of them is published under the Ledger name: "Ledger — Hardware wallet for crypto security™", "Ledger Wallet Desktop — Manage crypto from your computer™", "Ledger Wallet — App for crypto management™" and "Ledger Extension — One-click Web3 toolbar". The verdict on this domain has already been reached, and not by us”
— reported by Anonymous on Oct 16, 2026 · Source: ChainAbuse (TRM Labs) — full report and evidence there.
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.

Official reporting routes

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 en-leger.org)
  • Communications — emails, texts, phone numbers, usernames the scammer used

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

Where should I report the scam?

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

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

How do phishing scams typically work?

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

How can I protect myself in the future?

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

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

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.

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/en-leger.org"
  title="PhishDestroy threat report for en-leger.org"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>