The domain app.thorwsap.finance is currently active and classified as a high‑risk generic phishing site. It was registered on February 21, 2026 through Tucows Domains Inc. and resolves to the IPv4 address 23.254.225.127, which is allocated to AS54290 Hostwinds LLC in the Netherlands. The site returns HTTP status code 200 and does not present an SSL/TLS certificate, exposing all traffic in clear text.
Infrastructure analysis shows the domain is served by three Njalla‑controlled name servers: 1-you.njalla.no, 2-can.njalla.in, and 3-get.njalla.fo. The page title returned by the web server is identical to the domain name, "app.thorwsap.finance," offering no legitimate branding or user‑facing content. Absence of HTTPS combined with a generic title suggests the site is intended solely to host credential‑stealing forms or redirect victims to malicious payloads.
Threat intelligence indicates the domain appears on two independent security blocklists—PhishDestroy and ScamSniffer—demonstrating that multiple monitoring services have observed phishing activity associated with this host. VirusTotal analysis flags the domain by 15 of 95 security vendors, and Gridinsoft assigns a trust score of 0 out of 100, reinforcing the malicious assessment. No additional context such as phishing kit signatures or compromised credentials has been publicly disclosed.
Defenders should immediately block traffic to app.thorwsap.finance at perimeter and endpoint layers, and consider sinkholing the associated IP address to disrupt any ongoing credential collection. Continuous monitoring of DNS queries for the three Njalla name servers is advised, as changes may indicate redeployment of the phishing infrastructure. While the current evidence confirms phishing intent, the specific victim targeting and payload delivery mechanisms remain uncertain and warrant further investigation through sandbox or network traffic analysis should any connections be observed.
For the registrable domain thorwsap.finance 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.
Certificate fingerprintd8877f1bbbab22712439ecc947ddfa5803430be87f19ba6bef3d4b84559d83b2Certificate names · 1 SANs
thorwsap.finance
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationRedirectingHTTP redirect observed80%2026-10-20 10:02:20 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-20 10:02:20 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.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
地元の警察 — たとえ直ちに行動を起こせなくても、公式な記録が残される
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
詐欺による金銭の返還を装った詐欺 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
About this reportSources, observation dates and corrections
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.
(CA)
