Skip to security report
firmo-ledger.com favicon
Domain security and threat intelligence

firmo-ledger.com

I was scammed — help me write a report
Share / download report
Post on X Send in Telegram Check via API
In short

PhishDestroy first recorded firmo-ledger.com on 2026-10-26. Stored VirusTotal result: 2/92 engines flagged. Analysis time (as stored): 2026-10-26 12:28 UTC. Retrieved (as stored): 2026-10-26 18:13 UTC. Listed by external blocklists: MetaMask, SEAL.

Page title: “firmo-ledger.com”

More about the sources
Recorded security signals

Stored VirusTotal result: 2/92 engines flagged. Analysis time (as stored): 2026-10-26 12:28 UTC. Retrieved (as stored): 2026-10-26 18:13 UTC. Listed by external blocklists: MetaMask, SEAL. Use caution — do not enter credentials or personal information.

VirusTotal detections: 2/92 Stored blocklist matches: 2
Registrar
FranceOVH, SAS
Resolved IP
France213.186.33.5OVH SAS
Registered
2026-10-23
First seen by PhishDestroy
2026-10-26
OTX
community references
Page captures
open gallery
Domain age
registered 2026-10-23 according to WHOIS
Reports sent
view timeline
OTX: 4 refs 2026-10-26 1 Report Sent

Risk score, higher = worse · How this score works

What to do right now

Pick what happened and tick the steps as you go. The ticks are kept only in this browser.

Shared a seed phrase or private key0/3
Approved token spending (approve / permit)0/3
Connected a wallet but signed nothing0/2
Sent crypto0/3
Entered a password0/3
Paid or entered card or bank details0/2
Downloaded a file0/2
Write a police report

Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.

ABUSE NOTICE · 7D+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence

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

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

Elapsed since first report
27 days
Reports sent
1
Latest case ID
PD-20261026-4F33B7
Current status
HTTP 302 at latest stored check

Analysis

Domain summary

PhishDestroy first recorded firmo-ledger.com on 2026-10-26. Stored VirusTotal result: 2/92 engines flagged. Analysis time (as stored): 2026-10-26 12:28 UTC. Retrieved (as stored): 2026-10-26 18:13 UTC. Listed by external blocklists: MetaMask, SEAL. Risk: critical (evidence score 98/100). Registrar: OVH, SAS. Status: Last known active. Hosting: OVH SAS. PhishDestroy sent 1 abuse report. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
2 / 92
Blocklist matches
2 external + PhishDestroy list
Scam type (automated label)
Impersonation
Hosting
France213.186.33.5OVH SAS
Registrar
FranceOVH, SAS
Registered
2026-10-23
OTX
4 community refs
Page captures
4

PhishDestroy analysis, earlier unreviewed version

Overview

The captured screenshot observed on 2026-10-26 shows a browser error page reading This site can't be reached with the message The connection was reset and the code ERR_CONNECTION_RESET, alongside Details and Reload buttons. PhishDestroy listed the domain after its automated assessment classified it as an impersonation phishing page referencing Ledger, first seen by PhishDestroy on 2026-10-26.

How the scam works

No login or recovery form appeared in this capture, so no data entry was observed there. Pages in this category work by impersonation: a lookalike domain built to win a visitor's trust while the target is persuaded to hand over account credentials or recovery secrets. Because the domain was registered on 2026-10-23 and first seen three days later, the risk is a short-lived campaign page serving that lure.

Evidence

The screenshot itself shows only the connection-reset error page, with no visible form, offer or brand artwork captured on 2026-10-26. urlscan rated the capture as malicious at a machine-learning score of 93 on 2026-10-26 across 11 requests, and Cloudflare Radar tagged the domain with New Domains, Newly Seen Domains and Security Risks that same day. VirusTotal flagged the domain as malicious, with SOCRadar and Forcepoint ThreatSeeker labelling it phishing. Google Safe Browsing did not flag it and Spamhaus carried no listing, while MetaMask and SEAL blocklists plus the PhishDestroy internal blocklist recorded it and OTX recorded 4 pulses, all checked on 2026-10-26; a redirect funnel bounced between HTTP and HTTPS and a www variant using 307 and 302 responses before the final capture.

Infrastructure

Weak email authentication is the main posture gap: an SPF record is present but no DKIM or DMARC record was recorded, while a CAA record exists and DNSSEC is signed with DS, RRSIG and DNSKEY all set. The domain was registered through OVH, SAS on 2026-10-23, hosting recorded at OVH SAS, served by an openresty web server with ports 25 and 80 observed open and no CDN firewall identified in the capture.

What to do

A visitor who submitted credentials or recovery details through firmo-ledger.com should change the password on the genuine Ledger service and enable two-factor authentication, and should treat any follow-up messages as untrusted. Defenders should block firmo-ledger.com at proxy, DNS and endpoint controls, hunt for sibling lookalike registrations, and pivot on the recorded capture document hash for related pages.

Source evidenceVirusTotal 2 / 92 · OTX 4 references 6 sources

VirusTotal

2 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 13 fields
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
Result state
observed
Numerator
8
Denominator
92
Vendors
alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Fortinet, Gridinsoft, Kaspersky, SOCRadar, VIPRE
Checked at
2026-10-30 04:02:26
Fetched at
2026-10-30 03:02:27

OTX

4 community references

Open report

URLScan

Page capture

SHA-256 78a0cc8d…2dc381f

Open report
URLScanOriginal source recordObserved: 18 fields
Separate monitor record · 2026-10-27 04:31 UTC

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

UUID
01a1780f-9132-76ba-a41c-51fc35f7d881
Score
0
Malicious
✗
Result at
2026-10-27T04:31:12Z
Enriched at
2026-10-27T09:21:48Z
Source timestamps
Urlscan result at: 2026-10-27 05:31:12; Urlscan enriched at: 2026-10-27 10:21:48

PhishDestroy DOM

98 / 100 · heuristic score · 0 brand references · 1 classification

Content heuristic only; not the final score

Open report
Page code check by a separate monitor · 0 / 100 · 2026-10-26 15:20 UTC

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

Heuristic score
0
Analyzed at
2026-10-26T15:20:10Z
Source timestamp
2026-10-26 16:20:10
Technical metadata

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
firmo-ledger.com — Ledger impersonation phishing page
AI description
PhishDestroy assesses firmo-ledger.com as an impersonation phishing page targeting Ledger users based on technical signals.
AI summary
Overview The captured screenshot observed on 2026-10-26 shows a browser error page reading This site can't be reached with the message The connection was reset and the code ERR_CONNECTION_RESET, alongside Details and Reload buttons. PhishDestroy listed the domain after its automated assessment classified it as an impersonation phishing page referencing Ledger, first seen by PhishDestroy on 2026-10-26. How the scam works No login or recovery form appeared in this capture, so no data entry was observed there. Pages in this category work by impersonation: a lookalike domain built to win a visitor's trust while the target is persuaded to hand over account credentials or recovery secrets. Because the domain was registered on 2026-10-23 and first seen three days later, the risk is a short-lived campaign page serving that lure. Evidence The screenshot itself shows only the connection-reset error page, with no visible form, offer or brand artwork captured on 2026-10-26. urlscan rated the capture as malicious at a machine-learning score of 93 on 2026-10-26 across 11 requests, and Cloudflare Radar tagged the domain with New Domains, Newly Seen Domains and Security Risks that same day. VirusTotal flagged the domain as malicious, with SOCRadar and Forcepoint ThreatSeeker labelling it phishing. Google Safe Browsing did not flag it and Spamhaus carried no listing, while MetaMask and SEAL blocklists plus the PhishDestroy internal blocklist recorded it and OTX recorded 4 pulses, all checked on 2026-10-26; a redirect funnel bounced between HTTP and HTTPS and a www variant using 307 and 302 responses before the final capture. Infrastructure Weak email authentication is the main posture gap: an SPF record is present but no DKIM or DMARC record was recorded, while a CAA record exists and DNSSEC is signed with DS, RRSIG and DNSKEY all set. The domain was registered through OVH, SAS on 2026-10-23, hosting recorded at OVH SAS, served by an openresty web server with ports 25 and 80 observed open and no CDN firewall identified in the capture. What to do A visitor who submitted credentials or recovery details through firmo-ledger.com should change the password on the genuine Ledger service and enable two-factor authentication, and should treat any follow-up messages as untrusted. Defenders should block firmo-ledger.com at proxy, DNS and endpoint controls, hunt for sibling lookalike registrations, and pivot on the recorded capture document hash for related pages. Useful links urlscan.io scan and screenshot: https://urlscan.io/result/01a1780f-9132-76ba-a41c-51fc35f7d881/ Cloudflare Radar report: https://radar.cloudflare.com/scan/d0893f64-ccee-4fd1-8c6f-4ab6de67c160 URLQuery report: https://urlquery.net/report/fbeabf5e-f1b8-4316-a0c8-44a0dd5f235b Stored capture screenshot: https://i.ibb.co/XBT4vgK/20a098946c71.png Cloudflare Radar screenshot (2026-10-26T11:56:18Z): https://screenshots.phishdestroy.io/cf/d0893f64-ccee-4fd1-8c6f-4ab6de67c160.png URLQuery screenshot: https://screenshots.phishdestroy.io/uq/fbeabf5e-f1b8-4316-a0c8-44a0dd5f235b.png VirusTotal report: https://www.virustotal.com/gui/domain/firmo-ledger.com Google Safe Browsing status: https://transparencyreport.google.com/safe-browsing/search?url=firmo-ledger.com Report phishing to Google: https://safebrowsing.google.com/safebrowsing/report_phish/ Site owner? Request a review: https://phishdestroy.io/appeals/
AI generated by
mimo-flash
AI generated at
2026-10-26T20:16:49Z
Revision
616181c5ce00cfea4e9c48f22a36331c1450bfefb029577dda4262874dcd1c48
Mode
stored
Interpretation
Earlier stored analysis, not reviewed; 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: 10 fields

Mail configuration

MX records
  • mx1.mail.ovh.net
  • mx2.mail.ovh.net
  • mx3.mail.ovh.net
SPF record
v=spf1 include:mx.ovh.com -all
SPF lookups
3

CAA records

Domain
firmo-ledger.com

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Ports

Open ports
  • 25
  • 80

DNS servers

Nameservers
  • IP address
    5.196.39.89
    Host
    dns103.ovh.net
  • IP address
    5.135.54.65
    Host
    ns103.ovh.net
DNS zone
firmo-ledger.com

Location

IP address
213.186.33.5
ASN
16276
Organization
OVH SAS
City
Roubaix
Country
FR

DNS records

A
  • 213.186.33.5
MX
  • Mail server
    mx2.mail.ovh.net
    Priority
    5
  • Mail server
    mx1.mail.ovh.net
    Priority
    1
  • Mail server
    mx3.mail.ovh.net
    Priority
    100
NS
  • ns103.ovh.net
  • dns103.ovh.net
SOA
Primary nameserver
dns103.ovh.net
Hostmaster
tech.ovh.net
Serial
2092769954
Refresh, seconds
86400
Retry, seconds
3600
Expiry, seconds
3600000
Minimum TTL, seconds
60
TXT
  • v=spf1 include:mx.ovh.com -all
  • 1|www.firmo-ledger.com

DNSSEC

DS record
Yes
RRSIG
Yes
DNSKEY
Yes

IP lookup

IP address
213.186.33.5
IP version
4

Registration record

Registrar
OVH sas
Registered
Updated
Expires
Status
  • clientDeleteProhibited https://icann.org/epp
  • clientTransferProhibited https://icann.org/epp
Nameservers
  • dns103.ovh.net
  • ns103.ovh.net
Original source fields · JSON
Mail configuration
MX: mx1.mail.ovh.net, mx2.mail.ovh.net, mx3.mail.ovh.net; Spf: v=spf1 include:mx.ovh.com -all; Spf lookups: 3
Caa records
Domain: firmo-ledger.com
Protective DNS results
Resolvers: 12; Blocked count: 0
Ports
Open: 25, 80
DNS server
NS: (IP: 5.196.39.89; Host: dns103.ovh.net), (IP: 5.135.54.65; Host: ns103.ovh.net); Zone: firmo-ledger.com
Location
IP: 213.186.33.5; ASN: 16276; Org: OVH SAS; City: Roubaix; Country: FR
DNS records
A: 213.186.33.5; MX: Exchange: mx2.mail.ovh.net; Priority: 5, Exchange: mx1.mail.ovh.net; Priority: 1, Exchange: mx3.mail.ovh.net; Priority: 100; NS: ns103.ovh.net, dns103.ovh.net; Soa: Nsname: dns103.ovh.net; Hostmaster: tech.ovh.net; Serial: 2092769954; Refresh: 86400; Retry: 3600; Expire: 3600000; Minttl: 60; Txt: v=spf1 include:mx.ovh.com -all, 1|www.firmo-ledger.com
Dnssec
Ds: ✓; Rrsig: ✓; Dnskey: ✓
Get IP
IP: 213.186.33.5; Family: 4
Registration record
Registrar: OVH sas; Created: 2026-10-23T15:38:23Z; Updated: 2026-10-23T15:41:06Z; Expires: 2027-10-23T15:38:23Z; Status: clientDeleteProhibited https://icann.org/epp, clientTransferProhibited https://icann.org/epp; Nameservers: dns103.ovh.net, ns103.ovh.net

Questions about firmo-ledger.com

Is firmo-ledger.com legit?

PhishDestroy rates firmo-ledger.com as critical risk (evidence score 98/100) from the recorded evidence; it was first recorded on 2026-10-26. Stored VirusTotal result: 2/92 engines flagged. Analysis time (as stored): 2026-10-26 12:28 UTC. Retrieved (as stored): 2026-10-26 18:13 UTC. Listed by external blocklists: MetaMask, SEAL. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is firmo-ledger.com safe to connect a wallet?

Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions on firmo-ledger.com. A confirmed blockchain transaction cannot be reversed.

What should I do if I used firmo-ledger.com?

  • 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
  • Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
  • Approved token spending (approve / permit) — revoke that approval with a token-approval checker
  • Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
  • 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 matches2 external + PhishDestroy list · MetaMask · PhishDestroy · SEAL 2
MetaMask Listed View source
PhishDestroy PhishDestroy list View source
SEAL Listed View source

Last checked

Page captures (4)

All capture links and hashes (4)
firmo-ledger.com: Ledger impersonation — Blocked by MetaMask, flagged by SEAL, 8/92 VirusTotal engines. PhishDestroy risk score 98/100 (critical).
Social preview card firmo-ledger.com: Ledger impersonation — Blocked by MetaMask, flagged by SEAL, 8/92 VirusTotal engines. PhishDestroy risk score 98/100 (critical). v 58cecd8c3700

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 93 report ↗
IP Reputation France213.186.33.5 18/100abuse score · abuse reports about this server's IP address, not about the domain; higher = worse This IP address has a low abuse score, but the domain itself is recognized as phishing. 5 reports DDoS AttackEmail SpamPort Scan checked 2026-10-26 last reported
OTX tags 2026-10activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar OVH, SAS FR(FR)
Abuse contactabuse@ovh.net
Hosting abuse contact abuse@ovh.net OVH SAS · AS16276
RegistrationCreated 2026-10-23 (30d · New) — Expires 2027-10-23
Registrant countryFrance VirusTotal WHOIS
Registrant1f8f4166599d23ee0809924504b3d45cs@ VirusTotal WHOIS
HTTP Status302 Found (Temporary)
Technical detailsProvenance & timestamps
First Detected2026-10-26
DOM Analysisanalyzed 2026-10-26score 98/100
Submitted URLhttp://firmo-ledger.com/
Favicon Hash
Case ID
Observed page title
firmo-ledger.com

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
France213.186.33.5
Network ASN
AS16276
AS name
OVH OVH SAS, FR
Organization
OVH SAS
Observed location
FranceRoubaix, FR
Server header
openresty

Nameservers 2

  • dns103.ovh.net
  • ns103.ovh.net

SOA

  • nsname: dns103.ovh.net
  • hostmaster: tech.ovh.net
  • serial: 2092769954
  • refresh: 86400
  • retry: 3600
  • expire: 3600000
  • minttl: 60

Registrar abuse contact VirusTotal WHOIS

Mail routing 3 MX records

  • mx2.mail.ovh.netpriority 5
  • mx1.mail.ovh.netpriority 1
  • mx3.mail.ovh.netpriority 100

Location describes the IP network.

Latest Classified Outcome 2026-11-22 11:15 UTC

The site was redirecting visitors elsewhere at the latest check.

Technical details
Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Redirecting DNS: Resolved
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-11-22 11:15 UTC
RDAP registration
Observed timeline last reachable: 2026-11-22 11:15 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.

VirusTotal Analysis

2 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive result retrieved by PhishDestroy Previous stored snapshot: 2 detections
SOCRadar
Forcepoint ThreatSeeker
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://firmo-ledger.com/
Final URL: http://www.firmo-ledger.com/
Site en construction
Response
HTTP 200
HTML body
18.0 KB
Compressed
3.1 KB
Links
0 internal · 6 external
Selected response headers
Server: openresty
Content-Type: text/html; charset=utf8
Cache-Control: no-store, no-cache, must-revalidate
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Favicon fingerprint: 73366da0141f74ddd220ea53c03c7be935b9794d3befe7b360e0e8fe5de0987a
Saved response-header values · 8
Cache-Control
no-store, no-cache, must-revalidate
Content-Length
18397
Content-Type
text/html; charset=utf8
Date
Mon, 26 Oct 2026 11:56:37 GMT
Pragma
no-cache
Server
openresty
x-iplb-instance
52345
x-iplb-request-id
C33F1476:FD61_D5BA2105:0050_6ADF3FF5_72C6849:3B0774

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.

All stored data106
Open complete records

Captured network requests

Network requests: 11 SHA-256 hashes: 11 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-29 01:56 UTC.

Open this scan on URLScan 01a1780f-9132-76ba-a41c-51fc35f7d881 ↗

Check for cloaking

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

Page titles differ

Our scanner could not complete this check.

Browser
firmo-ledger.com
Crawler
302 Found
firmo-ledger.com
Stored observation history19
Open complete records
All retained availability observations112
Open complete records

Threat Response Pipeline

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

Recorded events: 13. 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
  • Threat Ingested
    firmo-ledger.com detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · Blocklist Detection · OTX Community References · Automated brand label: Ledger · Forensic Evidence Collected · Technical Analysis Recorded · VirusTotal detections +2 recorded
Notification RecordsSent Report Recorded recorded
  • Sent Report Recorded
    Stored record of an abuse report about this domain; registrar at the time: OVH, SAS. Abuse contacts: 1.
    • abuse@ovh.net
Publication & AvailabilityDestroyList Published · Monitoring Continues ongoing
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.
    ongoing

Recorded activity

5 entries

Lifecycle

  1. Domain registered
  2. Added to PhishDestroy+68 h 17 min
  3. First abuse report sent+6 min
  4. VirusTotal analysis with detections+26 min

Reported 68 h 23 min after registration

  1. AlienVault OTX

    4 community references

    +5 h 46 min
  2. VirusTotal

    2/92 engine detections

    +26 min
  3. Abuse report sent

    PD-20261026-4F33B7 · Receipt 83433

    abuse@ovh.net
    +6 min
  4. Added to PhishDestroy

    firmo-ledger.com

    same minute
  5. URLScan

    Page captured

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

Lookalike domains

151 stored lookalike domains

Names that imitate the brand, found by dnstwist. A similar name alone does not prove the same owner.

ledfger.com Inserted character Variant of ledger.com Internal report A 185.244.151.84MX ledfger.comNS ns3.ro.hostsailor.com ledgfer.com Inserted character Variant of ledger.com Internal report A 185.244.151.84MX ledgfer.comNS ns3.ro.hostsailor.com ledgher.com Inserted character Variant of ledger.com Internal report A 185.244.151.84MX ledgher.comNS ns3.ro.hostsailor.com ledgrr.com Replaced character Variant of ledger.com Internal report A 185.244.151.84MX ledgrr.comNS ns3.ro.hostsailor.com lefdger.com Inserted character Variant of ledger.com Internal report A 185.244.151.84MX lefdger.comNS ns3.ro.hostsailor.com lesdger.com Inserted character Variant of ledger.com Internal report A 185.244.151.84MX lesdger.comNS ns3.ro.hostsailor.com lkedger.com Inserted character Variant of ledger.com Internal report A 185.244.151.84MX lkedger.comNS ns3.ro.hostsailor.com lredger.com Inserted character Variant of ledger.com Internal report A 185.244.151.84MX lredger.comNS ns3.ro.hostsailor.com lwedger.com Inserted character Variant of ledger.com Internal report A 185.244.151.84MX lwedger.comNS ns3.ro.hostsailor.com xn--ledgr-9za.com Lookalike letters Variant of ledger.com Internal report NS ns-cloud-d1.googledomains.com ledgerk.com Added character Variant of ledger.com Internal report A 156.250.67.229NS ns1.bdydns.cn edger.com Missing character Variant of ledger.com A 54.215.31.113NS ns1.dyna-ns.net

Showing 12 of 151

Show 88 more
eldger.com Swapped characters Variant of ledger.com A 185.244.151.84MX eldger.comNS ns3.ro.hostsailor.com kedger.com Replaced character Variant of ledger.com A 13.56.33.8NS ns1.brandbucket.com kledger.com Inserted character Variant of ledger.com A 20.65.18.151NS ns-1490.awsdns-58.org l3dger.com Replaced character Variant of ledger.com A 216.198.79.1MX inbound-smtp.eu-west-1.amazonaws.comNS ns1.bluehost.com ldeger.com Swapped characters Variant of ledger.com A 185.244.151.84MX ldeger.comNS ns3.ro.hostsailor.com ldger.com Missing character Variant of ledger.com A 13.248.169.48NS ns1.dan.com le.dger.com Split into subdomain Variant of ledger.com A 13.248.169.48NS ns5.afternic.com lecger.com Replaced character Variant of ledger.com A 14.63.215.245NS ns1.hostname.net ledber.com Replaced character Variant of ledger.com A 104.21.35.54NS chin.ns.cloudflare.com ledegr.com Swapped characters Variant of ledger.com A 185.244.151.84MX ledegr.comNS ns3.ro.hostsailor.com leder.com Missing character Variant of ledger.com A 85.13.132.113MX w01a4668.kasserver.comNS ns5.kasserver.com ledg3r.com Replaced character Variant of ledger.com NS ns1.dreamhost.com ledge.com Missing character Variant of ledger.com A 54.215.31.113NS ns1.dyna-ns.net ledged.com Replaced character Variant of ledger.com A 52.20.84.62NS ns1.atom.com ledgedr.com Inserted character Variant of ledger.com A 31.43.160.6NS ns6.wixdns.net ledgee.com Replaced character Variant of ledger.com A 13.248.169.48NS ns3.afternic.com ledgeer.com Repeated character Variant of ledger.com A 52.20.84.62NS ns1.squadhelp.com ledgercom.com Variant Variant of ledger.com A 91.215.86.207NS ns3.epik.com ledget.com Replaced character Variant of ledger.com A 13.248.169.48NS ns1.afternic.com ledgewr.com Inserted character Variant of ledger.com A 185.244.151.84MX ledgewr.comNS ns3.ro.hostsailor.com ledgger.com Repeated character Variant of ledger.com A 13.56.33.8NS ns1.brandbucket.com ledgir.com Vowel swap Variant of ledger.com A 188.114.96.3NS lynn.ns.cloudflare.com ledgor.com Vowel swap Variant of ledger.com A 103.230.136.195MX mxn.mxhichina.comNS ens11.bigwww.com ledgr.com Missing character Variant of ledger.com A 188.114.96.3NS kim.ns.cloudflare.com ledgre.com Swapped characters Variant of ledger.com A 172.65.185.109NS sp1.gname-dns.com ledgrer.com Inserted character Variant of ledger.com A 185.244.151.84MX ledgrer.comNS ns3.ro.hostsailor.com ledgsr.com Replaced character Variant of ledger.com A 14.63.215.245NS ns1.hostname.net ledgwer.com Inserted character Variant of ledger.com A 185.244.151.84MX ledgwer.comNS ns3.ro.hostsailor.com ledgwr.com Replaced character Variant of ledger.com A 185.244.151.84MX ledgwr.comNS ns3.ro.hostsailor.com ledher.com Replaced character Variant of ledger.com A 15.197.148.33MX mailstore1.secureserver.netNS ns03.domaincontrol.com ledhger.com Inserted character Variant of ledger.com A 185.244.151.84MX ledhger.comNS ns3.ro.hostsailor.com ledsger.com Inserted character Variant of ledger.com A 185.244.151.84MX ledsger.comNS ns3.ro.hostsailor.com ledtger.com Inserted character Variant of ledger.com A 188.114.96.3NS janet.ns.cloudflare.com ledyer.com Replaced character Variant of ledger.com A 31.43.160.6MX alt1.aspmx.l.google.comNS ns-1051.awsdns-03.org ledzer.com Replaced character Variant of ledger.com A 188.114.96.3NS kimora.ns.cloudflare.com leedger.com Inserted character Variant of ledger.com MX mxbiz1.qq.comNS dns10.hichina.com legder.com Swapped characters Variant of ledger.com A 64.190.63.222MX localhostNS ns1.sedoparking.com leger.com Missing character Variant of ledger.com A 216.40.34.37MX mx.netidentity.com.cust.hostedemail.comNS ns1.mailbank.com lerdger.com Inserted character Variant of ledger.com A 185.244.151.84MX lerdger.comNS ns3.ro.hostsailor.com lerger.com Replaced character Variant of ledger.com A 13.248.169.48NS ns1.afternic.com lesger.com Replaced character Variant of ledger.com A 185.244.151.84MX lesger.comNS ns3.ro.hostsailor.com lewdger.com Inserted character Variant of ledger.com A 185.244.151.84MX lewdger.comNS ns3.ro.hostsailor.com lidger.com Vowel swap Variant of ledger.com A 66.241.124.184MX route1.mx.cloudflare.netNS erin.ns.cloudflare.com lledger.com Repeated character Variant of ledger.com A 50.254.19.65MX lledger-com.mail.protection.outlook.comNS ns-1532.awsdns-63.org lodger.com Vowel swap Variant of ledger.com A 149.210.148.65MX mail.lodger.comNS aron.ns.cloudflare.com lrdger.com Replaced character Variant of ledger.com A 77.247.179.85MX mail.h-email.netNS ns1.badgerdns.com lsdger.com Replaced character Variant of ledger.com A 14.63.215.245NS ns1.hostname.net oedger.com Replaced character Variant of ledger.com A 14.63.215.245NS ns1.hostname.net pedger.com Replaced character Variant of ledger.com A 74.220.199.6 pledger.com Inserted character Variant of ledger.com A 216.40.34.37MX mx.netidentity.com.cust.hostedemail.comNS ns1.mailbank.com dedger.com Bit flip Variant of ledger.com MX aspmx1.migadu.comNS apollo.ns.cloudflare.com hedger.com Bit flip Variant of ledger.com A 15.197.225.128MX alt1.aspmx.l.google.comNS ns23.domaincontrol.com iedger.com Lookalike letters Variant of ledger.com A 217.70.184.38MX fb.mail.gandi.netNS ns-157-c.gandi.net l-edger.com Added hyphen Variant of ledger.com A 216.198.79.65NS ns1.vercel-dns.com ladger.com Bit flip Variant of ledger.com A 185.80.2.134MX ladger.comNS ns209.superhosting.bg lcdlger.com Lookalike letters Variant of ledger.com NS ns2.my-ndns.com lddger.com Bit flip Variant of ledger.com A 14.63.215.245NS ns1.hostname.net lebger.com Lookalike letters Variant of ledger.com A 104.247.81.99NS ns1.parkingcrew.net leclger.com Lookalike letters Variant of ledger.com A 34.42.100.71NS ns-cloud-e1.googledomains.com ledcer.com Bit flip Variant of ledger.com A 15.197.148.33MX ledcer-com.mail.protection.outlook.comNS pdns11.domaincontrol.com leddger.com Inserted character Variant of ledger.com A 13.248.169.48NS ns1.afternic.com ledeer.com Bit flip Variant of ledger.com A 13.248.169.48NS ns1.dan.com ledeger.com Inserted character Variant of ledger.com A 103.224.182.253MX park-mx.above.comNS ns1.abovedomains.com ledfer.com Bit flip Variant of ledger.com A 15.197.142.173MX mailstore1.secureserver.netNS ns11.domaincontrol.com ledg-er.com Added hyphen Variant of ledger.com A 162.255.119.245MX mail.protonmail.chNS dns1.registrar-servers.com ledgar.com Bit flip Variant of ledger.com A 13.248.169.48NS ns1.namefind.com ledger0.com Added character Variant of ledger.com A 20.82.12.44MX ledger0-com.mail.protection.outlook.comNS ns1-04.azure-dns.com ledger1.com Added character Variant of ledger.com A 44.232.173.249NS launch1.spaceship.net ledger4.com Added character Variant of ledger.com A 52.201.53.166NS nsg1.namebrightdns.com ledger5.com Added character Variant of ledger.com MX mail.protonmail.chNS ns-1175.awsdns-18.org ledger6.com Added character Variant of ledger.com A 52.20.84.62NS ns1.atom.com ledgerb.com Added character Variant of ledger.com A 91.195.240.82NS ns1dhl.name.com ledgerc.com Added character Variant of ledger.com A 198.185.159.144MX alt1.aspmx.l.google.comNS dns1.p02.nsone.net ledgerf.com Added character Variant of ledger.com A 94.75.193.73MX mail.h-email.netNS ns1.thednscloud.com ledgeri.com Added character Variant of ledger.com A 52.20.84.62NS ns1.atom.com ledgern.com Added character Variant of ledger.com A 192.0.78.162MX ledgern-com.mail.protection.outlook.comNS ns1.wordpress.com ledgerq.com Added character Variant of ledger.com A 31.43.160.6MX ledgerq-com.mail.protection.outlook.comNS ns03.domaincontrol.com ledgerx.com Added character Variant of ledger.com A 198.202.211.1MX usb-smtp-inbound-1.mimecast.comNS alla.ns.cloudflare.com ledges.com Bit flip Variant of ledger.com A 170.249.218.186MX ledges-com.mail.protection.outlook.comNS ns47.domaincontrol.com ledgez.com Bit flip Variant of ledger.com A 67.23.254.40MX ledgez.comNS ns1.reseller-228.mco2.hostdime.com ledgur.com Bit flip Variant of ledger.com A 13.248.243.5MX ledgur-com.mail.protection.outlook.comNS ns23.domaincontrol.com lediger.com Lookalike letters Variant of ledger.com A 185.225.135.100MX mail02.lediger-consulting.deNS ns1.routing.net ledqer.com Lookalike letters Variant of ledger.com A 13.223.25.84NS nsg1.namebrightdns.com leeger.com Bit flip Variant of ledger.com A 194.191.24.29MX alt1.aspmx.l.google.comNS cns1.cloudpit.de leelger.com Lookalike letters Variant of ledger.com A 15.197.148.33NS ns69.domaincontrol.com lefger.com Bit flip Variant of ledger.com A 103.224.182.244MX park-mx.above.comNS ns1.abovedomains.com letger.com Bit flip Variant of ledger.com A 156.245.108.206NS ns1.dnsowl.com ludger.com Bit flip Variant of ledger.com A 18.195.62.85MX ludger-com.mail.protection.outlook.comNS ns11.worldnic.com

Showing 100 of 151

Evidence & External Reports

Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20261026-4F33B7 Recipient: abuse@ovh.net
PDF notice generated Notice text archived (819 characters)
Abuse notice text as sent to the provider
AUP & Terms of Service Violations:
Acceptable Use Policy: Active phishing operations targeting internet users directly violate standard AUP provisions prohibiting fraud and deceptive practices.
Terms of Service: Material breach of service terms regarding malicious use, providing contractual justification for immediate suspension.
Applicable Legal Framework (FR):
French Penal Code Article 323-1
French Penal Code Article 313-1 (Fraud)
Law for a Digital Republic
French law prohibits fraudulent access to automated data processing systems.
Investigation Notice: We fully respect your internal investigation processes and discretion. Prompt remediation protects innocent users while mitigating regulatory compliance scrutiny, legal liability, and brand reputation risks associated with ongoing malicious infrastructure.
Deep Analysis

Were You Affected by This Site?

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. Secure your accounts and funds first, then report. 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.

Where to report

The draft stays only with you.

First secure your money: call your bank or revoke wallet approvals. Immediate steps →

More: international and crypto channels

Official reporting routes

More official reporting routes
SEAL 911 Worldwide

Emergency help from security researchers when a crypto wallet is being drained right now.

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.

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.

  • Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
  • Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
  • Approved token spending (approve / permit) — revoke that approval with a token-approval checker (revoke.cash)
  • Sent crypto — save the transaction hash, your address and the receiving address; blockchain transactions cannot be reversed
  • 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
  • Downloaded a file — do not open it and scan the device with security software

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 firmo-ledger.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.

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