Stored registration data identifies NameSilo as the registrar. PhishDestroy maintains separate registrar investigations; that broader material is contextual and is not an independent detection for this domain.
Analysis of playhubai.network indicates active brand impersonation targeting Cloudflare, with infrastructure and detection patterns consistent with phishing activity. The domain was registered on February 21, 2026, through NameSilo, LLC, and currently resolves to 104.21.4.132, an IP address hosted on Cloudflare's network (AS13335). While the domain uses Cloudflare nameservers (aria.ns.cloudflare.com, patryk.ns.cloudflare.com), this does not confirm legitimacy, as threat actors frequently abuse Cloudflare's infrastructure for obfuscation. The HTTP status returns 200, and the page title 'Just a moment...' suggests a Cloudflare challenge or proxy page, though the exact content remains unanalyzed. MX records point to _dc-mx.69912a83b510.playhubai.network, which may indicate email-based attack vectors, though no specific campaign details are available.
Detection data shows the domain is flagged by one security vendor (PhishDestroy) and appears on a single blocklist. Gridinsoft assigns a trust score of 0/100, reinforcing its high-risk classification. VirusTotal reports one detection out of 93 vendors, though this does not rule out false negatives or delayed scans. The SSL certificate is issued by Google Trust Services (WE1), a common certificate authority for both legitimate and malicious domains. Technologies detected include Cloudflare Browser Insights and HTTP/3, further aligning with Cloudflare's ecosystem but providing no definitive proof of intent.
Defenders should treat this domain as high-risk due to its brand impersonation classification, active status, and detection by security vendors. Blocking the domain and its associated IP (104.21.4.132) is recommended, along with monitoring for related subdomains or MX record activity. The lack of widespread detection does not indicate safety; further investigation into email campaigns or user reports may reveal additional indicators.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not observedNo cloaking was observed in the stored scan
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Stored cloaking flag
Not observed
Cloaking score
0/6
Last cloaking scan
Scanner note:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='playhubai.network', 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.
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 Apr 10, 2026score 15/1001 brand signal
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:12:41 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-08-29 22:15:40 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-08-29 22:15:40 UTC → 2026-09-30 16:14:55 UTC · 761.99hmidpoint estimate ≈ 2026-09-14 19:15:17 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 · 3 identified
Cloudflare Browser Insights
AnalyticsRUM
Performance monitoring tool that measures website speed from real users.
Last analyzed Previous stored snapshot: 1 detection
ADMINUSLabs
alphaMountain.ai
Bfore.Ai PreCrime
BitDefender
Chong Lua Dao
Fortinet
G-Data
Gridinsoft
Lionic
Sophos
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
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.
15 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
playhubai.network 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.
Jun 6, 2026
Time to First Unavailability
92 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 · playhubai.network
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.
(US)
PhishDestroy Investigation
