VirusTotal
8 / 91
“stonks.fun | 502: Bad gateway”
On 2026-10-01, stonks.fun returned an HTTP status 301 during a recorded check, indicating a redirect response to a request on that date. The same source data records a first observation of the domain on 2026-09-29, giving the earliest date present in the supplied records.
The domain stonks.fun was first observed on 2026-09-29. An HTTP check on 2026-10-01 recorded status 301. VirusTotal, checked on 2026-10-01, reported 8 detections across 91 scanners. OTX, checked on 2026-10-01, listed 3 pulses. The PhishDestroy internal listing was recorded, and the blocklist check occurred on 2026-10-01. Registration was recorded on 2026-07-03 with registrar Porkbun LLC. The SSL certificate, scanned on 2026-09-29, was issued by Google Trust Services / WE1.
The HTTP 301 response describes only the outcome recorded on 2026-10-01 and does not describe all content that may be served by stonks.fun. VirusTotal detections and OTX pulses are separate metrics gathered by different sources, so they should be read as distinct records rather than combined. The first observation and the HTTP check fall on different dates, and those dates alone do not establish a trend or change. The PhishDestroy internal listing is a separate catalogue entry from the VirusTotal and OTX records.
Preserve the HTTP response record for stonks.fun as a reference for future checks. Keep the VirusTotal entry and the OTX pulses as separate source records for comparison. Retain the PhishDestroy internal listing alongside the other observations. Avoid submitting sensitive information to stonks.fun while these records remain the basis for review.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
cloudflareScanner note: redirect: raw=redirect_301; http=301; via=http_proxy; location=https://stonks.fun/; 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.
Location describes the IP network.
a96004a40d9864289cd73059e3a522b5d3c8262e922d018b325cded2084cf5ddSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
104.21.16.234. 11 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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