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.
Detection-evasion evidence
Cloaking confirmed: scanners and visitors see different content
ObservedDifferent content was served to scanners and to visitors
The page served one response to a browser-like visitor and another to a crawler or security scanner. Cloaking exists only to keep reviewers away from the real landing page.
Stored cloaking flag
Observed
Cloaking type
status_split
Cloaking score
1/6
Last cloaking scan
Scanner note:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='bhapprise.digital', port=80): Max retries exceeded with url: / (Caused by NewConnectionErr
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='bhapprise.digital', port=80): Max retries exceeded with url: / (Caused by NewConnectionErr
checked Oct 11, 2026
Time to First Unavailability160 days
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedFeb 26, 2026
DOM Analysisanalyzed Jul 9, 2026score 71/100
ICANN OVERSIGHT
Accreditation and RAA context
Registrar accreditation and DNS abuse obligations
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 inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-11 01:11:43 UTC
RDAP registrationUnknown
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.
Technologies · 2 identified
Cloudflare
CDN
Web infrastructure and security company providing CDN, DDoS mitigation, and DNS services.
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
11 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
bhapprise.digital detected and queued for full analysis
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Mar 2, 2026
Time to First Unavailability
3841 hours elapsed from detection to the first unavailable observation.
How we investigate & report
Public scans, evidence and abuse channels
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
3 evidence signal groups linked0 reports recordedContent unavailable
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · bhapprise.digital
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Same registrar: Web Commerce Communica…6
Registered through the same registrar. A registrar serves millions of unrelated customers, so this groups reports rather than proving a link.
(MY)
