Skip to security report
Analytics Dashboard
Domain security and threat intelligence
tornadomixer.org favicon

tornadomixer.org

In short

tornadomixer.org is a blocklisted domain detected by PhishDestroy on 2026-10-23. Risk: critical (88/100). Registrar: Name.com. Status: Last known active. Hosting: Amazon.com. PhishDestroy sent 1 abuse report. VirusTotal: 1/92 engines flag it. Do not enter credentials or connect a wallet.

“Tornado - Cryptocurrency Mixer”

Review the evidence
Registrar
Name.com
Resolved IP
35.157.26.135
Registered
Sep 8, 2026
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed · HTTP probe
Risk signals
VirusTotal detections: 1/92 Stored blocklist matches: 2
OTX: 4 refs Oct 23, 2026 1 Report Sent CDN
API
This domain has been flagged as malicious
Security engines reporting a detection: 1. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
ABUSE NOTICE · 24H+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence

The sent-report ledger records the first outgoing report at . The recorded recipient is abuse@name.com. The latest stored availability evidence still shows the domain reachable; 29 hours has elapsed since the first outgoing report.

ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.

Elapsed since first report
29 hours
Reports sent
1
Latest case ID
PD-20261023-30722B
Current status
HTTP 200 at latest stored check
VirusTotal
1 / 92
engine detections
Google Safe Browsing
No threat flag
OTX
4
community references
Page captures
7
open gallery
Domain age
45 days
Reports sent
1
view timeline
Source evidenceVirusTotal 1 / 92 · OTX 4 references 6 sources

VirusTotal

1 / 92 engine detections

Open report

OTX

4 community references

Open report

Google Safe Browsing

No threat flag

Open report

URLScan

No malicious flag

Open report

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Analysis

Critical
VirusTotal
1 / 92
OTX
4 community refs
Page captures
7
Page captures Source results Registration record

PhishDestroy threat report

Overview

PhishDestroy’s intake system classified the site as malicious because it presents itself as a cryptocurrency mixer, a service often linked to money‑laundering activities. The recorded page title on 2026-10-23 reads “Tornado – Cryptocurrency Mixer” and the page shows a “Mix Cryptocurrency” interface with deposit statistics. PhishDestroy first observed the domain on 2026-10-23, 45 days after its registration on 2026-09-08, and an HTTP 200 response was recorded on that date.

How the scam works

Cryptocurrency mixers pool funds from many users, shuffle them, and return the same amount to designated addresses, thereby obscuring the transaction trail. Operators typically charge a fee and may request wallet connections, creating opportunities to steal or lock users’ assets.

Evidence

The intake AI flagged the page as malicious with high confidence, citing the mixer‑related content as a fraud indicator. VirusTotal recorded one malicious detection (CRDF) out of 92 engines on 2026-10-23. URLScan’s engine scoring marked the URL as malicious with a score of 85, while its overall verdict was clean on the same date. Google Safe Browsing reported no flag, OTX listed four pulses referencing the domain, and external blocklists MetaMask and SEAL both flagged it; PhishDestroy also lists the domain internally.

Infrastructure

The domain was registered with Name.com on 2026-09-08 and is marked clientTransferProhibited. Hosting records show the site served from IP 98.84.224.111, an Amazon AWS node in the United States, and the HTTP headers indicate a Netlify front‑end. The TLS certificate, issued by Let’s Encrypt, was valid from 2026-09-08 to 2026-12-07 and covers both the apex and wildcard subdomains.

What to do

Avoid visiting the site or providing any wallet credentials; if a wallet was connected, monitor the associated accounts for unauthorized activity. Defenders should block tornadomixer.org at DNS or proxy level, log any connections to the recorded IPs, and add the domain to internal threat feeds.

Useful links

urlscan.io scan and screenshotCloudflare Radar reportURLQuery reportStored capture screenshotCloudflare Radar screenshot (2026-10-23T01:33:48Z)URLQuery screenshotURLScan screenshot (2026-10-21T09:14:34Z)URLScan capture reportURLScan screenshot (2026-10-23T01:37:23Z)URLScan capture reportVirusTotal reportGoogle Safe Browsing statusReport phishing to GoogleSite owner? Request a review

Questions about tornadomixer.org

Is tornadomixer.org legit?

No. PhishDestroy classifies tornadomixer.org as a blocklisted domain (risk: critical, 88/100); it was first detected on 2026-10-23. VirusTotal: 1/92 engines flag it. Treat the site as unsafe.

Is tornadomixer.org safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on tornadomixer.org. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.

What should I do if I used tornadomixer.org?

Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.

Explore

Blocklist matchesMetaMask · PhishDestroy · SEAL 3
MetaMask Listed View source
PhishDestroy PhishDestroy list View source
SEAL Listed View source

Last checked

Stored Capture · 7 captures

Primary capture 1 / 7
SourcePrimary capture
Recorded2026-10-23 01:37 UTC
StateStored capture
HTTP status at archiveHTTP 200
Final URLhttps://tornadomixer.org/
Position1 / 7
Open capture Wayback Download

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Context Netlify shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags 2026-10activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar Name.com SE(SE)
Abuse contactabuse@name.com
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for tornadomixer.org →
RegistrationCreated Sep 8, 2026 (45d · New) — Expires Sep 8, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 23, 2026
DOM Analysisanalyzed Oct 23, 2026score 88/100
Submitted URLhttp://tornadomixer.org/
Favicon Hash
Case ID
Observed page title
Tornado - Cryptocurrency Mixer
TLS Certificate
Issued by Let's Encrypt / YE2 · stored validity ends in 44 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
35.157.26.135
Network ASN
AS16509
Organization
Amazon.com
Observed location
Frankfurt, DE
Server header
Netlify

Edge-IP reputation is not attributed to this domain.

Nameservers 4

  • dns1.p01.nsone.net
  • dns2.p01.nsone.net
  • dns3.p01.nsone.net
  • dns4.p01.nsone.net

Mail routing 1 MX record

  • smtp.google.compriority 1

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE2
Valid from
2026-09-08 17:35:32
Valid until
2026-12-07 17:35:31
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintee26d7d17475b82519e0e85c654287378c5cc6b062c01c32ede17cd03fac7739
Certificate names · 2 SANs
  • *.tornadomixer.org
  • tornadomixer.org

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

viewdns.info · 35.157.26.135rapiddns.io

Latest Classified Outcome 2026-10-23 22:01:54 UTC

Primary outcome Live content reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Stale Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-10-23 22:01:54 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-23 22:31:34 UTC last content: 2026-10-23 22:01:54 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

1 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 1 detection
CRDF
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of tornadomixer.org · checked Oct 23, 2026

100
Good
Performance
FCP
0.79s
First Contentful Paint
LCP
1.23s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
63ms
Total Blocking Time
SI
1.84s
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: http://tornadomixer.org/
Final URL: https://tornadomixer.org/
Tornado - Cryptocurrency Mixer
Generated by create next app
Response
HTTP 200
HTML body
11.8 KB
Compressed
3.1 KB
Links
0 internal · 0 external
Detected technologies
react
Selected response headers
Cache-Control: public,max-age=0,must-revalidate
Content-Encoding: gzip
Content-Type: text/html; charset=utf-8
Server: Netlify
X-Powered-By: Next.js
Security headers present
Strict-Transport-SecurityX-Content-Type-Options
HSTS: observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 18
Age
3809353
Cache-Control
public,max-age=0,must-revalidate
Cache-Status
"Netlify Durable"; hit; ttl=27726646
Content-Encoding
gzip
Content-Length
3240
Content-Type
text/html; charset=utf-8
Date
Fri, 23 Oct 2026 01:29:43 GMT
Etag
"8kojyym65g9b5"
Netlify-Vary
query=__nextDataReq|_rsc, header=x-nextjs-data|x-next-debug-logging|next-router-prefetch|next-router-segment-prefetch|next-router-state-tree|next-url|rsc|accept-encoding, cookie=__prerender_bypass|__next_preview_data
Server
Netlify
Strict-Transport-Security
max-age=31536000
Vary
rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch, Accept-Encoding
X-Content-Type-Options
nosniff
X-Nextjs-Date
Tue, 20 Oct 2026 20:14:18 GMT
X-Nextjs-Prerender
1, 1
X-Nextjs-Stale-Time
300
X-Nf-Request-Id
01M5K61M54XB5MNP2BBH7CGXBW
X-Powered-By
Next.js

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

Archived
Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

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

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

Every stored field, with its source and date
URLScan · 2026-10-23T01:36:06Z21 fields

Observed: · Retrieved:

Report ID

01a16666-8d3d-74b1-8cd9-8c187cb78b6d

Final url

https://tornadomixer.org/

HTTP response

200

Redirected

https-only

Redirects

  • To
    https://tornadomixer.org/
    From
    http://tornadomixer.org/
    Status
    307

Ip

98.84.224.111

Ptr

ec2-98-84-224-111.compute-1.amazonaws.com

Contacted IP addresses

  • 98.84.224.111

Asns

  • 14618

Countries

  • US

Document hash

baecc717cd8aef86908e1785fe0016dd06956e512a3dfab2485ac63fc1fe1046

Script hashes

  • 49cf866bf4d0282119e51835114325403f28e53fd0bccb63dde7ba3114a8e9fb
  • 82d28975ef4120af4576e36df96453dca7465c104a3dc53aa1be2625e8ef685d
  • c0930af826f989eea00dbaca15c1e4b3d3609b7b0bc5416a661a4948d8c26515
  • 7a3b5d6ac23f323b67a406c5541141f56821a28f18c0b1eb0336a53c8c99790d
  • 34ed6abf4c6d0d1bb3dc56d3f133d2a5dbc3a3c89c791deab314e27143ac14ce
  • ce5d41ae3146e80a319e80274e6787046f8d2e67cc4f85d4703ea94d82fc9dca
  • a28004df24371c97caf4436a204659da088dbe231753a9cbdbbe4bf22779dfd9
  • 932e33a2d78e4d190fcb54ac91da84710b38589695b18679a4aa6b11192c3749
  • 4e73ef1381120a3bcc849a970152d3415e070d8051b8344a073e97b5ceca000d
  • 3a946abd1ea019b60096464bfae1b83262816f25c1d4ee7829846b6158446042

Globals

  • __next_f
  • TURBOPACK
  • next
  • __webpack_hash__

Tls

San
  • *.tornadomixer.org
  • tornadomixer.org
Cipher
AES_128_GCM
Issuer
YE2
Subject
tornadomixer.org
Protocol
TLS 1.3
Valid to
Valid from

Domain age days

44

Apex age days

44

Tls age days

44

Tls valid days

89

Requests

15

Provider verdicts

Engines
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
85
Malicious
Yes
Overall
Score
0
Malicious
No

HTTP headers

Server
Netlify
Content-type
text/html; charset=utf-8
X-powered-by
Next.js
Strict-transport-security
max-age=31536000
X-content-type-options
nosniff
Original source fields · JSON
Uuid
01a16666-8d3d-74b1-8cd9-8c187cb78b6d
Final url
https://tornadomixer.org/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://tornadomixer.org/",
        "from": "http://tornadomixer.org/",
        "status": 307
    }
]
Ip
98.84.224.111
Ptr
ec2-98-84-224-111.compute-1.amazonaws.com
Contacted IP addresses
[
    "98.84.224.111"
]
Asns
[
    "14618"
]
Countries
[
    "US"
]
Document hash
baecc717cd8aef86908e1785fe0016dd06956e512a3dfab2485ac63fc1fe1046
Script hashes
[
    "49cf866bf4d0282119e51835114325403f28e53fd0bccb63dde7ba3114a8e9fb",
    "82d28975ef4120af4576e36df96453dca7465c104a3dc53aa1be2625e8ef685d",
    "c0930af826f989eea00dbaca15c1e4b3d3609b7b0bc5416a661a4948d8c26515",
    "7a3b5d6ac23f323b67a406c5541141f56821a28f18c0b1eb0336a53c8c99790d",
    "34ed6abf4c6d0d1bb3dc56d3f133d2a5dbc3a3c89c791deab314e27143ac14ce",
    "ce5d41ae3146e80a319e80274e6787046f8d2e67cc4f85d4703ea94d82fc9dca",
    "a28004df24371c97caf4436a204659da088dbe231753a9cbdbbe4bf22779dfd9",
    "932e33a2d78e4d190fcb54ac91da84710b38589695b18679a4aa6b11192c3749",
    "4e73ef1381120a3bcc849a970152d3415e070d8051b8344a073e97b5ceca000d",
    "3a946abd1ea019b60096464bfae1b83262816f25c1d4ee7829846b6158446042"
]
Globals
[
    "__next_f",
    "TURBOPACK",
    "next",
    "__webpack_hash__"
]
Tls
{
    "san": [
        "*.tornadomixer.org",
        "tornadomixer.org"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE2",
    "subject": "tornadomixer.org",
    "protocol": "TLS 1.3",
    "valid_to": "2026-12-07T17:35:31Z",
    "valid_from": "2026-09-08T17:35:32Z"
}
Domain age days
44
Apex age days
44
Tls age days
44
Tls valid days
89
Requests
15
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 85,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "Netlify",
    "content-type": "text/html; charset=utf-8",
    "x-powered-by": "Next.js",
    "strict-transport-security": "max-age=31536000",
    "x-content-type-options": "nosniff"
}
Cloudflare Radar · 2026-10-23T01:33:48Z11 fields

Observed: · Retrieved:

Report ID

87f65aa7-a853-4452-982b-d102f71c79f1

Final url

https://tornadomixer.org/

HTTP response

200

History

  • URL
    https://tornadomixer.org/
    Status
    200

DOM structure hash

63b72085c7d039cd6e5571735f27ecc966364e8244c4e0195ed0176b628feecd

Document hash

baecc717cd8aef86908e1785fe0016dd06956e512a3dfab2485ac63fc1fe1046

Radar rank

Bucket
>200000

DNS records

  • Name
    tornadomixer.org
    Type
    A
    Value
    13.52.188.95
  • Name
    tornadomixer.org
    Type
    A
    Value
    52.52.192.191

Dnssec valid

No

Ip

13.52.188.95

Registration record

Registrar
Name.com, Inc.
Registered
Updated
Expires
Nameservers
  • dns1.p01.nsone.net
  • dns2.p01.nsone.net
  • dns3.p01.nsone.net
  • dns4.p01.nsone.net
Original source fields · JSON
Uuid
87f65aa7-a853-4452-982b-d102f71c79f1
Final url
https://tornadomixer.org/
Status
200
History
[
    {
        "url": "https://tornadomixer.org/",
        "status": 200
    }
]
DOM structure hash
63b72085c7d039cd6e5571735f27ecc966364e8244c4e0195ed0176b628feecd
Document hash
baecc717cd8aef86908e1785fe0016dd06956e512a3dfab2485ac63fc1fe1046
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "tornadomixer.org",
        "type": "A",
        "value": "13.52.188.95"
    },
    {
        "name": "tornadomixer.org",
        "type": "A",
        "value": "52.52.192.191"
    }
]
Dnssec valid
false
Ip
13.52.188.95
Registration record
{
    "registrar": "Name.com, Inc.",
    "created": "2026-09-08T16:20:49Z",
    "updated": "2026-09-13T16:21:42Z",
    "expires": "2027-09-08T16:20:49Z",
    "nameservers": [
        "dns1.p01.nsone.net",
        "dns2.p01.nsone.net",
        "dns3.p01.nsone.net",
        "dns4.p01.nsone.net"
    ]
}
VirusTotal · 2026-10-23T02:05:47Z14 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
53
Malicious
1
Suspicious
0
Undetected
38

Vendor labels

CRDF
malicious

Reputation

0

Registrar

Name.com, Inc.

Created

Expires

Updated

First seen

DNS records

  • Ttl
    3600
    Type
    NS
    Value
    dns2.p01.nsone.net
  • Ttl
    120
    Type
    A
    Value
    98.84.224.111
  • Ttl
    3600
    Type
    NS
    Value
    dns1.p01.nsone.net
  • Ttl
    120
    Type
    A
    Value
    18.208.88.157
  • Ttl
    3600
    Type
    TXT
    Value
    google-site-verification=vrnyx6RytJePnSAEvXLc7UaOoObPq-vxdwqnwxNRj2k
  • Ttl
    3600
    Type
    MX
    Value
    smtp.google.com
    Priority
    1
  • Ttl
    3600
    Type
    TXT
    Value
    v=spf1 include:_spf.google.com ~all
  • Ttl
    3600
    Type
    NS
    Value
    dns3.p01.nsone.net
  • Ttl
    3600
    Type
    NS
    Value
    dns4.p01.nsone.net
  • Ttl
    3600
    Type
    SOA
    Rname
    domains+netlify.netlify.com
    Value
    dns1.p01.nsone.net

Dns at

Jarm

40d40d40d00000000043d43d00043d6aff5ab0f4fc31897186312c9e639319

Certificate

San
  • *.tornadomixer.org
  • tornadomixer.org
Issuer
Let's Encrypt / YE2
Serial
634ed360528ab3e9dfa8b516ad2b369e533
Sha256
ee26d7d17475b82519e0e85c654287378c5cc6b062c01c32ede17cd03fac7739
Subject
tornadomixer.org
Valid to
Valid from

Registration record

Registrar
Name.com, Inc.
Registrar iana id
625
Registrar url
http://www.name.com
Registered
Updated
Expires
Status
  • clientTransferProhibited
Nameservers
  • dns1.p01.nsone.net
  • dns2.p01.nsone.net
  • dns3.p01.nsone.net
  • dns4.p01.nsone.net
Dnssec
unsigned

Registry data

Status
  • transfer prohibited
Events
Expiration
Last changed
Registration
Registrar expiration
Last update of RDAP database
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 53,
    "malicious": 1,
    "suspicious": 0,
    "undetected": 38
}
Vendor labels
{
    "CRDF": "malicious"
}
Reputation
0
Registrar
Name.com, Inc.
Created
2026-09-08T16:20:49Z
Expires
2027-09-08T16:20:49Z
Updated
2026-09-13T16:21:42Z
First seen
2026-09-22T11:50:29Z
DNS records
[
    {
        "ttl": 3600,
        "type": "NS",
        "value": "dns2.p01.nsone.net"
    },
    {
        "ttl": 120,
        "type": "A",
        "value": "98.84.224.111"
    },
    {
        "ttl": 3600,
        "type": "NS",
        "value": "dns1.p01.nsone.net"
    },
    {
        "ttl": 120,
        "type": "A",
        "value": "18.208.88.157"
    },
    {
        "ttl": 3600,
        "type": "TXT",
        "value": "google-site-verification=vrnyx6RytJePnSAEvXLc7UaOoObPq-vxdwqnwxNRj2k"
    },
    {
        "ttl": 3600,
        "type": "MX",
        "value": "smtp.google.com",
        "priority": 1
    },
    {
        "ttl": 3600,
        "type": "TXT",
        "value": "v=spf1 include:_spf.google.com ~all"
    },
    {
        "ttl": 3600,
        "type": "NS",
        "value": "dns3.p01.nsone.net"
    },
    {
        "ttl": 3600,
        "type": "NS",
        "value": "dns4.p01.nsone.net"
    },
    {
        "ttl": 3600,
        "type": "SOA",
        "rname": "domains+netlify.netlify.com",
        "value": "dns1.p01.nsone.net"
    }
]
Dns at
2026-10-23T02:11:17Z
Jarm
40d40d40d00000000043d43d00043d6aff5ab0f4fc31897186312c9e639319
Certificate
{
    "san": [
        "*.tornadomixer.org",
        "tornadomixer.org"
    ],
    "issuer": "Let's Encrypt / YE2",
    "serial": "634ed360528ab3e9dfa8b516ad2b369e533",
    "sha256": "ee26d7d17475b82519e0e85c654287378c5cc6b062c01c32ede17cd03fac7739",
    "subject": "tornadomixer.org",
    "valid_to": "2026-12-07T17:35:31Z",
    "valid_from": "2026-09-08T17:35:32Z"
}
Registration record
{
    "registrar": "Name.com, Inc.",
    "registrar_iana_id": "625",
    "registrar_url": "http://www.name.com",
    "created": "2026-09-08T16:20:49Z",
    "updated": "2026-09-13T16:21:42Z",
    "expires": "2027-09-08T16:20:49Z",
    "status": [
        "clientTransferProhibited"
    ],
    "nameservers": [
        "dns1.p01.nsone.net",
        "dns2.p01.nsone.net",
        "dns3.p01.nsone.net",
        "dns4.p01.nsone.net"
    ],
    "dnssec": "unsigned"
}
Registry data
{
    "status": [
        "transfer prohibited"
    ],
    "events": {
        "expiration": "2027-09-08T16:20:49Z",
        "last changed": "2026-09-13T16:21:42Z",
        "registration": "2026-09-08T16:20:49Z",
        "registrar expiration": "2027-09-08T16:20:49Z",
        "last update of RDAP database": "2026-09-13T16:21:42Z"
    }
}
Website checks · 2026-10-23T01:39:22Z21 fields

Mail configuration

Mx
  • smtp.google.com
Spf
v=spf1 include:_spf.google.com ~all
Dkim
  • google
Dkim bits
2048
Providers
  • Google Workspace
SPF lookups
1

CAA records

Domain
tornadomixer.org

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Web archive observations

Last observation
First observation
Recorded changes
0
Archived days
1
Average page size, bytes
4326

Page title and metadata

Page title
Tornado - Cryptocurrency Mixer
Description
Generated by create next app

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
6
TLS
112
Waiting
275
Connection
14
Download
8
Response time, ms
415

TLS connection

ALPN
h2
Cipher
TLS_AES_128_GCM_SHA256
Protocol
TLSv1.3
Supported versions
  • TLSv1.2
  • TLSv1.3
Certificate authorized
Yes
Forward secrecy
Yes

Ports

Open
  • 80
  • 443

Carbon estimate

Bytes
12067
CO₂, grams
0.0004
Cleaner than, %
68

DNS servers

Nameservers
  • IP address
    198.51.44.1
    Host
    dns1.p01.nsone.net
  • IP address
    198.51.45.1
    Host
    dns2.p01.nsone.net
  • IP address
    198.51.44.65
    Host
    dns3.p01.nsone.net
  • IP address
    198.51.45.65
    Host
    dns4.p01.nsone.net
DNS zone
tornadomixer.org

Location

IP address
63.176.8.218
ASN
16509
Organization
Amazon.com
City
Frankfurt
Country
DE

TLS certificate

Issuer
Let's Encrypt / YE2
Subject
tornadomixer.org

DNS records

A
  • 35.157.26.135
  • 63.176.8.218
MX
  • Exchange
    smtp.google.com
    Priority
    1
NS
  • dns1.p01.nsone.net
  • dns4.p01.nsone.net
  • dns3.p01.nsone.net
  • dns2.p01.nsone.net
SOA
Primary nameserver
dns1.p01.nsone.net
Hostmaster
domains+netlify.netlify.com
Serial
1788884447
Refresh, seconds
43200
Retry, seconds
7200
Expiry, seconds
1209600
Minimum TTL, seconds
3600
TXT
  • v=spf1 include:_spf.google.com ~all
  • google-site-verification=vrnyx6RytJePnSAEvXLc7UaOoObPq-vxdwqnwxNRj2k

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Header
max-age=31536000
Observation
HSTS header does not include all subdomains.

HTTP security policies

X-Frame-Options
No
Referrer-Policy
No
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
nosniff
Content-Security-Policy
No
Strict-Transport-Security
max-age=31536000
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
35.157.26.135
IP version
4

Redirects

Redirect chain
  • https://tornadomixer.org

Registration record

Registrar
Name.com, Inc.
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
Nameservers
  • dns1.p01.nsone.net
  • dns2.p01.nsone.net
  • dns3.p01.nsone.net
  • dns4.p01.nsone.net

HTTP headers

Response headers
Server
Netlify
Content-type
text/html; charset=utf-8
X-powered-by
Next.js
Strict-transport-security
max-age=31536000
X-content-type-options
nosniff
Original source fields · JSON
Mail configuration
{
    "mx": [
        "smtp.google.com"
    ],
    "spf": "v=spf1 include:_spf.google.com ~all",
    "dkim": [
        "google"
    ],
    "dkim_bits": 2048,
    "providers": [
        "Google Workspace"
    ],
    "spf_lookups": 1
}
Caa records
{
    "domain": "tornadomixer.org"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Web archive observations
{
    "last": "2026-10-23T01:29:40Z",
    "first": "2026-10-23T01:29:40Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 4326
}
Page title and metadata
{
    "title": "Tornado - Cryptocurrency Mixer",
    "description": "Generated by create next app"
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 6,
        "tls": 112,
        "wait": 275,
        "connect": 14,
        "download": 8
    },
    "response_ms": 415
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_128_GCM_SHA256",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443
    ]
}
Carbon
{
    "bytes": 12067,
    "co2_grams": 0.0004,
    "cleaner_than": 68
}
Dns server
{
    "ns": [
        {
            "ip": "198.51.44.1",
            "host": "dns1.p01.nsone.net"
        },
        {
            "ip": "198.51.45.1",
            "host": "dns2.p01.nsone.net"
        },
        {
            "ip": "198.51.44.65",
            "host": "dns3.p01.nsone.net"
        },
        {
            "ip": "198.51.45.65",
            "host": "dns4.p01.nsone.net"
        }
    ],
    "zone": "tornadomixer.org"
}
Location
{
    "ip": "63.176.8.218",
    "asn": "16509",
    "org": "Amazon.com",
    "city": "Frankfurt",
    "country": "DE"
}
Ssl
{
    "issuer": "Let's Encrypt / YE2",
    "subject": "tornadomixer.org"
}
DNS records
{
    "A": [
        "35.157.26.135",
        "63.176.8.218"
    ],
    "MX": [
        "{\"exchange\": \"smtp.google.com\", \"priority\": 1}"
    ],
    "NS": [
        "dns1.p01.nsone.net",
        "dns4.p01.nsone.net",
        "dns3.p01.nsone.net",
        "dns2.p01.nsone.net"
    ],
    "SOA": "{\"nsname\": \"dns1.p01.nsone.net\", \"hostmaster\": \"domains+netlify.netlify.com\", \"serial\": 1788884447, \"refresh\": 43200, \"retry\": 7200, \"expire\": 1209600, \"minttl\": 3600}",
    "TXT": [
        "v=spf1 include:_spf.google.com ~all",
        "google-site-verification=vrnyx6RytJePnSAEvXLc7UaOoObPq-vxdwqnwxNRj2k"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "header": "max-age=31536000",
    "message": "HSTS header does not include all subdomains."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": "nosniff",
    "contentSecurityPolicy": false,
    "strictTransportPolicy": "max-age=31536000",
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "35.157.26.135",
    "family": 4
}
Redirects
{
    "chain": [
        "https://tornadomixer.org"
    ]
}
Registration record
{
    "registrar": "Name.com, Inc.",
    "created": "2026-09-08T16:20:49Z",
    "updated": "2026-09-13T16:21:42Z",
    "expires": "2027-09-08T16:20:49Z",
    "status": [
        "clientTransferProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "dns1.p01.nsone.net",
        "dns2.p01.nsone.net",
        "dns3.p01.nsone.net",
        "dns4.p01.nsone.net"
    ]
}
HTTP headers
{
    "headers": {
        "server": "Netlify",
        "content-type": "text/html; charset=utf-8",
        "x-powered-by": "Next.js",
        "strict-transport-security": "max-age=31536000",
        "x-content-type-options": "nosniff"
    }
}
Stored observation history3

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→live_content

    content_served

  2. VirusTotal · Detection count

    0→1

  3. Availability monitor · First collection record

    Reachable

Recorded activity

6 entries
  1. AlienVault OTX

    4 community references

    View source
  2. Google Safe Browsing

    No threat flag

    View source
  3. VirusTotal

    1/92 engine detections

    View source
  4. Abuse report sent

    PD-20261023-30722B

    abuse@name.com
  5. URLScan

    Page captured

    View source
  6. Added to PhishDestroy

    tornadomixer.org

    View source

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

tornadomixer.org

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 1 det. ChainPatrol URLQuery Report stored SSL Labs Stored certificate dates valid CF Radar Open report OTX 4 refs WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20261023-30722B Recipient: abuse@name.com
Page title stored with report: Tornado - Cryptocurrency Mixer
PDF notice generated
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 & reporting

Were You Affected by This Site?

6 evidence signal groups linked 1 stored notification records Last known active
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.

Immediate steps Find reporting contacts

Official reporting routes

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
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 tornadomixer.org)
  • 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

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
About this reportSources, observation dates and corrections

This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.

The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.

A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.

Request a correction or appeal How PhishDestroy works
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/tornadomixer.org"
  title="PhishDestroy threat report for tornadomixer.org"
  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>