VirusTotal
18 / 92
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
“Ledger® Live - Login | Secure Access to Your Wallet”
Assessment based on the stored source evidence below. Review sources →
These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.
18 / 92
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
provider verdict: malicious
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
malicious
ReportThis is the recorded automated analysis. Completion alone is not a safety verdict.
2 external matches
DetailsA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
no community references
ReportCommunity publication references, not a vendor verdict or evidence of a common operator.
stored report
A preserved page image documents what the collector received; a capture is not a safety verdict.
Checked; no threat flag recorded
ReportA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
AI-assisted analysis Stored narrative · generated . Provider checks below retain their own observation dates. This narrative is an interpretation of collected evidence, not an independent source verdict.
livledgerlog.framer.media returned an HTTP status 200 on 2026-10-15, showing a successful response was recorded on that date. The domain was also observed on the same date with entries on three external blocklists.
On 2026-10-15, the HTTP status for livledgerlog.framer.media was recorded as 200. The domain appeared on the MetaMask, SEAL, and PhishFeed external blocklists as of 2026-10-15. VirusTotal, on 2026-10-14, documented 18 detections out of 92 total scanners. PhishDestroy internally listed the domain on 2026-10-15.
The VirusTotal record contains a measurement of detections from multiple scanners, providing a quantitative assessment from that source. The HTTP status observation documents a successful response, which is a technical indicator of the domain's response at a specific time. The presence of the domain on MetaMask, SEAL, and PhishFeed blocklists expands the context of the evidence with multiple external references.
For livledgerlog.framer.media, preserve the HTTP status, VirusTotal, and external blocklist records for future comparison. Reference the PhishDestroy internal listing and VirusTotal scanner results when conducting subsequent reviews. Store all current evidence to support ongoing technical assessments and blocklist checks.
22 · datasets with records / 9 · not recorded
What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.
These checks have no retained result. This does not mean they passed or that a scan is running.
2 · external source matches
CSC Corporate Domains, Inc. · 31.43.160.6 · DNS, TLS and retained responses
ns-97.awsdns-12.comLocation describes the IP network.
b2c0a2324388fb7095a65d4199119b9e4e948be90e4a8b395a89962f1b9f26c9Saved 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 livledgerlog.framer.media · checked Oct 14, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://livledgerlog.framer.media/https://livledgerlog.framer.media/Cache-Control: public, max-age=0, must-revalidateContent-Encoding: gzipContent-Type: text/htmlServer: Framer/24ab00fa8c604f5780004055234eb042141127c52abe99560f73a8f68395bff99c38ec4summary_large_imageh3=":443"; ma=2592000public, max-age=0, must-revalidategzip15098text/htmlWed, 14 Oct 2026 19:43:36 GMT"4b34ace7a12e9bccdfd6a69657540250"f40d7f22ca3b868e147f56bcdbf4dd6e9181a8f314ace4bc0641505286dea97cWed, 10 Dec 2025 12:36:35 GMT; rel="preconnect", ; rel="preconnect"; crossorigin=""Framer/24ab00fregion;desc="ca-central-1", cache;desc="not-cached", ssg-status;desc="optimized", version;desc="24ab00f", instance;desc="c6aec8b", route;dur=1;desc="id=augiA20Il&locale=default", country;desc="CA"max-age=31536000Accept-Encoding, AcceptnosniffValues retained by the collector; long values may be shortened during collection.
Stored file checks, including unavailable and invalid responses. Retained contents and paths appear where available.
/robots.txt
A legacy response is stored, but it does not establish whether the file exists.
/sitemap.xml
A legacy response is stored, but it does not establish whether the file exists.
/.well-known/security.txt
A legacy response is stored, but it does not establish whether the file exists.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Stored browser and crawler observations
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Framer/24ab00fLocal archived 2026-10-14 19:43:37 UTCScanner note: alive_content: raw=ok; http=200; via=https_proxy; server=Framer/24ab00f
Collection history, report status and investigation channels
31.43.160.6.Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown→live_content
content_served
live_content→Unknown
probe_inconclusive
Unknown→live_content
content_served
Unknown
stale_current_evidence
Unknown
12 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.
Shared hosting, registrar records and related domains
151 stored lookalike domains
Showing 100 of 151
Original reports, independent checks and evidence links
Recovery steps, reporting contacts and complaint drafts
Listed domains receive at least one abuse report; this entry has no retained notification history.
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 →.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
livledgerlog.framer.media)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
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
Stored evidence snapshot. Source timestamps appear where available.
Captured title: “Ledger® Live - Login | Secure Access to Your Wallet”. Apparent target: Ledger.
VirusTotal detections for livledgerlog.framer.media: 18 (2026-10-14 23:11:06 UTC).
Each source records a particular observation. A screenshot, an available website, or a result with no detections does not establish that a site is safe. Source results can change after they are collected.
submit an appeal or review the FAQ page.