On 2026-10-01, ledgrecom-lives.pages.dev returned HTTP status 403 in an HTTP check recorded that day. The same domain was first observed on 2026-09-08, according to the recorded first-observation timestamp.
Recorded Evidence
The internal PhishDestroy listing for this domain is recorded as true, while the external blocklist count stands at 2, naming MetaMask and SEAL as of the 2026-10-01 blocklist check. VirusTotal recorded 16 detections across 89 scanners on 2026-09-18. A PageSpeed check on 2026-09-16 produced a performance score of 99, and the HTTP check on 2026-10-01 returned status 403.
Interpretation
The MetaMask and SEAL blocklist entries, the PhishDestroy internal listing, and the VirusTotal result come from different collection points, so their dates do not align and the observations cannot be compared as if simultaneous. The PageSpeed score from 2026-09-16 and the HTTP 403 from 2026-10-01 describe separate checks, and the first observation on 2026-09-08 predates both. These dated records show what each source reported at its own time, without establishing a single current state.
Recommended Actions
Retain the dated records for ledgrecom-lives.pages.dev, including the MetaMask and SEAL blocklist entries and the VirusTotal figures, so later checks can be compared against them. Schedule fresh observations and compare each new result with the corresponding earlier date rather than across sources. During any review, avoid submitting passwords, wallet credentials, or other sensitive information to pages reached through this domain.
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:30 UTCobserved RIP window: 2026-09-08 20:28:28 UTC → 2026-10-01 01:39:30 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
CyRadar
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
卡巴斯基
LevelBlue
Lionic
MalwareURL
SafeToOpen
Sophos
VIPRE
Webroot
网站性能分析
Google PageSpeed Insights — mobile performance audit of ledgrecom-lives.pages.dev· checked Sep 16, 2026
99
Good
Performance
FCP
0.78s
First Contentful Paint
LCP
1.87s
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:30 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)
