jumper.ceo was listed on the MetaMask and SEAL external blocklists as of 2026-10-13, reflecting its presence in multiple security intelligence sources. Another notable fact is that OTX referenced two pulses for this domain on the same date.
Recorded Evidence
On 2026-10-13, jumper.ceo appeared on both the MetaMask and SEAL external blocklists. OTX recorded two pulses referencing the domain on that same date. VirusTotal checked the domain on 2026-10-12 and reported 0 detections out of 92 total scanners. PhishDestroy internally listed jumper.ceo as of 2026-10-13.
Interpretation
PhishDestroy provides an internal listing for jumper.ceo, documenting its inclusion in a security-focused database. VirusTotal’s record contains a scan-based measurement, showing how multiple security engines evaluated the domain. OTX records pulses, which are collections of security intelligence, adding further context to the domain’s monitoring profile. These sources together capture a range of security-related observations for jumper.ceo without asserting a single outcome.
Recommended Actions
For jumper.ceo, retain the external blocklist entries and the PhishDestroy internal listing for future reference. Compare the OTX pulse records and VirusTotal scan results periodically to monitor for changes in external intelligence or detection. Use these recorded observations to inform ongoing review and context-specific decisions regarding the domain.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
저장된 은신 플래그
아직 스캔되지 않았습니다
마지막 은폐 스캔
스캐너 메모:timeout: raw=timeout; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='jumper.ceo', port=80): Max retries exceeded with url: / (Caused by ConnectTimeoutError(<SO
TDS 지문 인식 실시간 확인
이 패널이 열려 있을 때 PhishDestroy 스캐너에서 실행되는 7개의 케이타로 지문과 크롤러 대 브라우저 비교 결과.
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observation알 수 없음Probe Inconclusive20%2026-10-13 01:00:45 UTC
RDAP registration알 수 없음
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.
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-12 23:43:00 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 144.31.223.117.
위협 대응 Pipeline
발견
Analysis
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.
차단 목록 탐지
출처: 2 blocklists: MetaMask, SEAL
2026년 10월 13일
OTX Community References
2 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
2026년 10월 13일
Brand Impersonation
Impersonation of Genericcrypto
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
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)
