Stored registration data identifies NameSilo as the registrar. PhishDestroy maintains separate registrar investigations; that broader material is contextual and is not an independent detection for this domain.
The domain hodlwallet.org was referenced in the PhishDestroy internal listing as of 2026-10-13, providing a dated record for security assessment. Another notable fact is that the domain was registered with NameSilo, LLC on 2026-09-28.
Recorded Evidence
On 2026-10-13, VirusTotal checked hodlwallet.org and recorded 0 detections out of 92 total scanners. The same date, OTX referenced four pulses associated with the domain. PhishDestroy listed hodlwallet.org in its internal catalogue on 2026-10-13. The domain’s registrar was recorded as NameSilo, LLC, with registration dated 2026-09-28.
Interpretation
PhishDestroy contains a listing for hodlwallet.org, which documents its presence in a security-focused internal catalogue. VirusTotal provides a measurement of the domain’s detection status across a wide range of security scanners, while OTX records the number of pulses as an indicator of external security intelligence activity. These sources each capture different facets of the domain’s technical and security profile, offering multiple dated perspectives.
Recommended Actions
For hodlwallet.org, preserve the VirusTotal, OTX, and PhishDestroy records for future reference and comparison. Review the internal listing status and pulse activity as part of ongoing monitoring. Use the recorded scanner results to inform periodic checks and maintain an updated evidence base for hodlwallet.org.
Latest HTTP observation未知Probe Inconclusive20%2026-10-13 14:17:12 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-13 14:17:12 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.
Google PageSpeed Insights — mobile performance audit of hodlwallet.org· checked Oct 13, 2026
60
Needs Work
Performance
FCP
6s
First Contentful Paint
LCP
6.98s
Largest Contentful Paint
CLS
0.008
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
7.36s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Stored Capture Evidence 1 snapshot
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
Archived HTTP responseHTTP 200
Requested URL:https://hodlwallet.org/
HODL CRYPTO WALLET — Your crypto. A wider perspective.
Explore the HODL desktop workspace: portfolios, crypto networks, tokens, stablecoins, collectibles and transaction activity in one considered interface.
响应 HTTP 200
HTML body 62.4 KB
Compressed 14.0 KB
Links 79 internal · 1 external
Detected technologies
bootstrapapachereact
Selected response headers
Server: Apache
Content-Encoding: gzip
Cache-Control: no-cache
Content-Type: text/html; charset=UTF-8
Security headers present
X-Content-Type-OptionsReferrer-Policy
HSTS: not observedDNSSEC: not observedWAF / firewall: not observedCloaking flag: not observed
Open Graph title:HODL CRYPTO WALLET — Your crypto. A wider perspective.
Open Graph description:Explore the HODL desktop workspace: portfolios, crypto networks, tokens, stablecoins, collectibles and transaction activity in one considered interface.
Twitter card:summary_large_image
Saved response-header values · 13
Accept-Ranges
bytes
Cache-Control
no-cache
Connection
Keep-Alive
Content-Encoding
gzip
Content-Length
14414
Content-Type
text/html; charset=UTF-8
Date
Tue, 13 Oct 2026 14:15:41 GMT
Keep-Alive
timeout=5, max=100
Last-Modified
Wed, 23 Sep 2026 14:21:22 GMT
Referrer-Policy
strict-origin-when-cross-origin
Server
Apache
Vary
Accept-Encoding
X-Content-Type-Options
nosniff
Values retained by the collector; long values may be shortened during collection.
Crawler & disclosure files
Site configuration evidence
2 recorded files
Files, paths and sitemap entries retained by the collector.
robots.txt
Reachable (legacy)/robots.txt
HTTP response
200
Observed at
2026-10-13 16:15:43 UTC
来源
legacy scan archive
A legacy scan recorded a successful response. The file contents were not retained.
Sitemap
Reachable (legacy)/sitemap.xml
HTTP response
200
Observed at
2026-10-13 16:15:43 UTC
来源
legacy scan archive
A legacy scan recorded a successful response. The file contents were not retained.
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.
Threat First Observed2026-10-13 14:17:12 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 146.70.24.201.
威胁响应 Pipeline
发现
Analysis
Notifications
Monitoring
8 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.
OTX Community References
4 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
2026年10月13日
Registrar Context: NameSilo
Separate registrar research is available. Registrar association is contextual and is not scored as an independent detection.
Forensic Evidence Collected
Stored evidence from URLScan.io, URLQuery, stored screenshot
2026年10月13日
Sent Report Recorded
Stored outgoing record associated with registrar NameSilo, LLC, 2 abuse contacts
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 (856 chars)
Abuse notice text as sent to the provider
AUP & Terms of Service Violations:
Acceptable Use Policy: Active phishing operations targeting internet users directly violate standard AUP provisions prohibiting fraud and deceptive practices.
Terms of Service: Material breach of service terms regarding malicious use, providing contractual justification for immediate suspension.
Applicable Legal Framework (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.
Investigation Notice: We fully respect your internal investigation processes and discretion. Prompt remediation protects innocent users while mitigating regulatory compliance scrutiny, legal liability, and brand reputation risks associated with ongoing malicious infrastructure.
(US)
PhishDestroy Investigation
