The domain ledger.gl was observed on 2026-10-11 with entries on multiple external blocklists, as documented by MetaMask and SEAL. This assessment also notes its inclusion in internal listings and references to OTX intelligence pulses, providing a snapshot of its recorded status.
Recorded Evidence
MetaMask and SEAL both listed ledger.gl on their blocklists as of 2026-10-11. The domain was registered with Gname.com Pte. Ltd. on 2026-10-01 and received an SSL certificate from Let's Encrypt / YE1, scanned on 2026-10-11. OTX documented four pulses referencing ledger.gl on 2026-10-11, and PhishDestroy internally listed the domain on the same date.
Interpretation
PhishDestroy contains an internal listing for ledger.gl, recording its evaluation based on observed criteria. OTX provides a measurement of intelligence activity through its four documented pulses. The scope of these observations covers both external blocklist entries and internal intelligence, offering a multi-source snapshot of ledger.gl's recorded profile on 2026-10-11.
Recommended Actions
For ledger.gl, preserve the blocklist entries from MetaMask and SEAL for future comparison. Retain the OTX pulse records and PhishDestroy internal listing as reference points for ongoing monitoring. Review all source observations periodically to track any changes in recorded status or listings.
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 08:28:48 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 08:28:48 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.
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.
Threat First Observed2026-10-11 08:28:48 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 188.114.97.3.
脅威対応 Pipeline
ディスカバリー
Analysis
Monitoring
8 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
(DE)
