Skip to security report
Analytics Dashboard
Domain security report
yomix.to favicon

yomix.to

Threat verdict
MediumDomain Appeal
Assessment sources

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

Availability Unverified Current reachability is unverified Observed · HTTP probe
Risk signals
Stored PhishDestroy threat listing
OTX: 1 ref Oct 16, 2026 1 Report Sent CDN
API
Registrar
DYNADOT
Resolved IP
104.21.33.215
Registered
Jun 11, 2026
2 sources
The capture source is temporarily unavailable.
1 / 2
Source
Primary capture
Collected · UTC
Open capture
⚠️
Suspicious Domain — Listed on PhishDestroy
Stored PhishDestroy threat listing. VirusTotal analysis stored; no vendor detections were recorded at check time. Exercise extreme caution — do not enter credentials or personal information.
Additional indicators at a glance
OTX references
1 community ref
URLScan
URLScan
Report ↗
TLS Certificate
Expired or unverified
Age
4 mo
PhishDestroy
DestroyList
Listed
Reports Sent
1

Source evidence

7 · 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

checked — no detections recorded

Report
Interpretation & limits

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

URLQuery

Report stored; detailed verdict not recorded

Observation time not recorded
Report
Interpretation & limits

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

OTX

1 community reference

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.

CF Radar

Report stored; verdict not recorded

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.

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.

Evidence Summary

Medium
OTX
1 community ref
URLScan
Stored capture

Stored narrative · generated . Provider checks below retain their own observation dates.

Assessment

yomix.to was referenced in a publisher-owned PhishDestroy internal listing on 2026-10-16, documenting its presence in a curated catalogue. Additional technical data was recorded for yomix.to on the same date, providing further context for review.

Read the full analysis3

Recorded Evidence

VirusTotal checked yomix.to on 2026-10-16, recording 0 detections out of 92 total scanners. OTX documented one pulse referencing the domain on 2026-10-16. The domain was registered with DYNADOT LLC on 2026-06-11. A PageSpeed performance score of 77 was also captured on 2026-10-16.

Interpretation

The PhishDestroy internal listing contains a record of yomix.to, which documents its inclusion in a publisher-curated catalogue. VirusTotal provides a measurement of security scanner results, offering a technical snapshot of how the domain was evaluated by multiple sources. OTX records an external intelligence pulse, contributing to the timeline of references associated with yomix.to.

Recommended Actions

For yomix.to, retain the PhishDestroy internal listing and VirusTotal scanner results for future comparison. Review the OTX pulse and PageSpeed performance score alongside subsequent observations to monitor changes in external intelligence and technical performance. Preserve these records for ongoing domain evidence tracking.

Data coverage & collection19 · datasets with records / 12 · 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
0 / 92 · engine detections
URLScan analysis
Capture retained; no provider verdictCollection time not recorded
URLQuery
Stored source recordCollection time not recorded
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
1 · community references
External blocklists
0 · external matches
Cloudflare Radar
Report link retainedCollection time not recorded
Domain registration
DYNADOT LLCCollection time not recorded
Network & DNS
104.21.33.215 · 2 · nameserversCollection time not recorded
TLS certificate
Let's Encrypt / YE2
Page captures
2 · retained captures
HTML archives
1 · retained responses
Site configuration files
robots.txt · sitemap.xml · security.txt
PageSpeed performance
77/100 · mobile performance
Response records
1 · outgoing report records
Recorded subdomains
1 · retained hostnamesCollection time not recorded
Availability history
1 · stored state changes
Source observation history
1 · stored source events
IP reputation
Network-level observations
Not recorded in this report 12

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

  • PhishStats
  • DNS security filters
  • Gridinsoft
  • Scamadviser
  • Spamhaus DBL
  • Page analysis
  • Observed indicators
  • Detection & evasion
  • Lookalike relationships
  • Community reports
  • Chainabuse records
  • Wayback archive
Download the dated observations and supporting metadata.
Blocklist records0 · external source matches

Public Blocklist Status

Domain, network & archiveDYNADOT LLC · 104.21.33.215 · DNS, TLS and retained responses

Domain details

Domain
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags blocklistcryptodrainerfraudphishdestroyphishingscam
Registrar DYNADOT US(US)
Abuse contactabuse@dynadot.com
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for yomix.to →
RegistrationCreated Jun 11, 2026 (126d) — Expires Jun 11, 2027
Technical detailsProvenance & timestamps
First DetectedOct 16, 2026
Submitted URLhttps://yomix.to/
Favicon Hash
Case ID

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
104.21.33.215

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • bella.ns.cloudflare.com
  • melnicoff.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE2
Valid from
2026-09-23 04:24:36
Valid until
2026-12-22 04:24:35
Hostname coverage
Hostname coverage not recorded
Validity
Within stored validity dates
Collection time
2026-10-16 01:02:03 UTC
Collection source
PhishDestroy collector
Certificate fingerprintf9f4cc30fc73df29d19c9d573e4c2f27d2e305c8424bb53435a2d7b73902221f

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

viewdns.info · 104.21.33.215rapiddns.io

Latest Classified Outcome 2026-10-15 23:12:28 UTC

Primary outcome Unknown reason: Probe Inconclusive 20% confidence
Attribution source: Current State Backfill
Evidence layers Availability: Unreachable Content: Unknown DNS: Stale Registration: Unknown
Latest HTTP observation Unknown Probe Inconclusive 20% 2026-10-15 23:12:28 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-15 23:12:28 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.
Recorded subdomains1

Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.

  • www.yomix.toDomain record

The original observation time is not recorded for these hostnames.

Report This Domain Submit evidence & help protect others
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of yomix.to · checked Oct 16, 2026

77
Needs Work
Performance
FCP
2.71s
First Contentful Paint
LCP
3.94s
Largest Contentful Paint
CLS
0.154
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
3.28s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-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 response HTTP 200
Requested URL: https://yomix.to/
Yomix
YoMix.TO especially created to provide full anonymity to you and your bitcoins. Innovative mixing technology is now available to everyone.
Response
HTTP 200
HTML body
36.0 KB
Compressed
6.2 KB
Links
30 internal · 0 external
Detected technologies
jquerycloudflare
Selected response headers
Content-Type: text/html; charset=utf-8
Server: cloudflare
CF-Cache-Status: DYNAMIC
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Favicon fingerprint: 62d869b48e04e08497b09d082f730f79f45f975a99f0fb5f3eca3112d86d6a66
Open Graph title: Yomix
Open Graph description: YoMix.TO especially created to provide full anonymity to you and your bitcoins. Innovative mixing technology is now available to everyone.
Twitter card: summary_large_image
Saved response-header values · 16
Access-Control-Allow-Headers
Content-Type, X-Requested-With
Access-Control-Allow-Methods
GET, POST, OPTIONS
Access-Control-Allow-Origin
*
alt-svc
h3=":443"; ma=86400
cf-cache-status
DYNAMIC
CF-RAY
a4b283918a127287-EWR
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=utf-8
Date
Thu, 15 Oct 2026 23:13:22 GMT
Nel
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=UYY7mA47nELUZUpb28gWpm%2FI9d5EZsX4980vRfxo86Mc56qMrbF3Fxm3DWrmNlt5Vak%2BddT9YRXlKCMCBEWMrdobg3qVx34rJY063%2BZsyjmeZCwO6Je5U2XktA%3D%3D"}]}
Server
cloudflare
Server-Timing
cfCacheStatus;desc="DYNAMIC"
Transfer-Encoding
chunked
Vary
Accept-Encoding

Values retained by the collector; long values may be shortened during collection.

Archived
Crawler & disclosure files

Site configuration evidence

3 · file checks

Stored file checks, including unavailable and invalid responses. Retained contents and paths appear where available.

robots.txt

Reachable (legacy)
/robots.txt
HTTP response
200
Observed at
2026-10-15 23:13:24 UTC
Source
legacy scan archive

A legacy scan recorded a successful response. The file contents were not retained.

Sitemap

Reachable (legacy)
/sitemap.xml
HTTP response
200
Observed at
2026-10-15 23:13:24 UTC
Source
legacy scan archive

A legacy scan recorded a successful response. The file contents were not retained.

security.txt

Not found
/.well-known/security.txt
HTTP response
404
Observed at
2026-10-15 23:13:24 UTC
Source
legacy scan archive

The scanner received HTTP 404 or 410 for this file.

Registration & observation details1

Availability observations

Last reachable 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 checksStored 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
Capture routing
Local archived 2026-10-15 23:13:24 UTC
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
Waiting
Timeline & response1 · 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. Threat First Observed 2026-10-15 23:12:28 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain ingestion complete. Initial state is marked as alive pointing to IP 104.21.33.215.
Stored observation history2

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

    Unknown

    probe_inconclusive

  2. Availability monitor · First collection record

    Reachable

Threat Response Pipeline

Discovery
Analysis
Notifications
Monitoring

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

Threat Ingested
yomix.to detected and queued for full analysis
Oct 16, 2026
URLScan.io Capture
Stored URLScan report with capture artifacts
Oct 16, 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.
OTX Community References
1 community publication reference on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
Oct 16, 2026
Forensic Evidence Collected
Stored evidence from URLScan.io, URLQuery, stored screenshot
Oct 16, 2026
Sent Report Recorded
Stored outgoing record associated with registrar DYNADOT LLC, 1 abuse contact
abuse@dynadot.com
Oct 15, 2026
DestroyList Published
Listed in the public PhishDestroy/DestroyList repository
Oct 16, 2026
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.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecSiteReview AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation
Related infrastructureShared hosting, registrar records and related domains
Evidence & investigation toolsOriginal reports, independent checks and evidence links

Evidence & External Reports

Security Analysis
URLScan Stored capture VirusTotal ChainPatrol URLQuery Report stored SSL Labs Hostname coverage not recorded CF Radar Open report OTX 1 ref WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20261015-3B5126 Recipient: abuse@dynadot.com
PDF notice generated Notice text archived (291 chars)
Abuse notice text as sent to the provider 
Registrar: Dynadot LLC / Dynadot Inc (United States)
Policy Violations: Acceptable Use forbids illegal content; Spam & Abuse Policy prohibits phishing, fraud, malware; Dynadot may disable DNS and suspend domains
Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis
Help & reportingRecovery steps, reporting contacts and complaint drafts

Were You Affected by This Site?

5 evidence signal groups linked 1 reports recorded Unverified
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.

Europol
Find the official reporting channel for your EU country
National police directory
PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect
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

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

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
Embed this reportA 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/yomix.to"
  title="PhishDestroy threat report for yomix.to"
  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>