tornado.ws Tornado.ws

   
Tornado.cash

Domain Summary

What is the traffic rank for Tornado.ws?

• Tornado.ws ranks #4,369,075 globally on HypeStat.

What percent of global Internet users visit Tornado.ws?

• 2.0E-7% of global Internet users visit Tornado.ws

How many people visit Tornado.ws each day?

• Tornado.ws receives approximately 9 visitors and 17 page impressions per day.

Which countries does Tornado.ws receive most of its visitors from?

• Tornado.ws is mostly visited by people located in Viet Nam,Germany,Indonesia.

How much Tornado.ws can earn?

• Tornado.ws should earn about $0.01/day from advertising revenue.

What is Tornado.ws estimated value?

• Estimated value of Tornado.ws is $9.29.

What IP addresses does Tornado.ws resolve to?

• Tornado.ws resolves to the IP addresses 2606:4700:3030::6815:1001, 104.21.16.1.

tornado.ws Profile

Title:Tornado.cash Description:Non-custodial Ethereum Privacy solution.
Tags:
zksnark
decentralized
ethereum
smart contract
tornado
dapp
erc20
zero knowledge
metamask
Category:Finance / Investing
Edit Site Info

What technologies does tornado.ws use?

These are the technologies used at tornado.ws. tornado.ws has a total of 8 technologies installed in 8 different categories.
CDN
CloudFlare CloudFlare
Miscellaneous
HTTP/3 HTTP/3
Open Graph Open Graph
PWA PWA
Network Storage
IPFS IPFS
JavaScript Frameworks
Nuxt.js Nuxt.js
Vue.js Vue.js
Web Frameworks
Nuxt.js Nuxt.js
Web Servers
Nuxt.js Nuxt.js
Static Site Generator
Nuxt.js Nuxt.js
Programming Languages
Node.js Node.js

tornado.ws Traffic Analysis

Tornado.ws is ranked #4,369,075 in the world. This website is viewed by an estimated 9 visitors daily, generating a total of 17 pageviews. This equates to about 272.7 monthly visitors. Tornado.ws traffic has decreased by 83.09% compared to last month.
Daily Visitors9
87.86%
Monthly Visits272.7
83.09%
Pages per Visit1.81
12.11%
Visit duration00:37
89.02%
Bounce Rate41.14%
34.06%
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
9
Monthly Visits:
273
Pages per Visit:
1.81
Daily Pageviews:
17
Avg. visit duration:
00:37
Bounce rate:
41.14%
Global Reach:
2.0E-7%
Monthly Visits (SEMrush):
852
Monthly Unique Visitors (SEMrush):
602
Monthly Visits (SimilarWeb):
272
HypeRank:
4,369,075
SEMrush Rank:
8,071,689
SimilarWeb Rank:
6,055,919
*All traffic values are estimates only.

Traffic sources

Direct:
55.40%
Referral:
43.08%
Search:
1.53%
Social:
0%
Paid:
0%

Desktop vs Mobile

Desktop:
100.00%
Mobile:
0%

Total Visits Last 3 Months

11.7K
DEC
1.6K
JAN
272.7
FEB

Visitors by country

Country
Users%
 
Viet Nam 47.17%
 
Germany 29.55%
 
Indonesia 23.27%

Which sites are competitors to tornado.ws?

Websites similar to tornado.ws are sites similar on user interests and browsing behavior. Users can discover new websites that are similar to the ones they already enjoy or find useful.
Last update was 213 days ago
     
This can take up to 60 seconds. Please wait...

*HypeStat.com is not promoting or affiliated with tornado.ws in any way. Only publicly available statistics data are displayed.

Search Engine Indexes ▼

Search engine indexes are huge databases or collections of net pages that search engines like google like google and yahoo use to retrieve applicable facts while customers carry out searches. These indexes are created through search engines like google and yahoo through crawling and indexing net pages from throughout the internet.
Google Index:
167

  ▼

SEMrush is a complete on line advertising and marketing platform that gives a extensive variety of gear and functions to help companies and entrepreneurs in enhancing their on line visibility and optimizing their virtual advertising and marketing strategies.
SemRushSemRush
Domain:
  tornado.ws
Rank:
(Rank based on keywords, cost and organic traffic)
  8,071,689
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  19
Organic Traffic:
(Number of visitors coming from top 20 search results)
  8
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $23.00
Full SEMrush Report >>

Revenue report ▼

Google.com would generate approximately $0 per day if the source of income were advertisements, which equates to an estimated monthly revenue of $0.3 and annual gross revenue of approximately $3.7. Based on these figures, the site's net worth is estimated at around $9.3.

How much would tornado.ws make?

Daily Revenue:
$0.01
Monthly Revenue:
$0.30
Yearly Revenue:
$3.65
*All earnings values are estimates only.

Daily earning by country

 
CountryPageviewsEarning
 
Germany 5$0.01
 
Viet Nam 8$0.00
 
Indonesia 4$0.00

Daily revenue loss by country

 
CountryBlockedLost Money
 
Germany 1$0.00
 
Indonesia 2$0.00
 
Viet Nam 0$0.00

How much is tornado.ws worth?

Website Value:
$9.3

Ad Experience Report ▼

Summary of the ad experience rating of a website for a specific platform.

Mobile summary

Root domain:
tornado.ws
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

Desktop summary

Root domain:
tornado.ws
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

Abusive Experience Report ▼

Summary of the abusive experience rating of a website.
Root domain:
tornado.ws
Enforcement:
(Chrome is not preventing your site from opening new windows or tabs.)
Off
Status:
(The status of the site reviewed for the abusive experiences.)
Not reviewed

Where is tornado.ws hosted? ▼

Tornado.ws may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.

How fast does tornado.ws load? ▼

The average loading time of tornado.ws is 69 ms. The Desktop speed index is 40 and mobile speed index is 37.
Average Load Time:
69 ms

Page Speed (Google PageSpeed Insights) - Desktop

40
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a SLOW speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Cumulative Layout Shift (CLS)0ms 95% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 95% 2% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 2% 1% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 1%
Time To First Byte (TTFB)604ms 80% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 80% 15% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 15% 3% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 3%
First Contentful Paint (FCP)4.8s 29% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 29% 24% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 24% 45% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 45%
First Input Delay (FID)0 0% of loads for this page have a fast (<0ms) First Input Delay (FID) 0% 0% of loads for this page have an average (0ms ~ 0ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>0ms) First Input Delay (FID) 0%
Interaction To Next Paint (INP)77ms 92% of loads for this page have a fast (<200ms) Interaction To Next Paint (INP) 92% 5% of loads for this page have an average (200ms ~ 500ms) Interaction To Next Paint (INP) 5% 2% of loads for this page have a slow (>500ms) Interaction To Next Paint (INP) 2%
Largest Contentful Paint (LCP)4.6s 45% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 45% 22% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 22% 32% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 32%

Origin Data

All pages served from this origin have an FAST speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Cumulative Layout Shift (CLS)0ms 97% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 97% 1% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 1% 1% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 1%
Time To First Byte (TTFB)489ms 83% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 83% 9% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 9% 6% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 6%
First Contentful Paint (FCP)964ms 87% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 87% 5% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 5% 6% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 6%
First Input Delay (FID)0 0% of loads for this page have a fast (<0ms) First Input Delay (FID) 0% 0% of loads for this page have an average 0ms ~ 0ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>0ms) First Input Delay (FID) 0%
Interaction To Next Paint (INP)45ms 96% of loads for this page have a fast (<200ms) Interaction To Next Paint (INP) 96% 1% of loads for this page have an average (200ms ~ 500ms) Interaction To Next Paint (INP) 1% 1% of loads for this page have a slow (>500ms) Interaction To Next Paint (INP) 1%
Largest Contentful Paint (LCP)1.1s 89% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 89% 5% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 5% 4% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 4%

Lab Data

Long critical network tree  
by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Avoid chaining critical requests
First Meaningful Paint  
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
INP by phase  
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
LCP request discovery  
Optimize LCP by making the LCP image from the HTML immediately, and discoverable avoiding lazy-loading
Max Potential First Input Delay 2,350 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric
Total Blocking Time 2,550 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric
Largest Contentful Paint image was not lazily loaded  
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading
Preload Largest Contentful Paint image  
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements
Font display  
Consider setting to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with . font-display font metric overrides
Speed Index 2.7 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
First Contentful Paint 0.4 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
CSS Selector costs  
If Recalculate Style costs remain high, selector optimization can reduce them. with both high elapsed time and high slow-path %. Simpler selectors, fewer selectors, a smaller DOM, and a shallower DOM will all reduce matching costs. Optimize the selectors
Improve image delivery  
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Largest Contentful Paint 5.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Time to Interactive 5.8 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric
Forced reflow  
Many APIs, typically reading layout geometry, force the rendering engine to pause script execution in order to calculate the style and layout. Learn more about and its mitigations. forced reflow
Render blocking requests  
Requests are blocking the page's initial render, which may delay LCP. can move these network requests out of the critical path. Deferring or inlining
Lazy load third-party resources with facades  
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade

Page Speed (Google PageSpeed Insights) - Mobile

37
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a AVERAGE speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Cumulative Layout Shift (CLS)0ms 95% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 98% 0% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)541ms 80% of loads for this page have a fast (<800s) Time To First Byte (TTFB) 83% 11% of loads for this page have an average (800s ~ 1800s) Time To First Byte (TTFB) 11% 5% of loads for this page have a slow (>1800s) Time To First Byte (TTFB) 5%
First Contentful Paint (FCP)1.1s 29% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 88% 6% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 6% 5% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 5%
First Input Delay (FID)0 0% of loads for this page have a fast (<0ms) First Input Delay (FID) 0% 0% of loads for this page have an average (0ms ~ 0ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>0ms) First Input Delay (FID) 0%
Interactive To Next Paint (INP)261ms 92% of loads for this page have a fast (<200s) Interactive To Next Paint (INP) 64% 33% of loads for this page have an average (200s ~ 500s) Interactive To Next Paint (INP) 33% 2% of loads for this page have a slow (>500s) Interactive To Next Paint (INP) 2%
Largest Contentful Paint (LCP)1.2s 45% of loads for this page have a fast (<2500s) Largest Contentful Paint (LCP) 93% 3% of loads for this page have an average (2500s ~ 4000s) Largest Contentful Paint (LCP) 3% 3% of loads for this page have a slow (>4000s) Largest Contentful Paint (LCP) 3%

Origin Data

All pages served from this origin have an AVERAGE speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Cumulative Layout Shift (CLS)0ms 98% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 98% 0% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)541ms 83% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 83% 11% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 11% 5% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 5%
First Contentful Paint (FCP)1.1s 88% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 88% 6% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 6% 5% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 5%
First Input Delay (FID)0 0% of loads for this page have a fast (<0ms) First Input Delay (FID) 0% 0% of loads for this page have an average 0ms ~ 0ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>0ms) First Input Delay (FID) 0%
Interactive To Next Paint (INP)261ms 64% of loads for this page have a fast (<0.2s) Interactive To Next Paint (INP) 64% 33% of loads for this page have an average (0.2s ~ 0.5s) Interactive To Next Paint (INP) 33% 2% of loads for this page have a slow (>0.5s) Interactive To Next Paint (INP) 2%
Largest Contentful Paint (LCP)1.2s 93% of loads for this page have a fast (<2.5s)Largest Contentful Paint (LCP) 93% 3% of loads for this page have an average (2.5s ~ 4s)Largest Contentful Paint (LCP) 3% 3% of loads for this page have a slow (>4s)Largest Contentful Paint (LCP) 3%

Lab Data

Max Potential First Input Delay 3,470 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric
Largest Contentful Paint 21.2 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
First Contentful Paint 1.6 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
Time to Interactive 21.2 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric
Speed Index 8.4 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Total Blocking Time 3,820 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric
Largest Contentful Paint image was not lazily loaded  
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading
Preload Largest Contentful Paint image  
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements
Lazy load third-party resources with facades  
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade
First Meaningful Paint  
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric

Does tornado.ws use compression? ▼

Website compression is the process of reducing the size of website files, such as HTML, CSS, JavaScript, and image files, to improve website performance and load times. Compressing website files can significantly reduce the amount of data that needs to be transferred from the server to the user's browser, resulting in faster page load times and improved user experience. Files on tornado.ws are reduced by 74%.
tornado.ws use br compression.
Original size: 5.96 KB
Compressed size: 1.49 KB
File reduced by: 4.47 KB (74%)

Google Safe Browsing ▼

Google Safe Browsing is a service provided by Google that helps protect users from visiting websites that may contain malicious or harmful content, such as malware, phishing attempts, or deceptive software.
This site is not currently listed as suspicious

MyWot.com Reputation Ratings

MyWOT (short for "My Web of Trust") is a web-based reputation and rating service that provides users with information about the trustworthiness and safety of websites.
Status:
  SAFE

SSL Checker - SSL Certificate Verify ▼

An SSL (Secure Sockets Layer) certificate is a digital certificate that establishes a secure encrypted connection between a web server and a user's web browser. It provides authentication and encryption, ensuring that data transmitted between the server and the browser remains private and protected. tornado.ws supports HTTPS.
 tornado.ws supports HTTPS
     
Verifying SSL Support. Please wait...
Common Name: ipfs.io
Organization:
Location:
Issuer: WE1
Valid from: Feb 6 08:39:23 2025 GMT
Valid until: May 7 09:38:57 2025 GMT
Authority: CA:FALSE
Keysize:
Common Name: WE1
Organization: Google Trust Services
Location: US
Issuer: GTS Root R4
Valid from: Dec 13 09:00:00 2023 GMT
Valid until: Feb 20 14:00:00 2029 GMT
Authority: CA:TRUE
Keysize:
Common Name: GTS Root R4
Organization: Google Trust Services LLC
Location: US
Issuer: GlobalSign Root CA
Valid from: Nov 15 03:43:21 2023 GMT
Valid until: Jan 28 00:00:42 2028 GMT
Authority: CA:TRUE
Keysize:

Verify HTTP/2 Support ▼

HTTP/2 (Hypertext Transfer Protocol version 2) is a major revision of the HTTP protocol, which is the foundation of data communication on the World Wide Web. It was developed as an improvement over the previous HTTP/1.1 version to enhance web performance and efficiency.
 tornado.ws supports HTTP/2
     
Verifying HTTP/2.0 Support. Please wait...

Http Header ▼

HTTP headers are extra portions of records despatched among a consumer (which include an internet browser) and a server at some stage in an HTTP request or response. They offer instructions, metadata, or manipulate parameters for the conversation among the consumer and server. 
date: Tue, 01 Apr 2025 16:22:26 GMT
content-type: text/html
content-length: 167
location: https://ipfs.io/ipfs/bafybeib4rg5gx7plrvzasrrqa3tcb3tnzm2goxhteaxsbem6hjpzsgihbu/
cache-control: max-age=3600
expires: Tue, 01 Apr 2025 17:22:26 GMT
report-to: {"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=2vhN4SqVFw9z7IvD05SmzQHGgb2nKcmPbq6MER0OlkqQSadMEZBblhVcr9kQkZgk4yVo1OF3K6k0awlSHXc4z4v8ml0Mxr%2B9OKEVJ%2BuXkzlUCojRc97ytwoOE%2Bns"}],"group":"cf-nel","max_age":604800}
nel: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
vary: Accept-Encoding
server: cloudflare
cf-ray: 92996ce0c9cfeabf-ORD

HTTP/2 200 
date: Tue, 01 Apr 2025 16:22:26 GMT
content-type: text/html
access-control-allow-headers: Content-Type
access-control-allow-headers: Range
access-control-allow-headers: User-Agent
access-control-allow-headers: X-Requested-With
access-control-allow-methods: GET
access-control-allow-methods: HEAD
access-control-allow-methods: OPTIONS
access-control-allow-origin: *
access-control-expose-headers: Content-Length
access-control-expose-headers: Content-Range
access-control-expose-headers: X-Chunked-Output
access-control-expose-headers: X-Ipfs-Path
access-control-expose-headers: X-Ipfs-Roots
access-control-expose-headers: X-Stream-Output
cache-control: public, max-age=29030400, immutable
x-ipfs-path: /ipfs/bafybeib4rg5gx7plrvzasrrqa3tcb3tnzm2goxhteaxsbem6hjpzsgihbu/
x-ipfs-roots: bafybeib4rg5gx7plrvzasrrqa3tcb3tnzm2goxhteaxsbem6hjpzsgihbu
x-ipfs-pop: rainbow-dc13-01
cf-cache-status: HIT
age: 30220
vary: Accept-Encoding
x-robots-tag: noindex, nofollow
server: cloudflare
cf-ray: 92996ce0ef681183-ORD
content-encoding: br
alt-svc: h3=":443"; ma=86400

DNS Lookup ▼

DNS entries (Domain Name System) are a critical component of the Internet infrastructure. They act as directories that translate human-readable domain names (such as example.com) to machine-readable IP addresses. DNS records are stored on DNS servers and help forward internet traffic efficiently.
Type Ip Target/Txt TTL
AAAA 2606:4700:3030::6815:6001 229
AAAA 2606:4700:3030::6815:7001 229
AAAA 2606:4700:3030::6815:4001 229
AAAA 2606:4700:3030::6815:5001 229
AAAA 2606:4700:3030::6815:2001 229
AAAA 2606:4700:3030::6815:3001 229
AAAA 2606:4700:3030::6815:1001 229
A 104.21.48.1 229
A 104.21.112.1 229
A 104.21.80.1 229
A 104.21.16.1 229
A 104.21.32.1 229
A 104.21.64.1 229
A 104.21.96.1 229
NS ollie.ns.cloudflare.com 21529
NS gabriel.ns.cloudflare.com 21529
HINFO 3600

Whois Lookup ▼

Domain WHOIS is a public database that provides information about domain names, including registered owners, contact information, domain registrars, registration and expiration dates, name servers, and other relevant information. Domain registration for this website began on May 1, 2023 and will expire on May 1, 2026 if not renewed. This website is now assigned through the registrar Key-Systems GmbH. The WHOIS data for this website's domain was last updated on April 17, 2024.
Domain Created:
2023-05-01
Domain Expires:
2026-05-01
Domain Updated:
2024-04-17
Domain Age:
2 years 5 months 30 days
Domain Registrar:
Key-Systems GmbH
Domain Owner:
c/o whoisproxy.com
WhoIs:
 

Domain Name: tornado.ws
Registry Domain ID: 6E5B8ED70902C150E050010AAC011AF0-GDI
Registrar WHOIS Server: whois.rrpproxy.net
Registrar URL: http://www.reg.ru
Updated Date: 2024-04-17T12:46:44Z
Creation Date: 2023-05-01T16:42:07Z
Registrar Registration Expiration Date: 2026-05-01T16:42:07Z
Registrar: Key-Systems GmbH
Registrar IANA ID: 269
Registrar Abuse Contact Email: email
Registrar Abuse Contact Phone: +49.68949396850
Domain Status: ok https://icann.org/epp#ok
Registry Registrant ID: Not Available From Registry
Registrant Name: On behalf of tornado.ws OWNER 
Registrant Organization: c/o whoisproxy.com
Registrant Street: 604 Cameron Street
Registrant City: Alexandria
Registrant State/Province: VA
Registrant Postal Code: 22314
Registrant Country: US
Registrant Phone: +64.48319528
Registrant Phone Ext: 
Registrant Fax: 
Registrant Fax Ext: 
Registrant Email: email
Registry Admin ID: Not Available From Registry
Admin Name: On behalf of tornado.ws ADMIN 
Admin Organization: c/o whoisproxy.com
Admin Street: 604 Cameron Street
Admin City: Alexandria
Admin State/Province: VA
Admin Postal Code: 22314
Admin Country: US
Admin Phone: +64.48319528
Admin Phone Ext: 
Admin Fax: 
Admin Fax Ext: 
Admin Email: email
Registry Tech ID: Not Available From Registry
Tech Name: On behalf of tornado.ws TECH 
Tech Organization: c/o whoisproxy.com
Tech Street: 604 Cameron Street
Tech City: Alexandria
Tech State/Province: VA
Tech Postal Code: 22314
Tech Country: US
Tech Phone: +64.48319528
Tech Phone Ext: 
Tech Fax: 
Tech Fax Ext: 
Tech Email: email
Registry Billing ID: Not Available From Registry
Billing Name: On behalf of tornado.ws BILLING 
Billing Organization: c/o whoisproxy.com
Billing Street: 604 Cameron Street
Billing City: Alexandria
Billing State/Province: VA
Billing Postal Code: 22314
Billing Country: US
Billing Phone: +64.48319528
Billing Phone Ext: 
Billing Fax: 
Billing Fax Ext: 
Billing Email: email
Name Server: gabriel.ns.cloudflare.com 
Name Server: ollie.ns.cloudflare.com 
DNSSEC: unsigned
Whoisprivacy: 1
URL of the ICANN WHOIS Data Problem Reporting System: https://wdprs.internic.net/
>>> Last update of WHOIS database: 2025-03-15T17:38:59Z