VirusTotal
16 / 91 engine detections
レポートを開く“Sophie'S Hostel Prague - Prague, Czech Republic”
フィッシング: sophies.hostel.town — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 16/91 (alphaMountain.ai, BitDefender, CRDF, ESET, Forcepoint ThreatSeeker); CF…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
16 / 91 engine detections
レポートを開く悪意あり
レポートを開くno community references
レポートを開くNo threat flag
レポートを開くNo malicious flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
sophies.hostel.town presents itself as the website of Sophie's Hostel Prague, using the page title "Sophie'S Hostel Prague - Prague, Czech Republic". PhishDestroy classifies it as an impersonation phishing page aimed at travellers looking to book accommodation in Prague. We first detected it on 2026-09-29. The site was still online and serving its content when last checked on 2026-10-19.
Fake accommodation sites copy the name and look of a real property so that a guest searching for it lands on the fraudster's page instead. The visitor is then pushed to secure a room by entering card details or paying a deposit directly, often by bank transfer or another hard-to-reverse method. The victim loses the payment, has no reservation, and may hand over card data and personal details that can be reused for further fraud. The odd capitalisation in the title, "Sophie'S", is the kind of small error copied pages often carry.
On 2026-10-01, 16 of 91 VirusTotal engines flagged the domain as malicious. The vendors flagging it include alphaMountain.ai, BitDefender, CRDF, ESET, Forcepoint ThreatSeeker, Fortinet, G-Data and Gridinsoft. Because these are independent vendors with separate detection pipelines, their agreement supports the classification. The domain is on the PhishDestroy blocklist.
The domain was registered on 2026-04-21 through Spaceship, Inc., about five months before we detected it. That gap suggests it was set up well in advance or ran unnoticed for a while. It resolves to an address on the RouterHosting LLC network in the United States, which has no obvious link to a Prague hostel. The site uses a free domain-validated certificate from ZeroSSL, so the browser padlock only confirms an encrypted connection and says nothing about who runs the site.
If you entered card details or paid a deposit on this site, contact your bank or card issuer at once to block the card and dispute the charge. Then reach the real hostel through an independent channel or a trusted booking platform to check whether any booking exists. If you created an account there and reused that password elsewhere, change it and turn on two-factor authentication. Be alert for follow-up emails or calls that use your details. Defenders and booking platforms should block the domain and report it to the hosting network and registrar so it can be taken down.
For the registrable domain hostel.town 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.
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.
launch2.spaceship.netLocation describes the IP network.
be7695375cb6c7ca5a2ee3b931d7060dd0e5efaf68a763b04b02f811b24b86afhostel.townSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of sophies.hostel.town · checked Sep 29, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
redirected→live_content
content_served
live_content→redirected
http_redirect
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
15→16
16→15
No threat flag
View source16/91 engine detections
View sourcesophies.hostel.town
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
sophies.hostel.town
Listed domains receive at least one abuse report; this entry has no retained notification history.
アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
sophies.hostel.town)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
保存されたブロックリスト、WHOIS、DNS、および公開スキャン証拠を使用した脅威分析
今すぐスキャン不審なドメインを当社の脅威データベースに報告してください — コミュニティを守りましょう
レポート最近のフィッシングレポートと観察された可用性の変化
監視リアルタイムの脅威を監視するか、誤検知だと思われる場合はこのリストに異議を申し立ててください
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.