The domain live-lgers-com.pages.dev returned HTTP status 403 on 2026-10-01 according to the recorded HTTP check. That same record lists the IP address 172.66.47.122, located in CA and associated with Cloudflare, Inc. The domain was first observed on 2026-09-08, and it appears on the phishdestroy internal listing.
Recorded Evidence
External blocklists MetaMask and SEAL both listed the domain as of the 2026-10-01 blocklist check. VirusTotal recorded 16 detections out of 89 scanners on 2026-09-18. A PageSpeed check on 2026-09-16 returned a performance score of 100. The HTTP check on 2026-10-01 returned status 403, and the first observation of the domain was on 2026-09-08.
Interpretation
The MetaMask and SEAL listings, the phishdestroy internal listing, and the VirusTotal detections come from different checks on different dates, so they cannot be treated as a single simultaneous snapshot. The HTTP 403 on 2026-10-01 and the PageSpeed score on 2026-09-16 describe separate observations made weeks apart. Because the observation dates differ, a reader should compare each source on its own timeline rather than combining them into one conclusion.
Recommended Actions
Anyone reviewing live-lgers-com.pages.dev should retain the dated records from MetaMask, SEAL, VirusTotal, and the HTTP check for later comparison. Subsequent observations of live-lgers-com.pages.dev should be recorded with their own dates so changes can be tracked against the existing entries. During any review, avoid submitting sensitive information to live-lgers-com.pages.dev until the recorded concerns are resolved.
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:28 UTCcurrent episode first observed: 2026-10-01 01:39:31 UTCobserved RIP window: 2026-09-08 20:28:28 UTC → 2026-10-01 01:39:31 UTC · 533.18hmidpoint estimate ≈ 2026-09-19 23:03:59 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: 16 detections
alphaMountain.ai
BitDefender
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
卡巴斯基
LevelBlue
Lionic
MalwareURL
Netcraft
Sophos
VIPRE
Webroot
网站性能分析
Google PageSpeed Insights — mobile performance audit of live-lgers-com.pages.dev· checked Sep 16, 2026
100
Good
Performance
FCP
0.76s
First Contentful Paint
LCP
1.84s
Largest Contentful Paint
CLS
0.001
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
0.76s
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 09:13: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)
