On 2026-10-01, media-ledger.pages.dev returned an HTTP status code of 502 in a recorded observation. The same record set notes first observation of this domain on 2026-09-08.
Recorded Evidence
An HTTP check dated 2026-10-01 recorded status 502 for media-ledger.pages.dev. A blocklist check dated 2026-10-01 recorded two external listings, named as MetaMask and SEAL. VirusTotal, checked 2026-09-17, reported 14 detections across 89 scanners. A PageSpeed check dated 2026-09-16 recorded a performance score of 100, and an SSL scan on the same date recorded issuer WE1. The domain also appears on the internal PhishDestroy listing.
Interpretation
The HTTP and blocklist records share the 2026-10-01 date, while the VirusTotal and PageSpeed observations fall on earlier dates, so these sources describe different moments rather than one coordinated snapshot. Because the blocklist and VirusTotal records come from separate named sources with separate dates, their counts should be read as distinct observations rather than a single combined measure. The 502 response is a dated record only and does not establish present availability.
Recommended Actions
Retain the dated records for media-ledger.pages.dev, including the HTTP, blocklist, VirusTotal, PageSpeed and SSL observations, so later checks can be compared against them. When reviewing media-ledger.pages.dev, compare any new observation with the recorded dates and values instead of relying on a single result. Avoid submitting passwords, payment details or other sensitive information while the review remains open.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
저장된 은신 플래그
아직 스캔되지 않았습니다
마지막 은폐 스캔
스캐너 메모:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='media-ledger.pages.dev', port=80): Max retries exceeded with url: / (Caused by NewConnecti
TDS 지문 인식 실시간 확인
이 패널이 열려 있을 때 PhishDestroy 스캐너에서 실행되는 7개의 케이타로 지문과 크롤러 대 브라우저 비교 결과.
IP ContextCloudflare shared edgeorigin IP hiddenEdge-IP 평판은 이 도메인에 귀속되지 않습니다.
플랫폼 제공자Cloudflare Pages
최초 이용 불가까지 걸린 시간8 days
집계 기준
처음 저장된 악용사례 신고부터 콘텐츠를 사용할 수 없다는 첫 번째 관찰까지의 경과 시간입니다. 이것은 원인을 확립하지 못합니다.
각 보고서에 포함된 내용
저장된 발신 보고서 기록은 공급업체 평가, 등록 데이터, 호스팅 세부 정보, 분류 또는 스크린샷과 같이 당시 사용 가능한 증거를 참조할 수 있습니다. 이 페이지는 전달된 정확한 페이로드, 수신, 확인 또는 수신자의 작업을 추론하지 않습니다.
기술 세부 정보Provenance & timestamps
최초 발견2026년 9월 8일
페이지 제목
Suspected Phishing | Cloudflare
Impersonates
Ledger
TLS 인증서
Hostname coverage not recorded·
발급자 WE1
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
188.114.97.9
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 time
2026-09-16 01:02:04 UTC
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.
Latest HTTP observation알 수 없음Probe Inconclusive20%2026-10-11 01:14:40 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-09-08 20:28:20 UTC
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: 14 detections
alphaMountain.ai
BitDefender
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
카스퍼스키
LevelBlue
Lionic
MalwareURL
소포스
VIPRE
Webroot
사이트 성능 분석
Google PageSpeed Insights — mobile performance audit of media-ledger.pages.dev· checked Sep 16, 2026
100
Good
Performance
FCP
0.76s
First Contentful Paint
LCP
1.83s
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.
VirusTotal Detections Update2026-09-17 20:35:06 UTC
VirusTotal scanner detections updated from 13 to 14. Added scanner alerts: alphaMountain.ai.
Domain Status Transition2026-09-16 10:00:28 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-15 22:03:10 UTC
Domain ingestion complete. Initial state is marked as alive.
위협 대응 Pipeline
발견
Analysis
Monitoring
15 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.
최근에 저장된 확인 결과에 따르면 보고된 콘텐츠를 사용할 수 없습니다. 이는 변경의 원인이 누구인지, 원인이 무엇인지 확인하지 않습니다.
2026년 9월 16일
최초 이용 불가까지 걸린 시간
감지부터 사용할 수 없는 첫 번째 관찰까지 183 시간이 경과되었습니다.
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.
