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 indicates that the domain coinflare.global was registered on February 21, 2026 through NameSilo, LLC and is currently hosted behind Cloudflare’s network (AS13335). The authoritative nameservers ben.ns.cloudflare.com and sky.ns.cloudflare.com resolve the domain to IP address 104.21.12.140, which is located in the United States. The site is served over HTTPS using a certificate issued by Google Trust Services, and the HTTP response includes support for HTTP/3.
The public web page returns an HTTP 200 status but the HTML title reads “coinflare.global | 522: Connection timed out”, indicating that the origin server is intermittently unavailable or deliberately configured to present a timeout error. Email traffic is directed to Zoho mail servers (mx.zoho.com priority 10 and mx2.zoho.com priority 20), a pattern commonly observed in phishing campaigns that rely on third‑party mail services to receive victim credentials.
Threat intelligence shows the domain appears on one security blocklist and has been flagged by PhishDestroy. VirusTotal analysis recorded six positive detections out of ninety‑five scanners, reinforcing the suspicion of malicious activity. While the exact payload or credential‑harvesting pages are not presently observable due to the 522 condition, the combination of a recent registration, Cloudflare front‑end, legitimate‑looking SSL, and use of external mail services aligns with known credential‑harvesting operations.
Defenders should proactively block coinflare.global at the DNS and proxy layers, monitor for any outbound connections to the resolved IP address, and inspect email flows for messages originating from the listed Zoho MX hosts that reference the domain. Continuous re‑resolution of the domain is advised, as the underlying content may become active after the timeout condition resolves. Logging of TLS handshakes and HTTP/3 traffic can provide additional indicators if the site begins serving phishing pages.
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
content_divergence
Cloaking score
2/6
Last cloaking scan
Scanner note:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='coinflare.global', port=80): Max retries exceeded with url: / (Caused by NewConnectionErro
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='coinflare.global', port=80): Max retries exceeded with url: / (Caused by NewConnectionErro
checked Oct 13, 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 93/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-13 01:12:30 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-07-24 10:03:27 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-07-24 10:03:27 UTC → 2026-09-30 16:14:55 UTC · 1,638.19hmidpoint estimate ≈ 2026-08-27 13:09:11 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
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
Last analyzed Previous stored snapshot: 6 detections
ChainPatrol
alphaMountain.ai
Chong Lua Dao
Forcepoint ThreatSeeker
Fortinet
Gridinsoft
SOCRadar
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.
13 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
coinflare.global 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.
Feb 15, 2026
Time to First Unavailability
3840 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.
5 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 · coinflare.global
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
