Stored evidence for ledger-auth.com: VirusTotal recorded 5 detections among 89 scanners on 2026-09-23. That ratio reproduces the stored check in its original units and is not converted into another measure. OpenPhish appear as named external blocklist observations for ledger-auth.com. Each item in this report remains at the scope supplied by its dated source record.
Detection Evidence
VirusTotal records 5 detections among 89 scanners in the stored snapshot dated 2026-09-23. The numerator describes scanners that produced detections, while the denominator describes scanners included in that check. The reverse order would materially alter the stored result. The VirusTotal snapshot dated 2026-09-23 supplies no common rationale covering the included scanners, and this report adds none. A later VirusTotal snapshot may contain different values, so any comparison should preserve the exact ratio and date of each snapshot.
Source Context
OpenPhish are recorded as named external blocklist observations for ledger-auth.com in the snapshot dated 2026-09-23. The stored OpenPhish blocklist records supply names and entries, but they supply no shared method or common rationale. PhishDestroy’s catalogue also contains ledger-auth.com as a publisher record. That PhishDestroy record is counted separately from the OpenPhish external blocklist observations. This separation keeps the origin of every entry visible and prevents a single stored item from being counted again under another source label.
Reachability and Timeline
The record first observed ledger-auth.com on 2026-09-23. The OpenPhish blocklist snapshot is dated 2026-09-23 and remains a separate event in the stored timeline. The registration date is separately recorded as 2026-06-01. A URLScan reference was stored on 2026-09-23 as a dated artifact for review. Each timestamp qualifies only the adjacent observation in this timeline. Later collection results should be compared with these dated values without replacing the earlier snapshot.
Registration and Infrastructure
For ledger-auth.com, the registrar field records OwnRegistrar, Inc.; this is kept as an exact source value. The source stores 172.67.157.224 as the observed address in this record. The registration date for ledger-auth.com is recorded as 2026-06-01. The SSL issuer is recorded as Google Trust Services / WE1 in the snapshot dated 2026-09-23. These fields preserve registration, network, and certificate context stored in this record. The report preserves each label and number as a separate source value instead of combining them into an invented aggregate. Keeping the fields separate leaves every infrastructure value traceable to the record that supplied it.
Conclusion
The ledger-auth.com record states that VirusTotal recorded 5 detections among 89 scanners on 2026-09-23. OpenPhish remain named blocklist observations from the snapshot dated 2026-09-23. PhishDestroy remains a separate publisher catalogue entry in the stored record. For ledger-auth.com, the registrar field records OwnRegistrar, Inc.; this remains separate from the other source fields. The observed address field in this record contains 172.67.157.224. The supported conclusion is bounded to the exact stored observations for ledger-auth.com. Any statement beyond those source values would require additional dated material.
Recommended Actions
Avoid submitting sensitive information to ledger-auth.com during review. Use a known service address obtained separately from this report for any necessary access. Defenders can retain ledger-auth.com as an exact indicator and preserve relevant DNS, proxy, and endpoint records. Compare later VirusTotal snapshots and OpenPhish blocklist records with the dated values above instead of replacing them. Keep each later observation with its source date so changes remain visible during follow-up review. If a defensive rule is needed, keep its scope to ledger-auth.com. The stored record does not justify extending that rule to 172.67.157.224 or to other infrastructure records.
Analisis deteksi dan penghindaran
Pemeriksaan penyamaran dan distribusi lalu lintas
Belum dipindaiBelum ada perbedaan yang tercatat antara crawler dan browser
Data pengamatan perbandingan crawler versus browser yang telah disimpan untuk host ini, ditambah pemeriksaan sidik jari secara real-time untuk sistem distribusi lalu lintas bergaya Keitaro.
Bendera penyamaran yang tersimpan
Belum dipindai
Pemindaian penyamaran terakhir
Catatan pemindai:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='ledger-auth.com', port=80): Max retries exceeded with url: / (Caused by NewConnectionError
Pemeriksaan sidik jari secara langsung melalui TDS
Tujuh sidik jari Keitaro ditambah perbandingan antara crawler dan browser; jalankan dari pemindai PhishDestroy saat panel ini terbuka.
Yang kami hitung
Waktu yang berlalu sejak laporan penyalahgunaan pertama kali disimpan hingga pengamatan pertama bahwa konten tersebut tidak tersedia. Hal ini tidak dapat menentukan penyebabnya.
Isi setiap laporan
Catatan laporan keluar yang disimpan dapat merujuk pada bukti yang tersedia pada saat itu, seperti keputusan vendor, data pendaftaran, detail hosting, klasifikasi, atau tangkapan layar. Halaman ini tidak menyimpulkan secara pasti muatan yang dikirimkan, penerimaan, pengakuan, atau tindakan oleh penerima.
Detail teknisProvenance & timestamps
Pertama Kali Terdeteksi23/09/2026
DOM Analysisanalyzed 23/09/2026score 63/1001 brand signal
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS tidak aktifreason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationTidak diketahuiProbe Inconclusive20%2026-10-13 01:31:57 UTC
RDAP registrationTidak diketahui
Observed timelinelast reachable: 2026-09-23 15:45:05 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-23 15:45:05 UTC → 2026-09-30 16:14:55 UTC · 168.50hmidpoint estimate ≈ 2026-09-27 04:00:00 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.
Teknologi · 3 identified
Cloudflare Browser Insights
AnalyticsRUM
Cloudflare Browser Insights is a tool that measures the performance of websites from the perspective of users.
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 ledger-auth.com· checked Sep 23, 2026
96
Good
Performance
FCP
1.55s
First Contentful Paint
LCP
1.55s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
4.9s
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-23 23:04:16 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-23 15:45:05 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 172.67.157.224.
Alur Tanggapan Ancaman Pipeline
Penemuan
Analysis
Notifications
Monitoring
15 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Ancaman Telah Diterima
ledger-auth.com telah terdeteksi dan dimasukkan ke dalam antrian untuk analisis menyeluruh
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.
Pemeriksaan terakhir yang disimpan menunjukkan bahwa konten yang dilaporkan tidak tersedia; ini tidak menentukan siapa atau apa yang menyebabkan perubahan tersebut.
24/09/2026
Waktu hingga pertama kali tidak tersedia
7 jam berlalu dari deteksi hingga observasi pertama yang tidak tersedia.
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.
PDF notice generated Notice text archived (650 chars)
Abuse notice text as sent to the provider
Policy Violations:
Illegal Activities: Active phishing operation targeting victims
Fraud & Deception: Impersonation of legitimate services
Identity Theft: Collection of credentials under false pretenses
Applicable Laws (Unknown):
International Anti-Cybercrime Regulations
Budapest Convention on Cybercrime
Universal Fraud Prevention Laws
Phishing activities violate international cybercrime conventions and Unknown's domestic fraud laws.
Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
7 evidence signal groups linked1 reports recordedKonten tidak tersedia
If credentials were compromised, report immediately. Do not engage with recovery scammers.
Jika Anda memasukkan kredensial akun, informasi pribadi atau pembayaran, atau mengunduh file dari domain ini, segera ambil tindakan. Di bawah ini adalah sumber daya untuk membantu Anda melaporkan insiden tersebut dan melindungi diri Anda sendiri.
Waspadalah terhadap penipu yang mengatasnamakan pemulihan! Penjahat dapat menghubungi korban lagi sambil berpura-pura menjadi penyelidik, pengacara, atau agen pemulihan. Jangan membayar biaya di muka atau membagikan kredensial.Pelajari lebih lanjut tentang penipuan dalam proses pemulihan →
Laporkan kepada Pihak Berwenang di Daerah Anda
Pilih negara Anda untuk mendapatkan kontak resmi kejahatan dunia maya, atau membuat draf pengaduan →.
Direktori 97 negara
Template-based draft · optional AI wording assistance requires separate consent
Draf yang dibantu AI — detail insiden diproses oleh penyedia AI · Tinjau dan kirimkan sendiri
Infrastruktur dan Laporan Terkait
Hubungan yang disimpan dikelompokkan berdasarkan atribut pencocokan tepat. Penyedia atau registrar bersama saja tidak membuktikan kepemilikan bersama.
Tautan langsung Menggunakan pendaftaran yang sama atau perangkat phishing yang identik.
Sinyal pendukung Berbagi infrastruktur atau merek sasaran; bukan bukti adanya satu operator.
Hanya untuk penemuan Terdaftar untuk navigasi; tidak ada atribut yang sama dengan host ini.
Peta infrastruktur · ledger-auth.com
Setiap jalur merupakan salah satu alasan mengapa sebuah domain terhubung ke host ini. Ukuran node menandai deteksi VirusTotal, sedangkan node bergaris putus-putus menunjukkan bahwa node tersebut sudah offline. Daftar lengkapnya tercantum di bawah ini.
Konten cocok4
Hash favicon yang sama atau judul halaman yang sama dengan host ini.
Laporan-laporan ini diselesaikan dengan IP edge bersama yang sama. Mereka membantu penemuan laporan tetapi tidak menyiratkan kepemilikan bersama atau server asal bersama.
Didaftarkan melalui penyedia layanan pendaftaran yang sama. Sebuah penyedia layanan pendaftaran melayani jutaan pelanggan yang tidak saling terkait, sehingga hal ini sekadar mengelompokkan laporan-laporan tersebut, bukan membuktikan adanya hubungan.
