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.
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.
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.
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.
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/
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.
IP Reputation213.186.33.518/100abuse score · abuse reports about this server's IP address, not about the domain; higher = worseThis IP address has a low abuse score, but the domain itself is recognized as phishing.5 reportsDDoS AttackEmail SpamPort Scanchecked 2026-10-26last reported
Latest HTTP observationRedirectingHTTP redirect observed80%2026-11-22 11:15 UTC
RDAP registration
Observed timelinelast 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.
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.
Recorded events: 13. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
The domain remains reachable or access-restricted; future checks may update this observation.
ongoing
Recorded activity
5 entries
Lifecycle
Domain registered
Added to PhishDestroy+68 h 17 min
First abuse report sent+6 min
VirusTotal analysis with detections+26 min
Reported 68 h 23 min after registration
AlienVault OTX
4 community references
+5 h 46 min
VirusTotal
2/92 engine detections
+26 min
Abuse report sent
PD-20261026-4F33B7 · Receipt 83433
abuse@ovh.net
+6 min
Added to PhishDestroy
firmo-ledger.com
same minute
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
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
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.
Names that imitate the brand, found by dnstwist. A similar name alone does not prove the same owner.
Report all
A similar name alone does not prove fraud. Send the list to services that check each address themselves. Report a domain as phishing only if you saw a fake page on it.
Supporting signal — Shares a page feature, infrastructure or a collector label; not proof of one operator.
Discovery only — Same registrar or CDN edge: listed for navigation, not evidence of a link.
Each spoke is one reason a domain is linked to this report. Node size marks VirusTotal detections, dashed nodes are already offline, and the full lists follow below. Full list of related reports
Content matches4
Same favicon file hash, or a recorded page title that starts with the same 20 characters. A content match does not establish a shared phishing kit or owner.
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.
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.
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)
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
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.