VirusTotal
5 / 89 engine detections
レポートを開く“Suspected Phishing | Cloudflare”
Cloudflareなりすまし: booking.jh-print.com — コンテンツが利用できません. 証拠の概要: VirusTotal 5/89 (alphaMountain.ai, CRDF, Gridinsoft, SOCRadar, Webroot); URLQuery 2 alerts; CF…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
5 / 89 engine detections
レポートを開く2 threat-system alerts
レポートを開く悪意あり
レポートを開く15/100
レポートを開く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
booking.jh-print.com is an impersonation phishing page that dressed itself in Cloudflare branding. It targets internet users who are used to Cloudflare screens and people with Cloudflare accounts. PhishDestroy first flagged it on 2026-09-12. The site went offline on 2026-09-13, its DNS no longer resolved when last checked on 2026-10-19, and it is currently dead.
The page carried the title "Suspected Phishing | Cloudflare," which copies the wording of Cloudflare's own warning screen, while we classified the site itself as an impersonation phishing page. Pages that copy Cloudflare usually rely on the brand's familiar challenge and warning screens to look routine. Behind that look, they ask visitors to sign in, "verify" themselves, or follow instructions that hand over account credentials or run something on the victim's machine. A stolen Cloudflare login is especially damaging because it can give an attacker control over DNS, SSL and traffic for every domain on that account.
Five of 89 VirusTotal engines flagged the site on 2026-09-13: alphaMountain.ai, CRDF, Gridinsoft, SOCRadar and Webroot. That is a modest count, but it comes from several unrelated vendors within a day of our first sighting, which supports the classification. Among public blocklists, only PhishDestroy lists the domain, so many browsers and filters may not have warned visitors while the page was live.
The page sat on a "booking" subdomain of jh-print.com. That parent domain was registered on 2010-10-20 through Gname.com Pte. Ltd., nearly sixteen years before the phishing page appeared. The operation borrowed an established name rather than registering a fresh lookalike, which helps it slip past filters that score domains by age. Traffic ran through Cloudflare's own network in the US, and the certificate came from Google Trust Services (WE1), a standard issuer for Cloudflare-proxied sites. So the hosting reveals nothing about the operator beyond the fact that it sat behind the brand it was copying.
If you entered a Cloudflare email and password on this page, change the password from the official dashboard right away and enable or reset two-factor authentication. Then review your account's active sessions, API tokens and recent DNS or SSL changes. Change the password on any other service that shared those credentials. If the page told you to download a file or paste a command, scan that device and treat stored passwords on it as exposed. Defenders should block the hostname and alert users that genuine Cloudflare warning screens never ask for logins. Whoever owns jh-print.com should also audit its DNS records for subdomains it did not create.
Edge-IP の評判はこのドメインに起因しません。
ashley.ns.cloudflare.comrazvan.ns.cloudflare.comLocation describes the IP network.
25b7a789a02ee2a31f1de5d9a7fbe556669637207d00c1ea67ec10859a7d569ajh-print.comSaved 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 booking.jh-print.com · checked Sep 12, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
booking.jh-print.com
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
利用不可→到達可能
到達可能→利用不可
到達可能
No threat flag
View source5/89 engine detections
View sourcePD-20260912-560AAE
booking.jh-print.com
View sourcePage captured
View source保存された類似ドメイン:142 件
142 件中 100 件を表示
PD-20260912-560AAE Recipient: complaint@gname.com Registrar: Gname.com Pte. Ltd. (Singapore) Policy Violations: Illegal Activities section forbids phishing, fraud, fake sites, malware distribution; registrar investigates and may suspend or delete domain Applicable Laws: Computer Misuse Act 1993 §§3+, Penal Code §§415–420 (cheating), Online Criminal Harms Act (OCHA)
アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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 ↗
booking.jh-print.com)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.