ledgerwalletrepair.com returned an HTTP status of 200 when checked on 2026-10-07, indicating a successful connection at that time. Google Safe Browsing flagged this domain for social engineering threats on the same date, providing a specific security assessment.
Recorded Evidence
On 2026-10-07, the domain ledgerwalletrepair.com was internally listed by Phishdestroy. Google Safe Browsing flagged the domain for social engineering threats when checked on 2026-10-07. An external blocklist, Phishunt, also listed the domain as of 2026-10-07. VirusTotal reported 19 detections out of 92 total scanners on 2026-10-06. OTX recorded 2 pulses for the domain on 2026-10-07. The domain was first observed on 2026-10-06, and its registration date is 2025-08-29 with registrar OwnRegistrar, Inc. An SSL certificate from Let's Encrypt / YE2 was scanned on 2026-10-07.
Interpretation
The Google Safe Browsing flag for social engineering threats and the Phishunt blocklist entry indicate specific concerns identified by these services. The internal Phishdestroy listing further highlights a detection within a proprietary system. The VirusTotal detections provide a broad view of how various security scanners assessed the domain. OTX pulses suggest additional community observations related to the domain's activity.
Recommended Actions
Preserve the Google Safe Browsing flag and the Phishunt blocklist entry for ledgerwalletrepair.com as reference points. Compare future VirusTotal detection counts and OTX pulse observations against the recorded values. Regularly monitor the Phishdestroy internal listing and the HTTP status code for ledgerwalletrepair.com for any changes.
Analisi di rilevamento ed evasione
Verifica del cloaking e della distribuzione del traffico
Non ancora scansionatoNon è stata ancora rilevata alcuna differenza tra crawler e browser
Osservazioni archiviate relative al confronto tra crawler e browser per questo host, oltre a una verifica in tempo reale delle impronte digitali per i sistemi di distribuzione del traffico in stile Keitaro.
Flag di occultamento memorizzato
Non ancora scansionato
Ultima scansione di occultamento
Nota dello scanner:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='ledgerwalletrepair.com', port=80): Max retries exceeded with url: / (Caused by NewConnecti
Verifica delle impronte digitali in tempo reale TDS
Sette impronte digitali di Keitaro più un confronto tra crawler e browser, eseguiti dallo scanner PhishDestroy quando questa finestra è aperta.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS inattivoreason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationSconosciutoProbe Inconclusive20%2026-10-11 10:08:10 UTC
RDAP registrationSconosciuto
Observed timelinelast reachable: 2026-10-08 22:00:47 UTClast content: 2026-10-08 22:00:47 UTCcurrent episode first observed: 2026-10-09 20:20:42 UTCobserved RIP window: 2026-10-08 22:00:47 UTC → 2026-10-09 20:20:42 UTC · 22.33hmidpoint estimate ≈ 2026-10-09 09:10:44 UTC · precision medium · 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.
Last analyzed Previous stored snapshot: 19 detections
alphaMountain.ai
Bfore.Ai PreCrime
BitDefender
Chong Lua Dao
CyRadar
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
G-Data
Google Safe Browsing
Gridinsoft
Kaspersky
Lionic
Seclookup
SOCRadar
Sophos
VIPRE
Webroot
Analisi delle prestazioni del sito
Google PageSpeed Insights — mobile performance audit of ledgerwalletrepair.com· checked Oct 6, 2026
97
Good
Performance
FCP
0.78s
First Contentful Paint
LCP
2.56s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
1.46s
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.
Status Check2026-10-06 21:12:13 UTC
Telemetry event observed.
Threat First Observed2026-10-06 21:11:47 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 172.233.211.67.
Pipeline di risposta alle minacce
Scoperta
Analysis
Monitoring
12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Minaccia rilevata
ledgerwalletrepair.com rilevati e inseriti in coda per un’analisi completa
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.
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.
4 evidence signal groups linked0 reports recordedNon verificato
If credentials were compromised, report immediately. Do not engage with recovery scammers.
Se hai inserito credenziali dell'account, informazioni personali o di pagamento oppure hai scaricato un file da questo dominio, agisci immediatamente. Di seguito sono riportate le risorse per aiutarti a segnalare l'incidente e proteggerti.
Attenzione ai truffatori che promettono il recupero dei fondi! I criminali possono contattare nuovamente le vittime fingendo di essere investigatori, avvocati o agenti di recupero. Non pagare commissioni anticipate né condividere credenziali.Scopri di più sulle frodi relative ai sussidi di recupero →
Template-based draft · optional AI wording assistance requires separate consent
Bozza assistita dall'intelligenza artificiale: i dettagli dell'incidente vengono elaborati dal fornitore di intelligenza artificiale · Controllalo e invialo tu stesso
Infrastruttura e rapporti correlati
Le relazioni archiviate sono raggruppate in base all'attributo di corrispondenza esatta. Un fornitore o un registrar condiviso da solo non dimostra la proprietà comune.
Link diretto Condivide una registrazione o un kit di phishing identico.
Segnale di supporto Condivide l'infrastruttura o un marchio di riferimento; non costituisce prova della presenza di un unico operatore.
Solo per la scoperta Elencato ai fini della navigazione; nessun attributo in comune con questo host.
Mappa delle infrastrutture · ledgerwalletrepair.com
Ogni riga rappresenta un motivo per cui un dominio è collegato a questo host. I nodi a dimensione intera indicano rilevamenti di VirusTotal, mentre quelli tratteggiati sono già offline. Di seguito è riportato l'elenco completo.
Risultati corrispondenti8
Stesso hash della favicon o stesso titolo della pagina di questo host.
Questi report si risolvono nello stesso IP edge condiviso. Aiutano con l'individuazione dei report ma non implicano la proprietà comune o un server di origine condiviso.
Registrati tramite lo stesso registrar. Un registrar serve milioni di clienti non collegati tra loro, quindi questo dato indica semplicemente un raggruppamento piuttosto che dimostrare un nesso.
(US)
