VirusTotal
3 / 91
“Home | Meteora”
The domain meteora.markets is presently active and has been classified as a generic phishing site. As of the report date, July 25, 2026, DNS resolution points to the IPv4 address 188.114.96.3, which belongs to AS13335 (Cloudflare, Inc.) and is geolocated in the United States. Authoritative nameservers listed are marek.ns.cloudflare.com and poppy.ns.cloudflare.com, confirming that the domain is hosted behind Cloudflare’s edge network. The web service presents an HTTPS endpoint secured by a certificate issued by Google Trust Services under the WE1 label, indicating a valid TLS chain. The HTTP response code returned by the server is 521, a Cloudflare‑specific status that denotes the origin server is refusing connections, which may be used to obscure backend activity.
Detected technologies include Cloudflare’s CDN and HTTP/3 support, both typical of modern hosting but not indicative of benign intent. VirusTotal analysis shows that 6 of 95 security vendors have flagged the domain, suggesting a moderate level of consensus about malicious behavior. The site appears on a single security blocklist and has been explicitly blocked by the PhishDestroy feed. Independent reputation scoring from Gridinsoft assigns a trust score of 0 out of 100, reinforcing the assessment of high risk.
The page title returned by the server is "Home | Meteora," but no further content has been harvested, leaving the exact phishing payload or credential‑ harvesting mechanisms unknown. Given the combination of Cloudflare‑based hosting, a low trust score, multiple vendor detections, and active blocklist listings, defenders should treat meteora.markets as malicious. Recommended mitigations include adding the domain to outbound allow‑list exclusions, updating intrusion‑prevention signatures to drop traffic to 188.114.96.3, and monitoring DNS logs for queries to the associated nameservers.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
nginxScanner note: terminal_unconfirmed: candidate_reason=hosting_placeholder; raw=placeholder; http=200; via=https_direct; server=nginx
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.
marek.ns.cloudflare.compoppy.ns.cloudflare.comLocation describes the IP network.
64d4a0d4d2b29d8c64023a9206cb2cf73258c92c920e0b5d0d1e3055ed2e4016Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
14 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 Oct 29, 2025
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