On 2026-10-01, live-ledgr-io-en.pages.dev returned an HTTP 403 status code, a recorded response for that date. The domain was first observed on 2026-09-08, according to the same evidence set. A PageSpeed check on 2026-09-16 recorded a performance score of 99 for the domain.
Recorded Evidence
VirusTotal checked the domain on 2026-09-18 and recorded 15 detections across 89 scanners. MetaMask and SEAL appeared as external blocklists on 2026-10-01. PhishDestroy recorded an internal listing, and the blocklist check date was 2026-10-01. The HTTP check on 2026-10-01 resolved to IP address 188.114.97.9, associated with CloudFlare, Inc. in CA.
Interpretation
The VirusTotal record covers scanner detections on its own check date, while the external blocklists and PhishDestroy listing reflect separate source records. The HTTP 403 response describes only the response recorded on 2026-10-01 and does not describe all content on the domain. The first-observed date and the PageSpeed check date differ from the blocklist and HTTP check dates, so those observations come from different points in time. The IP organization and country are recorded attributes of the address at check time.
Recommended Actions
For live-ledgr-io-en.pages.dev, preserve the VirusTotal detection record, the MetaMask and SEAL blocklist entries, and the PhishDestroy internal listing for later comparison. Compare the HTTP status observation against future checks of the same domain, and compare the PageSpeed score against later measurements in a separate sentence. Keep the first-observed record alongside these sources so each dated observation remains traceable.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Observed timelinelast reachable: 2026-09-08 20:28:26 UTCcurrent episode first observed: 2026-10-01 01:39:31 UTCobserved RIP window: 2026-09-08 20:28:26 UTC → 2026-10-01 01:39:31 UTC · 533.18hmidpoint estimate ≈ 2026-09-19 23:03:58 UTC · precision low · basis bounded
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.
技术 · 3 identified
H
HSTS
安全
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
Last analyzed First positive detection Previous stored snapshot: 15 detections
alphaMountain.ai
BitDefender
CyRadar
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
卡巴斯基
LevelBlue
Lionic
MalwareURL
Netcraft
Sophos
VIPRE
网站性能分析
Google PageSpeed Insights — mobile performance audit of live-ledgr-io-en.pages.dev· checked Sep 16, 2026
99
Good
Performance
FCP
0.78s
First Contentful Paint
LCP
1.84s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
2.04s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
Domain Status Transition2026-09-16 10:00:32 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-16 07:53:12 UTC
Domain ingestion complete. Initial state is marked as alive.
威胁响应 Pipeline
发现
Analysis
Monitoring
11 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
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.
(US)
