VirusTotal
8 / 92
Brand impersonation: Ledger
Availability last checked First listed Oct 14, 2026 VirusTotal analysed Oct 14, 2026 UTC
Based on 3 recorded source signals. The score is a heuristic over stored detections, not a probability or confidence level.
View evidenceHTTP 301
Latest stored reachability observation
HTTP 301 is a redirect response. The redirect destination and its content were not recorded with this observation.
Source checks and detection results recorded for this domain, with the time each was observed.
Stored written summary, generated Oct 14, 2026. It is not updated when source results change.
The domain ledger.com.am recorded an HTTP status code of 301 on 2026-10-15, reflecting a redirect response at that time. On 2026-10-14, it was also noted on two external blocklists, highlighting its presence in security monitoring systems.
On 2026-10-14, ledger.com.am was listed on both the MetaMask and SEAL external blocklists. VirusTotal checked the domain on 2026-10-08, documenting 8 detections out of 92 total scanners. OTX referenced the domain in two pulses as of 2026-10-15. The PhishDestroy internal listing included ledger.com.am, and a PageSpeed performance score of 100 was recorded on 2026-10-14.
The VirusTotal record contains a quantitative detection measurement from multiple scanners, while OTX documents community-driven security references called pulses. The HTTP status entry describes a redirect response, which is a technical observation rather than a content assessment. These sources together provide a multi-faceted view of ledger.com.am’s recorded security context across different dates.
For ledger.com.am, preserve the VirusTotal, OTX, and PhishDestroy records for future comparison with subsequent security checks. Reference the MetaMask and SEAL blocklist entries to monitor changes in external blocklist status. Retain the HTTP status and PageSpeed measurements as technical benchmarks for later network reviews.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Local archived 2026-10-14 23:29:54 UTCScanner note: redirect: raw=redirect_301; http=301; via=http_proxy; location=https://ledger.com.am/
Location describes the IP network.
1b3ff4de5c7479b759492149e09e340032c47c7e9b49e776e0c77e1ba50b8a16Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of ledger.com.am · checked Oct 14, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://ledger.com.am/https://ledger.com.am/Cache-Control: no-cacheContent-Type: text/htmlno-cachetext/htmlValues retained by the collector; long values may be shortened during collection.
136.65.148.138. 9 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
151 stored lookalike domains
Showing 100 of 151
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive