VirusTotal
6 / 91
This domain, coincommunity.community, is identified as a generic phishing threat targeting cryptocurrency users. Analysis indicates no direct association with known legitimate brands or drainer kits, but its infrastructure and behavioral patterns align with credential harvesting and wallet-draining campaigns. The domain presents a static 'Loading...' page title, a common tactic to mask malicious intent while awaiting victim interaction or evading automated detection systems. Infrastructure analysis reveals the following technical indicators: the domain was registered on June 22, 2026, through NICENIC INTERNATIONAL GROUP CO., LIMITED, a registrar frequently used for high-risk domains. It resolves to IP address 172.66.44.247, a Cloudflare-hosted endpoint often leveraged to obscure origin servers. VirusTotal detection shows 4 out of 95 security vendors flagging the domain as malicious, while it appears on 3 distinct security blocklists. The SSL certificate is issued by Google Trust Services (WE1), providing a superficial layer of legitimacy but failing to mitigate the underlying threat. Google Safe Browsing (GSB) status is not explicitly provided, but the domain's presence on multiple blocklists suggests active malicious classification. As of the latest assessment, coincommunity.community has been taken offline, reducing immediate exposure to end users. However, the domain remains registered and could be reactivated or repurposed for future campaigns. Response actions should include monitoring for re-emergence, updating blocklists, and alerting users who may have interacted with the domain prior to takedown. The residual risk remains elevated due to the domain's registration persistence and the registrar's history of hosting malicious infrastructure. Organizations are advised to maintain strict DNS filtering rules and educate users on recognizing phishing indicators, such as unexpected 'Loading...' page titles and mismatched SSL certificates.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
cloudflareScanner note: cloudflare_ban: raw=cf_phishing_block; http=403; via=https_proxy; server=cloudflare; provider_error=cloudflare_phishing_interstitial
Provider response during scan: cloudflare_phishing_interstitial
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 reputation is not attributed to this domain.
plato.ns.cloudflare.comprincess.ns.cloudflare.comLocation describes the IP network.
fe153f87a0d0b65302693b0c4fe5f07196e03ef1427683314eb812f4b9d3bf76Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
9 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive