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.
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='bhapprise.digital', port=80): Max retries exceeded with url: / (Caused by NewConnectionErr
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.
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-19 01:11:11 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-07-09 10:42:12 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-07-09 10:42:12 UTC → 2026-09-30 16:14:55 UTC · 1,997.55hmidpoint estimate ≈ 2026-08-20 01:28:33 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
Cloudflare
CDN
Web infrastructure and security company providing CDN, DDoS mitigation, and DNS services.
Template-based draft · optional AI wording assistance requires separate consent
AI辅助草稿——事件详细信息由AI提供商处理 · 自行审核并提交
After a phishing incident
针对受害者的建议与指导
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.
更改所有密码 — 电子邮件、Exchange 账户，以及任何使用同一密码的账户
启用双因素认证 使用身份验证器应用（而非短信）。禁用基于短信的恢复功能
冻结卡片 如果您在钓鱼网站上输入了银行信息
我应该为报告收集哪些信息？
联邦调查局（FBI）指南
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.
How do phishing scams typically work?
虚假网站 — 与正规网站完全一致的克隆网站，仅域名略有改动
猪的屠宰 — 通过Telegram/WhatsApp/交友软件花数周时间建立信任，随后钱被骗走
退款诈骗 — 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.
(MY)
