Skip to security report
Domain security report
jetodus.com favicon

jetodus.com

“jetodus Crypto Hardware Wallet (Official) | The best wallet to protect your assets”

Threat verdict
Assessment sources

Assessment based on the stored source evidence below. Review sources →

Availability Content unavailable Content was unavailable in the latest observation Observed · HTTP probe
VirusTotal detections: 16/91 URLQuery threat systems: 3 alerts Automated brand label: Across
OTX: 4 refs Jul 27, 2026 Across 1 Report Sent
API
Registrar
TuringSign
Resolved IP
185.66.143.35
Registered
May 24, 2026
4 sources
Stored TLS certificateHostname mismatchReview certificate names and collection time
In this reportGet help
This domain has been flagged as malicious
Security engines reporting a detection: 16. Exercise extreme caution — do not enter credentials or personal information.

Additional indicators at a glance

VirusTotal
VirusTotal
16 det.
URLQuery
URLQuery
3 threat alerts
OTX references
CF Radar
Malicious
URLScan
URLScan
TLS Certificate
Hostname mismatch
Let's Encrypt · Certificate hostname mismatch
Age
5 mo
Observed status
Content unavailable
PhishDestroy
DestroyList
Listed
Reports Sent
1

Source evidence

8 · sources

These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.

VirusTotal

16 / 91

Report
Interpretation & limits

Engine detections from this stored analysis. Vendors and collection times may differ from other sources.

URLQuery

3 threat-system alerts

Report
Interpretation & limits

Alerts refer to the preserved scan. They do not describe the current state of the site.

CF Radar

provider verdict: malicious

Observation time not recorded
Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

OTX

4 community references

Report
Interpretation & limits

Community publication references, not a vendor verdict or evidence of a common operator.

URLScan capture

stored report

View stored capture ↗
Report
Interpretation & limits

A preserved page image documents what the collector received; a capture is not a safety verdict.

URLScan verdict

Analysis completed

Report
Interpretation & limits

This is the recorded automated analysis. Completion alone is not a safety verdict.

Google Safe Browsing

Checked; no threat flag recorded

Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Public blocklists

0 external matches

Details
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Network Security Intelligence
Threat Detection Systems 3 alerts
Detection System Indicator Verdict Alert
DNS4EU jetodus.com malicious Sinkholed
OpenDNS jetodus.com phishing Phishing Block
Cloudflare DNS jetodus.com malicious Sinkholed
CF Cloudflare Radar Verdict Malicious
Phishing Phishing Security threats

Evidence Summary

Critical
VirusTotal
16/91
OTX
4 community refs
URLScan
Stored capture

AI-assisted analysis Stored narrative · generated . Provider checks below retain their own observation dates. This narrative is an interpretation of collected evidence, not an independent source verdict.

On July 27, 2026, the domain jetodus.com was observed as an active generic phishing infrastructure. The domain resolves to the IPv4 address 185.66.143.35 and is delegated to the authoritative name servers ns19.knownsrv.com and ns20.knownsrv.com. Registration data indicates the domain was created on 24 May 2026 and was purchased through the registrar TuringSign Inc. d/b/a Cosmotown.

VirusTotal analysis shows that six of ninety‑one security vendors have flagged the domain as malicious, providing an early indicator of compromise. The domain is listed on one public security blocklist and is actively blocked by the PhishDestroy mitigation service, confirming that at least one defensive platform has identified it as a phishing source. No additional public intelligence such as page titles, SSL certificate details, or HTTP response codes is currently available, leaving the exact content and targeted brand of the phishing campaign unverified.

The presence of a recent registration date, a single‑digit vendor detection count, and inclusion on a blocklist suggest a purpose‑built operation rather than a long‑standing compromised site. Defenders should add jetodus.com to local block and allow lists, monitor DNS queries for the associated IP address, and consider leveraging threat‑intelligence feeds that include the domain’s identifiers. Continuous re‑assessment is advised, as further analysis of the landing page, credential‑harvesting mechanisms, and potential victim outreach may reveal additional indicators of compromise.

Data coverage & collection

22 · datasets with records / 9 · not recorded

What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.

Recorded dataPartial recordUTC
VirusTotal
16 / 91 · engine detections
URLScan analysis
Automated verdict retained
URLQuery
3 · recorded detections / alerts
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
4 · community references
External blocklists
0 · external matches
Cloudflare Radar
maliciousCollection time not recorded
Spamhaus DBL
Collection time retained; verdict missing
Domain registration
TuringSign Inc. d/b/a CosmotownCollection time not recorded
Network & DNS
185.66.143.35 · 2 · nameserversCollection time not recorded
TLS certificate
Let's Encrypt
Page captures
4 · retained captures
Page analysis
9 · automated brand labels
Observed indicators
1 · wallet / Telegram indicators
Detection & evasion
Stored browser and crawler comparison
PageSpeed performance
68/100 · mobile performance
Response records
1 · outgoing report records
Availability history
21 · stored state changes
Source observation history
2 · stored source events
Chainabuse records
4 · recorded reports
IP reputation
Network-level observations
Wayback archive
Archive link retained
Not recorded in this report 9

These checks have no retained result. This does not mean they passed or that a scan is running.

  • PhishStats
  • DNS security filters
  • Gridinsoft
  • Scamadviser
  • HTML archives
  • Site configuration files
  • Recorded subdomains
  • Lookalike relationships
  • Community reports
Download the dated observations and supporting metadata.
Extracted from stored page analysis

Observed indicators

0 wallet · 1 Telegram

Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.

Telegram
https://t.me/SafePal_officialStored page reference

IoC extraction recorded 2026-07-29 01:51:20 UTC

Blocklist records

0 · external source matches

Public Blocklist Status

Domain, network & archive

TuringSign Inc. d/b/a Cosmotown · 185.66.143.35 · DNS, TLS and retained responses

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Reputation abuse score 0/100 0 reports checked Sep 25, 2026
OTX tags 2026-07activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar TuringSign (Unknown)
Abuse contactabuse@cosmotown.com
RegistrationCreated May 24, 2026 (146d) — Expires May 24, 2027
Time to First Unavailability 79 days
What we count Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedJul 27, 2026
DOM Analysisanalyzed Oct 9, 2026score 98/1009 brand signals
IoC Extractionscanned Jul 29, 20260 wallet · 1 Telegram IoC
Submitted URLhttps://jetodus.com/
Favicon Hash
Case ID

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
185.66.143.35
Network ASN
AS200514
Organization
KnownSRV Ltd
Observed location
Amsterdam, NL
Server header
LiteSpeed
Nameservers 2
  • ns19.knownsrv.com
  • ns20.knownsrv.com
Mail routing 1 MX record
  • jetodus.compriority 0

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt
Valid from
2026-06-27 06:04:04
Valid until
2026-09-25 06:04:03
Hostname coverage
Certificate hostname mismatch
Validity
Stored certificate expired
Collection time
2026-07-27 07:02:51 UTC
Collection source
PhishDestroy collector
Certificate fingerprintba12b01650a7ae9989710ad03470b79dc80f9bc65ffd1cb4ae4c94ac155de736
Certificate names · 2 SANs
  • jetodus.com.fastlinegroupplc.com
  • www.jetodus.com.fastlinegroupplc.com

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Latest Classified Outcome 2026-10-17 01:54:29 UTC

Primary outcome Unknown reason: Probe Inconclusive 20% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Unreachable Content: Unknown DNS: Timeout Registration: Unknown
Latest HTTP observation Unknown Probe Inconclusive 20% 2026-10-17 01:54:29 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-11 22:27:44 UTC last content: 2026-10-11 22:27:44 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.
Technologies · 7 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

16 / 91 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 16 detections
alphaMountain.ai
BitDefender
CRDF
CyRadar
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Lionic
Netcraft
SOCRadar
Sophos
VIPRE
Webroot

Archived Evidence

Wayback Machine Snapshot
A historical snapshot is available for evidence review
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of jetodus.com · checked Jul 27, 2026

68
Needs Work
Performance
FCP
2.87s
First Contentful Paint
LCP
6.39s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
5.55s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details2

Availability observations

Last reachable observation
Last content observation

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Detection & evasion checks

Stored browser and crawler observations

Detection-evasion analysis

Cloaking and traffic-distribution check

Not yet scanned No crawler-versus-browser difference has been recorded yet

Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.

Stored cloaking flag
Not yet scanned
Last cloaking scan

Scanner note: unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='jetodus.com', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("SO

Live TDS fingerprint check
Seven Keitaro fingerprints and a browser-versus-crawler comparison. A new scan starts only when you press the button.
Saved result
Cloaked / Filtered

Timeline & response

1 · outbound report records

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.
  1. Domain Status Transition 2026-10-13 22:29:41 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain state transitioned from alive to dead.
  2. Threat First Observed 2026-07-27 04:34:48 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain ingestion complete. Initial state is marked as alive pointing to IP 185.66.143.35.
Stored observation history23

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Reachable→Unavailable

  2. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  3. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  4. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  5. Availability monitor · Recorded state

    Unknown→live_content

    content_served

Earlier observations 18
  1. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  2. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  3. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  4. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  5. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  6. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  7. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  8. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  9. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  10. Availability monitor · Recorded state

    live_content→Unknown

    stale_current_evidence

  11. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  12. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  13. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  14. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  15. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  16. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  17. Availability monitor · Recorded state

    Unknown

    probe_inconclusive

  18. Availability monitor · First collection record

    Reachable

Threat Response Pipeline

Discovery
Analysis
Notifications
Monitoring

15 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Threat Ingested
jetodus.com detected and queued for full analysis
Jul 27, 2026
URLScan.io Capture
Stored URLScan report with capture artifacts
Jul 27, 2026
Cloudflare Radar Report
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.
Web Archive
Preserved in Wayback Machine — historical evidence archived
Jul 27, 2026
VirusTotal
16/91 recorded on VirusTotal
Oct 6, 2026
OTX Community References
4 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
Oct 5, 2026
CF Radar: Malicious
Cloudflare Radar classified this domain as phishing, Phishing, Security threats
Brand Impersonation
Impersonation of Across
Forensic Evidence Collected
Stored evidence from URLScan.io, URLQuery, stored screenshot
Jul 27, 2026
Technical Analysis Recorded
The report contains stored technology or forensic-analysis results.
Oct 17, 2026
Content Observed Unavailable
Monitoring recorded an unavailable response; the cause was not independently established.
Oct 14, 2026
Sent Report Recorded
Stored outgoing record associated with registrar TuringSign Inc. d/b/a Cosmotown, 1 abuse contact
abuse@cosmotown.com
Jul 27, 2026
DestroyList Published
Jul 27, 2026
Content Observed Unavailable
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Oct 14, 2026
Time to First Unavailability
1889 hours elapsed from detection to the first unavailable observation.
How we investigate & report

Public scans, evidence and abuse channels

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
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. 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.

Related infrastructure

Shared hosting, registrar records and related domains

Community records

Retained community reports and observations

Community intelligence

4 community reports

CategoryOTHER_INVESTMENT_SCAM

Data submited by Intelligence for good

Evidence & investigation tools

Original reports, independent checks and evidence links

Evidence & External Reports

Third-Party Detection — ChainAbuse
4 reports filed for jetodus.com · category: Other Investment Scam · source checked
Flagged by Intelligence for Good on Jul 8, 2026 — automated submission, not a user testimony. Source: ChainAbuse (TRM Labs).
Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20260727-1BC733 Recipient: abuse@cosmotown.com
PDF notice generated Notice text archived (650 chars)
Abuse notice text as sent to the provider
Policy Violations:
Illegal Activities: Active phishing operation targeting victims
Fraud & Deception: Impersonation of legitimate services
Identity Theft: Collection of credentials under false pretenses
Applicable Laws (Unknown):
International Anti-Cybercrime Regulations
Budapest Convention on Cybercrime
Universal Fraud Prevention Laws
Phishing activities violate international cybercrime conventions and Unknown's domestic fraud laws.
Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
Deep Analysis

Help & reporting

Recovery steps, reporting contacts and complaint drafts

Help & reporting

Were You Affected by This Site?

6 evidence signal groups linked 1 stored notification records Content unavailable
If credentials were compromised, report immediately. Do not engage with recovery scammers.

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

Official reporting routes
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →
Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory

Template-based draft · optional AI wording assistance requires separate consent

Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

What information should I collect for my report?

FBI guidelines

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including jetodus.com)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?

  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?

  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Live Threat Feed Appeal This Listing
Read the evidence in context

About This Report: jetodus.com

Stored evidence snapshot. Source timestamps appear where available.

Captured title: “jetodus Crypto Hardware Wallet (Official) | The best wallet to protect your assets”. Apparent target: Across.

VirusTotal detections for jetodus.com: 16 (2026-10-06 02:24:04 UTC).

Each source records a particular observation. A screenshot, an available website, or a result with no detections does not establish that a site is safe. Source results can change after they are collected.

Embed this report

A compact widget with a link to the evidence

HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html
<iframe
  src="https://phishdestroy.io/embed/domain/jetodus.com"
  title="PhishDestroy threat report for jetodus.com"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>