Analysis of basewallet.walletverificationservice.online confirms its classification as a crypto drainer phishing domain, currently offline as of July 24, 2026. The domain was registered on November 27, 2025, through HOSTINGER operations, UAB, and resolves to IP address 92.113.23.173, hosted on AS47583 (Hostinger International Limited) in Germany. Nameservers ns1.dns-parking.com and ns2.dns-parking.com were in use, alongside Hostinger CDN and HTTP/3 protocol support. The SSL certificate was issued by Let's Encrypt (R13), a common choice for both legitimate and malicious infrastructure.
At the time of assessment, the domain returned an HTTP 403 Forbidden status, with no further page content accessible for analysis. Nine of ninety-five security vendors on VirusTotal flagged the domain, and it appears on at least one security blocklist, including PhishDestroy. Gridinsoft assigned a trust score of 0/100, reinforcing its malicious classification. The domain is explicitly categorized as a crypto scam, aligning with known crypto drainer tactics used to siphon digital assets from compromised wallets.
While the domain is no longer active, defenders should treat it as confirmed malicious infrastructure. Historical DNS and WHOIS records should be preserved for forensic purposes, and any residual DNS resolutions or SSL certificate associations should be monitored. Network defenders are advised to block traffic to 92.113.23.173 and the domain itself, and to review logs for prior connections from internal systems. Given the use of Hostinger CDN and Let's Encrypt, similar domains leveraging these services should be scrutinized for potential abuse.
For the registrable domain walletverificationservice.online behind this subdomain, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS 非アクティブreason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation不明Probe Inconclusive20%2026-10-11 01:12:18 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-06-15 22:13:15 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-06-15 22:13:15 UTC → 2026-09-30 16:14:55 UTC · 2,562.03hmidpoint estimate ≈ 2026-08-08 07:14:05 UTC · precision very 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.
使用技術 · 2 identified
H
Hostinger CDN
H
HTTP/3
Miscellaneous
Third major version of HTTP protocol, built on QUIC for faster, more reliable connections.
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.
13 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.
Web Archive
Preserved in ウェイバック・マシン — historical evidence archived
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.
(LT)
