On 2026-10-01, live-ledgres-us.pages.dev returned an HTTP 403 response in the recorded check. The same domain appears on two named external blocklists, MetaMask and SEAL, and was first observed on 2026-09-08.
Recorded Evidence
The HTTP check on 2026-10-01 recorded status 403 for live-ledgres-us.pages.dev. First observation of the domain was logged on 2026-09-08. The external blocklist review on 2026-10-01 listed MetaMask and SEAL, giving an external blocklist count of 2. A VirusTotal check on 2026-09-18 reported 0 detections across 89 scanners. The PageSpeed check on 2026-09-16 returned a performance score of 95. The domain resolved to IP address 188.114.97.9, associated with CloudFlare, Inc. in CA.
Interpretation
The named external blocklists and the internal listing describe how this domain is categorized by those sources, while the VirusTotal result reflects a separate scanner set. The HTTP 403 response, the PageSpeed score and the blocklist entries come from different checks on different dates, so they should be compared as distinct records rather than merged into a single trend. The chronology from first observation to the later checks shows the domain was recorded across multiple dates, but the dates alone do not establish a change in behavior.
Recommended Actions
Preserve the recorded HTTP response for live-ledgres-us.pages.dev and the external blocklist entries from MetaMask and SEAL as separate source records. Compare the VirusTotal scanner result with the blocklist listings in separate reviews, since they measure different things. Retain the PageSpeed observation and the first-observed record for future reference. Recheck the domain's HTTP status and blocklist presence on a later date to see whether the recorded sources change.
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:27 UTCcurrent episode first observed: 2026-10-01 01:39:31 UTCobserved RIP window: 2026-09-08 20:28:27 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.
Google PageSpeed Insights — mobile performance audit of live-ledgres-us.pages.dev· checked Sep 16, 2026
95
Good
Performance
FCP
0.85s
First Contentful Paint
LCP
1.92s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
197ms
Total Blocking Time
SI
3.67s
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 08:33:12 UTC
Domain ingestion complete. Initial state is marked as alive.
威胁响应 Pipeline
发现
Analysis
Monitoring
10 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.
黑名单检测
见于 2 blocklists: MetaMask, SEAL
2026年10月14日
CF Radar: Malicious
Cloudflare Radar classified this domain as phishing
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
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)
