VirusTotal
6 / 89
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| OpenDNS | bullcoin.digital |
phishing | Phishing Block |
| Hagezi Threat Feed | bullcoin.digital |
malicious | Sinkholed |
| DNS4EU | bullcoin.digital |
malicious | Sinkholed |
The domain bullcoin.digital has been identified as a high‑risk generic phishing infrastructure. It was registered on 21 April 2026 through NICENIC INTERNATIONAL GROUP CO., LIMITED and is currently active. The short lifespan combined with the rapid appearance on security feeds suggests a focused campaign rather than a long‑standing malicious site. The site is served behind Cloudflare, resolving to the IP address 188.114.97.3, which is listed as a Cloudflare, Inc. location in Canada. DNS resolution uses the Cloudflare authoritative nameservers june.ns.cloudflare.com and nikon.ns.cloudflare.com. A Let's Encrypt certificate (issuer E8) is present, providing a valid TLS handshake despite the malicious intent. Open Threat Exchange (OTX) records show the domain in a single threat pulse, and it is listed on one external security blocklist. PhishDestroy has also blocked the domain, and VirusTotal reports a single vendor detection out of 95 scans, indicating that at least one security engine has observed malicious behavior. HTTP requests to the host return a 403 status, which may be a defensive response or part of the phishing page delivery mechanism. Defenders should immediately add bullcoin.digital to outbound filtering rules and ensure internal DNS resolvers block the domain. Network monitoring should watch for traffic to 188.114.97.3, especially TLS connections that present the Let's Encrypt certificate. Email security gateways should be updated to flag any messages containing references to “bullcoin” or the domain itself, and incident response teams should be prepared to investigate credential‑theft attempts that may be tied to this infrastructure.
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.
status_splitcloudflareScanner note: cloudflare_challenge: raw=cf_challenge; http=403; via=https_proxy; server=cloudflare
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.
nikon.ns.cloudflare.comLocation describes the IP network.
c9f095db5ad7a05d215e96142181d420a64eb23ae0c99a3ce573fa6fb0775182Saved 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.
Reported by 1 community member, first seen Apr 21, 2026
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