VirusTotal
3 / 95 engine detections
レポートを開く“bhapprise.digital | 521: Web server is down”
ブロックリスト掲載ドメイン: bhapprise.digital — コンテンツが利用できません. 証拠の概要: VirusTotal 3/95 (Fortinet, Gridinsoft, SOCRadar); cloaking observed; PhishDestroy score 71/100.…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
3 / 95 engine detections
レポートを開くno community references
レポートを開くprovider verdict: clean
レポートを開く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
Analysis shows bhapprise.digital was registered on February 21, 2026 and is currently hosted behind Cloudflare’s network (AS13335). The domain resolves to IP 104.21.52.98, utilizes HTTP/3, and presents a valid SSL certificate issued by Google Trust Services under the WE1 label. Nameserver delegation to naomi.ns.cloudflare.com and denver.ns.cloudflare.com confirms the use of Cloudflare’s DNS infrastructure. The site returns an HTTP 200 response, but the page title reports a “521: Web server is down” error, indicating a possible misconfiguration or intentional denial of service to obscure content.
Threat intelligence flags bhapprise.digital as a generic_phishing actor. The domain appears on one security blocklist and is actively blocked by PhishDestroy. VirusTotal analysis records three of ninety‑five scanners flagging the domain, reinforcing the suspicion of malicious intent. The low Gridinsoft trust score of 0 / 100 further underscores the poor reputation associated with the domain.
Uncertainty remains regarding the exact phishing payload or target audience, as no page content has been captured beyond the title. The presence of a valid TLS certificate and Cloudflare front‑end may be employed to lend credibility to phishing emails or messages that reference the domain. Additionally, the “521” error could be a tactic to evade automated crawlers while still serving malicious content to specific victims.
Defenders should block outbound connections to 104.21.52.98 and add bhapprise.digital to domain deny lists across email gateways, web proxies, and endpoint protection platforms. Continuous monitoring of DNS queries for this domain is advised, as any sudden change in resolution or additional IP addresses could signal scaling of the campaign. Organizations using threat‑intel feeds should ensure the domain remains flagged in their security blocks, and incident response teams should be prepared to investigate any user reports involving links to bhapprise.digital.
For this gTLD, 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.
Edge-IP の評判はこのドメインに起因しません。
denver.ns.cloudflare.comLocation describes the IP network.
52f122503781a45e26fddd77f5f7562344ee5be39be898c5f600a224a139f136Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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.
status_split · unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='bhapprise.digital', port=80): Max retries exceeded with url: / (Caused by NewConnectionErr
bhapprise.digital
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
https://radar.cloudflare.com/scan/15a382e5-7f17-4627-b5f8-55a9c7832f38
https://radar.cloudflare.com/scan/15a382e5-7f17-4627-b5f8-55a9c7832f38
No threat flag
View sourcebhapprise.digital
View source3/95 engine detections
View sourceコミュニティの 1 人が報告・初回確認 2025年12月12日
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 ↗
bhapprise.digital)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.