VirusTotal
2 / 92 engine detections
Open reportledgerlive.org.im is a Ledger impersonation page detected by PhishDestroy on 2026-10-23. Risk: critical (83/100). Status: Last known active. Hosting: ExpressHost Ltd. VirusTotal: 2/92 engines flag it. Listed on Spamhaus DBL. Do not enter credentials or connect a wallet.
“Site is being set up...”
2 / 92 engine detections
Open reportSuspicious
Open reportDBL_SPAM
2 community references
Open reportNo threat flag
Open reportNo malicious flag
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
PhishDestroy’s intake analysis noted that the page only displays a “Site is being set up…” message, meaning no functional content could be examined. The domain was first seen by PhishDestroy on 2026-10-23. An HTTP 200 response was recorded on that date.
The listing does not point to a specific phishing or wallet‑draining technique; it reflects a generic risk where newly registered placeholder domains can later be repurposed for impersonation or credential collection. No malicious behavior was observed on the captured page.
VirusTotal scanned the domain on 2026-10-23 and reported 2 suspicious detections out of 92 engines, with Fortinet and alphaMountain.ai labeling it as spam. Google Safe Browsing checked on 2026-10-23 and reported no threat. External blocklists MetaMask and SEAL listed the domain, and Spamhaus DBL marked it as spam on 2026-10-23. OTX recorded two pulses referencing the domain on 2026-10-23. URLScan captured a snapshot on 2026-09-28; its overall verdict was clean, though its machine‑learning engine assigned a malicious score of 46. PhishDestroy’s internal blocklist includes the domain as of 2026-10-23.
The domain was registered two days before first observation and uses a Let’s Encrypt certificate issued on 2026-09-25, valid until 2026-12-24. The recorded IP address is 154.86.119.151, hosted by ExpressHost Ltd in the Netherlands. Authoritative nameservers are a.dnspod.com, b.dnspod.com and c.dnspod.com. The server responded with nginx and PHP, and ports 22, 80 and 443 were open.
Visitors should avoid entering any credentials, seed phrases or wallet approvals on this site. If any sensitive data was submitted, change passwords immediately and monitor associated accounts for suspicious activity. Defenders can block ledgerlive.org.im at the perimeter and review logs for connections to 154.86.119.151.
Stored page, network and scanner observations, grouped by source and observation time.
Observed: · Retrieved:
| Uuid | 01a166c6-2d18-71ed-a279-8aaa10a1058d |
|---|---|
| Final url | http://ledgerlive.org.im/ |
| Status | 200 |
| Redirects | [
{
"to": "https://ledgerlive.org.im/",
"from": "http://ledgerlive.org.im/",
"status": 307
},
{
"to": "http://ledgerlive.org.im/",
"from": "https://ledgerlive.org.im/",
"status": 307
}
] |
| Ip | 154.86.119.151 |
| Ptr | Wild-Cloud-o4BgF6zj.expresshost.cloud |
| Contacted domains | [
"fonts.gstatic.com",
"fonts.googleapis.com"
] |
| Contacted IP addresses | [
"142.251.20.94",
"142.251.14.95",
"154.86.119.151"
] |
| Asns | [
"15169",
"197574"
] |
| Countries | [
"US",
"NL"
] |
| Document hash | 9c42050d7163caf718859ca3616308c9e6af3e3f29f8a8dabf2a68b03553d111 |
| Cookies | [
"PHPSESSID"
] |
| Domain age days | 27 |
| Apex age days | 27 |
| Requests | 3 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": 81,
"malicious": true
},
"overall": {
"score": 0,
"malicious": false
}
} |
| HTTP headers | {
"server": "nginx",
"content-type": "text/html; charset=UTF-8",
"x-frame-options": "SAMEORIGIN",
"x-content-type-options": "nosniff",
"referrer-policy": "strict-origin-when-cross-origin",
"permissions-policy": "geolocation=(), microphone=(), camera=()"
} |
Observed: · Retrieved:
| Uuid | 698f64e5-80bd-4396-811b-8328294cca77 |
|---|---|
| Final url | https://ledgerlive.org.im/ |
| Status | 200 |
| History | [
{
"url": "https://ledgerlive.org.im/",
"status": 200
}
] |
| DOM structure hash | 92533d6d9f881bfe5059dae7ee137a6be31a649c436144a859ea4d3dcb024978 |
| Document hash | 9c42050d7163caf718859ca3616308c9e6af3e3f29f8a8dabf2a68b03553d111 |
| Domain risks | [
"Newly Seen Domains",
"Security Risks"
] |
| Radar rank | {
"bucket": ">200000"
} |
| DNS records | [
{
"name": "ledgerlive.org.im",
"type": "A",
"value": "154.86.119.151"
}
] |
| Dnssec valid | false |
| Ip | 154.86.119.151 |
| Registration record | {
"expires": "2027-09-26T00:59:59Z",
"nameservers": [
"a.dnspod.com",
"c.dnspod.com"
]
} |
Observed: · Retrieved:
| Vendor result counts | {
"timeout": 0,
"harmless": 52,
"malicious": 0,
"suspicious": 2,
"undetected": 38
} |
|---|---|
| Vendor labels | {
"Fortinet": "spam",
"alphaMountain.ai": "spam"
} |
| Reputation | 0 |
| First seen | 2026-09-25T12:51:21Z |
| DNS records | [
{
"ttl": 21600,
"type": "NS",
"value": "a.dnspod.com"
},
{
"ttl": 180,
"type": "SOA",
"rname": "domainadmin.dnspod.com",
"value": "a.dnspod.com"
},
{
"ttl": 600,
"type": "A",
"value": "154.86.119.151"
},
{
"ttl": 21600,
"type": "NS",
"value": "b.dnspod.com"
},
{
"ttl": 21600,
"type": "NS",
"value": "c.dnspod.com"
}
] |
| Dns at | 2026-10-23T02:48:31Z |
| Jarm | 3fd3fd0003fd3fd00042d42d00000000f78d2dc0ce6e5bbc5b8149a4872356 |
| Certificate | {
"san": [
"ledgerlive.org.im",
"www.ledgerlive.org.im"
],
"issuer": "Let's Encrypt / YR2",
"serial": "629bb420d7ebf1e95a326ac8d3266f90bb",
"sha256": "c18ed8a96989810a4764bc6abf9c1e5a2ceedd1a4695a9a00f56d0071454ed1d",
"subject": "ledgerlive.org.im",
"valid_to": "2026-12-24T08:59:50Z",
"valid_from": "2026-09-25T08:59:51Z"
} |
| Registration record | {
"nameservers": [
"a.dnspod.com.",
"c.dnspod.com."
]
} |
| Mail configuration | {
"spf_lookups": 0
} |
|---|---|
| Caa records | {
"domain": "ledgerlive.org.im"
} |
| Protective DNS results | {
"resolvers": 12,
"blocked_count": 0
} |
| Web archive observations | {
"last": "2026-09-25T16:45:39Z",
"first": "2026-09-25T16:45:39Z",
"changes": 0,
"days_archived": 1,
"avg_page_bytes": 853
} |
| Page title and metadata | {
"title": "Site is being set up..."
} |
| Trackers | {
"requests": 2,
"trackers": [
{
"name": "Google Fonts",
"company": "Google",
"country": "US",
"category": "Hosting",
"requests": 1
},
{
"name": "Google Static",
"company": "Google",
"country": "US",
"category": "Hosting",
"requests": 1
}
]
} |
| Forms and mixed content | {
"third_party_scripts": 0
} |
| Status | {
"up": true,
"code": 200,
"timings": {
"dns": 269,
"tls": 82,
"wait": 1475,
"connect": 18,
"download": 0
},
"response_ms": 1844
} |
| TLS connection | {
"alpn": "http/1.1",
"cipher": "TLS_AES_256_GCM_SHA384",
"protocol": "TLSv1.3",
"versions": [
"TLSv1.2",
"TLSv1.3"
],
"authorized": true,
"forward_secrecy": true
} |
| Ports | {
"open": [
22,
80,
443
]
} |
| Carbon | {
"bytes": 1854,
"co2_grams": 0.0001,
"cleaner_than": 95
} |
| Dns server | {
"ns": [
{
"ip": "117.135.128.175",
"host": "a.dnspod.com"
},
{
"ip": "43.161.3.75",
"host": "b.dnspod.com"
},
{
"ip": "125.94.59.175",
"host": "c.dnspod.com"
}
],
"zone": "ledgerlive.org.im"
} |
| Cookies | {
"cookies": [
{
"name": "PHPSESSID",
"session": true
}
]
} |
| Location | {
"ip": "154.86.119.151",
"asn": "197574",
"org": "ExpressHost Ltd",
"city": "Amsterdam",
"country": "NL"
} |
| Ssl | {
"issuer": "Let's Encrypt / YR2",
"subject": "ledgerlive.org.im"
} |
| DNS records | {
"A": [
"154.86.119.151"
],
"NS": [
"a.dnspod.com",
"b.dnspod.com",
"c.dnspod.com"
],
"SOA": "{\"nsname\": \"a.dnspod.com\", \"hostmaster\": \"domainadmin.dnspod.com\", \"serial\": 1791710457, \"refresh\": 3600, \"retry\": 180, \"expire\": 1209600, \"minttl\": 180}"
} |
| Dnssec | {
"ds": false,
"rrsig": false,
"dnskey": false
} |
| Hsts | {
"message": "Site does not serve any HSTS headers."
} |
| HTTP security policies | {
"xFrameOptions": "SAMEORIGIN",
"referrerPolicy": "strict-origin-when-cross-origin",
"xXSSProtection": false,
"permissionsPolicy": "geolocation=(), microphone=(), camera=()",
"xContentTypeOptions": "nosniff",
"contentSecurityPolicy": false,
"strictTransportPolicy": false,
"crossOriginOpenerPolicy": false,
"crossOriginEmbedderPolicy": false,
"crossOriginResourcePolicy": false
} |
| Get ip | {
"ip": "154.86.119.151",
"family": 4
} |
| Redirects | {
"chain": [
"https://ledgerlive.org.im"
]
} |
| Subdomains | {
"count": 1,
"subdomains": [
"www.ledgerlive.org.im"
]
} |
| Tech stack | {
"technologies": [
"PHP",
"Nginx"
]
} |
| HTTP headers | {
"headers": {
"server": "nginx",
"content-type": "text/html; charset=UTF-8",
"x-frame-options": "SAMEORIGIN",
"x-content-type-options": "nosniff",
"referrer-policy": "strict-origin-when-cross-origin",
"permissions-policy": "geolocation=(), microphone=(), camera=()"
}
} |
No. PhishDestroy classifies ledgerlive.org.im as a Ledger impersonation page (risk: critical, 83/100); it was first detected on 2026-10-23. VirusTotal: 2/92 engines flag it. Listed on Spamhaus DBL. Treat the site as unsafe.
No. Do not connect a wallet, sign messages or approve tokens on ledgerlive.org.im. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.
Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.
Last checked
a.dnspod.comb.dnspod.comc.dnspod.comLocation describes the IP network.
c18ed8a96989810a4764bc6abf9c1e5a2ceedd1a4695a9a00f56d0071454ed1dledgerlive.org.imwww.ledgerlive.org.imSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.ledgerlive.org.imDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of ledgerlive.org.im · checked Oct 23, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://ledgerlive.org.im/Server: nginxContent-Type: text/html; charset=UTF-8Cache-Control: no-store, no-cache, must-revalidateContent-Encoding: gzipno-store, no-cache, must-revalidategzip807text/html; charset=UTF-8Fri, 23 Oct 2026 01:44:22 GMTThu, 19 Nov 1981 08:52:00 GMTgeolocation=(), microphone=(), camera=()no-cachestrict-origin-when-cross-originnginxAccept-EncodingnosniffSAMEORIGINValues retained by the collector; long values may be shortened during collection.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Page captured
View source2 community references
View sourceNo threat flag
View source2/92 engine detections
View sourceledgerlive.org.im
View source151 stored lookalike domains
Showing 100 of 151
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
ledgerlive.org.im
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 ↗
ledgerlive.org.im)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
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.