ledger-live-desk-support.pages.dev returned an HTTP status code 403 in a check dated 2026-10-01, indicating a restricted or denied response at that time. The domain was also first observed on 2026-08-31, providing a reference for its earliest recorded activity.
Recorded Evidence
On 2026-09-12, VirusTotal reported 16 detections from 89 scanners for ledger-live-desk-support.pages.dev. The domain appeared on both MetaMask and SEAL external blocklists as of the 2026-10-01 blocklist check. A PageSpeed performance score of 100 was recorded on 2026-09-10.
Interpretation
The blocklist entries from MetaMask and SEAL, as well as the VirusTotal detections, are distinct observations that reflect external assessments of ledger-live-desk-support.pages.dev. The HTTP 403 response and PageSpeed score represent technical checks on separate dates, and each source provides its own measurement without overlap. Chronology shows when each record was made, but does not indicate any change or trend between observations.
Recommended Actions
For ledger-live-desk-support.pages.dev, retain the MetaMask and SEAL blocklist records and the VirusTotal detection report for comparison in future reviews. Keep the HTTP and PageSpeed results as separate technical artifacts. Recheck the domain against these named sources to ensure updated information before making any decisions.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
IP ContextCloudflare shared edgeorigin IP hiddenEdge-IP 평판은 이 도메인에 귀속되지 않습니다.
플랫폼 제공자Cloudflare Pages
HTTP 상태403 Forbidden
Elapsed Since First Report10 days
집계 기준
Raw elapsed time since the first stored abuse report. It is not a registrar response-time measurement. Latest observed status: 연결 가능 · 액세스가 제한됨.
각 보고서에 포함된 내용
저장된 발신 보고서 기록은 공급업체 평가, 등록 데이터, 호스팅 세부 정보, 분류 또는 스크린샷과 같이 당시 사용 가능한 증거를 참조할 수 있습니다. 이 페이지는 전달된 정확한 페이로드, 수신, 확인 또는 수신자의 작업을 추론하지 않습니다.
기술 세부 정보Provenance & timestamps
최초 발견2026년 8월 31일
페이지 제목
Suspected Phishing | Cloudflare
Impersonates
Ledger
TLS 인증서
Hostname coverage not recorded·
발급자 WE1
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
172.66.44.76
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
Toronto, CA
Server header
cloudflare
Edge-IP 평판은 이 도메인에 귀속되지 않습니다.
Location describes the IP network.
TLS 인증서
Issuer
WE1
Hostname coverage
Hostname coverage not recorded
Collection source
PhishDestroy collector
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-08-31 20:28:18 UTCcurrent episode first observed: 2026-10-01 01:37:13 UTCobserved RIP window: 2026-08-31 20:28:18 UTC → 2026-10-01 01:37:13 UTC · 725.15hmidpoint estimate ≈ 2026-09-15 23:02:45 UTC · precision very 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
Criminal IP
alphaMountain.ai
BitDefender
CyRadar
ESET
Emsisoft
Fortinet
G-Data
Gridinsoft
카스퍼스키
Lionic
넷크래프트
OpenPhish
소포스
VIPRE
Webroot
사이트 성능 분석
Google PageSpeed Insights — mobile performance audit of ledger-live-desk-support.pages.dev· checked Sep 10, 2026
100
Good
Performance
FCP
0.76s
First Contentful Paint
LCP
1.82s
Largest Contentful Paint
CLS
0
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-10 22:00:32 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-10 21:33:12 UTC
Domain ingestion complete. Initial state is marked as alive.
위협 대응 Pipeline
발견
Analysis
Monitoring
12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
위협 탐지됨
ledger-live-desk-support.pages.dev 탐지되어 전체 분석을 위해 대기열에 추가됨
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.
도메인은 계속 연결 가능하거나 액세스가 제한되어 있습니다. 향후 점검을 통해 이 관찰 내용이 업데이트될 수 있습니다.
How we investigate & report
Public scans, evidence and abuse channels
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.
