jurnper.exchange was observed with a VirusTotal detection record on 2026-10-13, documenting its presence in security monitoring sources. The domain was also included on two external blocklists as of 2026-10-14.
Recorded Evidence
VirusTotal recorded 4 detections out of 92 scanners for jurnper.exchange on 2026-10-13. On 2026-10-14, the domain appeared on the MetaMask and SEAL external blocklists. OTX included jurnper.exchange in 3 separate pulses on 2026-10-14. PhishDestroy internally listed the domain, and a PageSpeed performance score of 97 was documented on 2026-10-14. The registrar was recorded as Dynadot Inc, with a registration date of 2026-10-07.
Interpretation
The VirusTotal record contains a technical measurement by multiple security scanners, documenting the detection results for jurnper.exchange. OTX records its inclusion in several intelligence pulses, which are groupings of related security data. Presence on the MetaMask and SEAL blocklists provides additional context on how external sources have referenced the domain. These sources together capture a range of security-related observations within a short period.
Recommended Actions
For further review of jurnper.exchange, preserve the VirusTotal detection record and the OTX pulse entries for future comparison. Retain the MetaMask and SEAL blocklist records as external reference points. Keep the PhishDestroy internal listing and the PageSpeed performance score as supporting technical evidence in subsequent assessments.
注册信息创建 2026年10月7日 (7d · Very New!)—Expires 2027年10月7日
技术详情Provenance & timestamps
首次发现2026年10月14日
Submitted URLhttp://jurnper.exchange/
Favicon Hash
案件 ID
ICANN OVERSIGHT
认证和 RAA 背景
Registrar accreditation and DNS abuse obligations
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.
Accreditation is a contract, not a safety certification.
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.
Latest HTTP observation未知Probe Inconclusive20%2026-10-14 19:37:07 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-14 19:37:07 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Last analyzed Previous stored snapshot: 4 detections
ChainPatrol
alphaMountain.ai
Forcepoint ThreatSeeker
Fortinet
网站性能分析
Google PageSpeed Insights — mobile performance audit of jurnper.exchange· checked Oct 14, 2026
97
Good
Performance
FCP
0.9s
First Contentful Paint
LCP
1.8s
Largest Contentful Paint
CLS
0.103
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
1.7s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Stored Capture Evidence 1 snapshot
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
Archived HTTP responseHTTP 200
Requested URL:http://jurnper.exchange/
Final URL:https://jurnper.exchange/
Jumper Exchange | Smart App for the Universal Market
Jumper Exchange is a multichain liquidity aggregator and DeFi hub built on LI.FI protocol that enables users to swap and bridge tokens cross-chain seamlessly.
响应 HTTP 200
HTML body 19.2 KB
Compressed 6.8 KB
Links 0 internal · 0 external
Detected technologies
nginx
Selected response headers
Server: nginx/1.30.5
Content-Type: text/html; charset=UTF-8
Content-Encoding: gzip
HSTS: not observedDNSSEC: not observedWAF / firewall: not observedCloaking flag: not observed
Open Graph title:Jumper Exchange | Smart App for the Universal Market
Open Graph description:Jumper Exchange is a multichain liquidity aggregator and DeFi hub built on LI.FI protocol that enables users to swap and bridge tokens cross-chain seamlessly.
Twitter card:summary_large_image
Saved response-header values · 7
Connection
keep-alive
Content-Encoding
gzip
Content-Length
6941
Content-Type
text/html; charset=UTF-8
Date
Wed, 14 Oct 2026 19:35:22 GMT
Server
nginx/1.30.5
Vary
Accept-Encoding
Values retained by the collector; long values may be shortened during collection.
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
Threat First Observed2026-10-14 19:34:07 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 104.168.132.201.
威胁响应 Pipeline
发现
Analysis
Notifications
Monitoring
9 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
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.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
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.
(US)
