VirusTotal
4 / 89
need-ledgr-live.pages.dev returned HTTP status 200 on 2026-10-01, according to the recorded HTTP check. The same record set shows a first observation on 2026-09-08, roughly three weeks earlier.
The domain appears on three named external blocklists: MetaMask, SEAL, and PhishFeed, and it also carries a PhishDestroy internal listing. VirusTotal recorded 4 detections across 89 scanners on 2026-09-21. The SSL certificate was scanned on 2026-09-16 and issued by Google Trust Services / WE1, while the page performance score of 100 was recorded on 2026-09-16.
The blocklist checks and HTTP check share the 2026-10-01 date, so those two observations can be compared directly, while the VirusTotal scan from 2026-09-21 and the SSL scan from 2026-09-16 predate them. Because the observation dates differ, the named sources describe the domain at different points in time rather than a single consistent snapshot.
Anyone reviewing need-ledgr-live.pages.dev should retain the dated records from PhishDestroy, VirusTotal, and the named blocklists so later observations can be compared against them. Avoid submitting passwords, payment details, or other sensitive information while examining the domain. Subsequent checks should be logged with their own dates so changes in status or listings remain traceable.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
cloudflareScanner note: alive_content: raw=ok; http=200; via=https_proxy; server=cloudflare
Edge-IP reputation is not attributed to this domain.
Location describes the IP network.
42f4b4f8a97fcf7a65db7f3bb91793e032d18d467ec7954098a2a79be63c7afcSaved 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 need-ledgr-live.pages.dev · checked Sep 16, 2026
188.114.96.9. 8 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.
79 stored lookalike domains
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
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