VirusTotal
12 / 91
“Un instant…”
The domain proposal-jumper.exchange was registered on February 21, 2026 through NiceNIC International Group Co., Limited. It resolves to the Cloudflare edge address 188.114.97.3, which is announced by AS13335 and geolocated to the United States. The authoritative nameservers are adam.ns.cloudflare.com and danica.ns.cloudflare.com, confirming the use of Cloudflare’s DNS and CDN services. The site presents an SSL certificate issued by Google Trust Services under the WE1 trust chain, indicating a valid TLS handshake despite the underlying malicious purpose.
HTTP requests return a 403 status code, and the page title captured by crawlers is "Un instant…", offering no additional context about the content. Technical fingerprints include Cloudflare and HTTP/3 support. The domain has been flagged by multiple defensive feeds: PhishDestroy, MetaMask, and SEAL have listed it as blocked, and it appears on three public blocklists. VirusTotal analysis shows three out of ninety‑five security vendors flag the domain, reinforcing the suspicion of malicious activity.
The identified scam type is a "Fake Exchange" operation, suggesting the site attempts to impersonate a cryptocurrency or financial exchange to harvest credentials. Current operational status is offline, but the infrastructure remains registered and could be re‑activated. Defenders should continue to block the domain at network perimeter and DNS layers, monitor for any re‑hosting on alternative IP ranges, and update endpoint protection signatures to include the observed indicators. Further investigation is needed to capture the exact landing page content and any associated payloads, as the present data set does not reveal the specific phishing flow or victim interaction mechanisms.
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.
danica.ns.cloudflare.comLocation describes the IP network.
1d53bf2a7238a53c3cf9b5b427318c0d3961cddfd1f72dccd92416a3a7a2b065Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
13 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 Feb 12, 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