Tu.Tv - Info tu.tv

tu.tv receives about 1,306 unique visitors and 1,306 (1.00 per visitor) page views per day which should earn about $5.33/day from advertising revenue. Estimated site value is $3,358.77. According to Alexa Traffic Rank tu.tv is ranked number 743,324 in the world and 7.7E-5% of global Internet users visit it. Site is hosted in Hervás, Caceres, 10700, Spain and links to network IP address 149.36.226.226. This server doesn't support HTTPS and doesn't support HTTP/2.

About - tu.tv

Los mejores Videos de la Semana en Tu.tv, la mayor comunidad de videos en espa˝ol.
Edit Site Info

Technologies used on Website

Currently Not Available

tu.tv Profile

Title: Tu.tv - Tus videos en internet
Description: Copia el c├│digo y ponlo en tu web ... Agenda , Antivirus , Correo , Chat , Foros , Hispavista , Logos y Melod├şas , Postales , Solidaridad y ONGs , Tu web gratis , Videos tu.tv
Keywords: videos, ver online, ver video, video online, videos gratis,compartir video, videos musica, videos graciosos, trailers, videoclips
Last update was 246 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with tu.tv in any way. Only publicly available statistics data are displayed.

How popular is tu.tv?

1.3K daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
1,306
Monthly Unique Visitors:
31,344
Pages per Visit:
1.00
Daily Pageviews:
1,306
Alexa Rank:
743,324 visit alexa
Alexa Reach:
7.7E-5%   (of global internet users)
Avg. visit duration:
00:27
Bounce rate:
67.29%
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Traffic sources

Direct:
64.77%
Referral:
23.69%
Search:
6.88%
Social:
4.66%
Paid:
0%

Visitors by country

Users%Pageviews%Rank
Mexico 28.8%--
Spain 13.4%--
Argentina 9.0%--
Colombia 7.5%--
Peru 7.4%--
Venezuela 6.3%--
Chile 4.9%--
Ecuador 2.9%--
United States 2.8%--
Guatemala 2.0%--
Japan 1.9%--
Dominican Republic 1.7%--
El Salvador 1.2%--
Bolivia 0.8%--
Uruguay 0.8%--
Honduras 0.8%--
Nicaragua 0.7%--
Costa Rica 0.7%--
Puerto Rico 0.5%--
India 0.5%--

Where do visitors go on this site?

Reach%Pageviews%PerUser
tu.tv
87.83%87.83%1
OTHER
0%12.17%0

Competitive Data

SEMrush
Domain:
  tu.tv
Rank:
(Rank based on keywords, cost and organic traffic)
  n/a
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  0
Organic Traffic:
(Number of visitors coming from top 20 search results)
  0
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $0.00
Adwords Keywords:
(Keywords a website is buying in Google AdWords for ads that appear in paid search results)
  0
Adwords Traffic:
(Number of visitors brought to the website via paid search results)
  0
Adwords Cost:
(Estimated budget spent for buying keywords in Google AdWords for ads that appear in paid search results - monthly estimation)
  $0.00

+ Moz Data

Domain Authority:
  n/a
Page Authority:
  n/a
MozRank:
  n/a

+ How socially engaged is tu.tv?

Facebook:
  5
Google +:
  0
Linkedin:
  0
Stumbles:
  0
Buffer:
  0
Pins:
  0

+ Ad Experience Report

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

Desktop summary

Root domain:
tu.tv
Region:
(The Ad Standard region to which this site has been assigned.)
Pending
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


Mobile summary

Region:
(The Ad Standard region to which this site has been assigned.)
Pending
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

Root domain:
tu.tv
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

+ How much tu.tv can earn?

Daily Revenue:
$5.33
Monthly Revenue:
$159.90
Yearly Revenue:
$1,945.45
*All earnings values are estimates only.

Daily earning by country

PageviewsEarning
United States 37$0.42
Mexico 376$0.36
Spain 175$0.19
Argentina 118$0.14
Colombia 98$0.13
Peru 97$0.10
Japan 25$0.08
Chile 64$0.07
Venezuela 82$0.06
Ecuador 38$0.05
Dominican Republic 22$0.04
Puerto Rico 7$0.02
El Salvador 16$0.01
Guatemala 26$0.01
Uruguay 10$0.01
India 7$0.01
Nicaragua 9$0.01
Costa Rica 9$0.01
Bolivia 10$0.01
Honduras 10$0.00

How much money do tu.tv lose due to Adblock?

Daily Revenue Loss:
$0.21
Monthly Revenue Loss:
$6.34
Yearly Revenue Loss:
$77.17
Daily Pageviews Blocked:
130
Monthly Pageviews Blocked:
3,900
Yearly Pageviews Blocked:
47,445
*All earnings values are estimates only.

Daily revenue loss by country

BlockedLost Money
United States 7$0.08
Spain 33$0.04
Mexico 34$0.03
Argentina 16$0.02
Colombia 8$0.01
Peru 10$0.01
Chile 8$0.01
Ecuador 3$0.00
India 2$0.00
Japan 1$0.00
Venezuela 2$0.00
Dominican Republic 1$0.00
Uruguay 1$0.00
Puerto Rico 0$0.00
Costa Rica 1$0.00
El Salvador 1$0.00
Nicaragua 0$0.00
Honduras 1$0.00
Guatemala 1$0.00
Bolivia 0$0.00

How much is tu.tv worth?

Website Value:
$3,358.77

+ Where is tu.tv hosted?

Server IP:
149.36.226.226
ASN:
AS174 
ISP:
Cogent Communications 
Server Location:
Hervás
Caceres, CC
10700
Spain, ES
 

Other sites hosted on 149.36.226.226

+ How fast does tu.tv load?

Average Load Time:
(2779 ms) 28 % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

100
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a 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.

Origin Data

All pages served from this origin have an 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.

Lab Data

First CPU Idle 0.2 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 0.2 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 0.2 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 20 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 0.2 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Third-Party Usage
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Speed Index 0.2 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Avoids enormous network payloads - Total size was 1 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://tu.tv/
1 KB
Minimizes main-thread work - 0.0 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.

Category
Time Spent
Other
25 ms
Style & Layout
7 ms
Script Evaluation
5 ms
Parse HTML & CSS
2 ms
Rendering
2 ms
Script Parsing & Compilation
1 ms
Avoids an excessive DOM size - 23 elements
Browser engineers recommend pages contain fewer than ~1,500 DOM elements. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow). Learn more.

Statistic
ElementValue
Total DOM Elements
23
Maximum DOM Depth
4
Maximum Child Elements
8
Keep request counts low and transfer sizes small - 1 request ÔÇó 1 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Document
11 KB
Total
11 KB
Stylesheet
00 KB
Image
00 KB
Media
00 KB
Font
00 KB
Script
00 KB
Other
00 KB
Third-party
00 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://tu.tv/
0 ms192 ms1 KB1 KB200text/htmlDocument
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
216 ms
8 ms
224 ms
16 ms
243 ms
9 ms
Serve images in next-gen formats
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

Minimize Critical Requests Depth
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Preload key requests
Consider using to prioritize fetching resources that are currently requested later in page load. Learn more.

Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Server response times are low (TTFB) - Root document took 190 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Eliminate render-blocking resources
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

Uses efficient cache policy on static assets - 0 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

Network Round Trip Times - 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.

All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Preconnect to required origins
Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins. Learn more.

JavaScript execution time
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Server Backend Latencies - 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Remove unused CSS
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.


Page Speed (Google PageSpeed Insights) - Mobile

100
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a 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.

Origin Data

All pages served from this origin have an 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.

Lab Data

Max Potential First Input Delay 20 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 0.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Third-Party Usage
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.
First Contentful Paint (3G) 1230 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
Speed Index 0.7 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 0.6 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 0.6 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 0.6 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://tu.tv/
0 ms333 ms1 KB1 KB200text/htmlDocument
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
357 ms
9 ms
373 ms
7 ms
JavaScript execution time - 0.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
Other
108 ms11 ms4 ms
Avoids enormous network payloads - Total size was 1 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://tu.tv/
1 KB
Minimizes main-thread work - 0.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.

Category
Time Spent
Other
61 ms
Style & Layout
21 ms
Script Evaluation
12 ms
Rendering
5 ms
Script Parsing & Compilation
5 ms
Parse HTML & CSS
4 ms
Garbage Collection
2 ms
Avoids an excessive DOM size - 23 elements
Browser engineers recommend pages contain fewer than ~1,500 DOM elements. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow). Learn more.

Statistic
ElementValue
Total DOM Elements
23
Maximum DOM Depth
4
Maximum Child Elements
8
Keep request counts low and transfer sizes small - 1 request ÔÇó 1 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Document
11 KB
Total
11 KB
Stylesheet
00 KB
Image
00 KB
Media
00 KB
Font
00 KB
Script
00 KB
Other
00 KB
Third-party
00 KB
Eliminate render-blocking resources
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

Uses efficient cache policy on static assets - 0 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

Network Round Trip Times - 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.

All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Preconnect to required origins
Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Server Backend Latencies - 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Remove unused CSS
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

Serve images in next-gen formats
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

Minimize Critical Requests Depth
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Preload key requests
Consider using to prioritize fetching resources that are currently requested later in page load. Learn more.

Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Server response times are low (TTFB) - Root document took 330 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

Use legible font sizes

The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.

The following text fragments have a small font size. Increase the font size to make them more legible.

This domain is for sale! renders only 6 pixels tall (16 CSS pixels) .
Send us an offer E-mail: and 5 others render only 6 pixels tall (16 CSS pixels) .
dominios@corp.hispavista.com renders only 6 pixels tall (16 CSS pixels) .

Configure the viewport

Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.

Configure a viewport for this page.
Avoid landing page redirects
Your page has no redirects. Learn more about avoiding landing page redirects.
Avoid plugins
Your page does not appear to use plugins, which would prevent content from being usable on many platforms. Learn more about the importance of avoiding plugins.
Enable compression
You have compression enabled. Learn more about enabling compression.
Leverage browser caching
You have enabled browser caching. Learn more about browser caching recommendations.
Reduce server response time
Your server responded quickly. Learn more about server response time optimization.
Minify CSS
Your CSS is minified. Learn more about minifying CSS.
Minify HTML
Your HTML is minified. Learn more about minifying HTML.
Minify JavaScript
Your JavaScript content is minified. Learn more about minifying JavaScript.
Eliminate render-blocking JavaScript and CSS in above-the-fold content
You have no render-blocking resources. Learn more about removing render-blocking resources.
Optimize images
Your images are optimized. Learn more about optimizing images.
Prioritize visible content
You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.
Size content to viewport
The contents of your page fit within the viewport. Learn more about sizing content to the viewport.
Size tap targets appropriately
All of your page's links/buttons are large enough for a user to easily tap on a touchscreen. Learn more about sizing tap targets appropriately.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does tu.tv use compression?

tu.tv use gzip compression.
Original size: 548 B
Compressed size: 314 B
File reduced by: 234 B (42%)

+ Google Safe Browsing

This site is not currently listed as suspicious

MyWot.com Reputation Ratings

Trustworthiness:
  90
Vendor reliability:
  90
Privacy:
  90
Child safety:
  56

+ SSL Checker - SSL Certificate Verify

tu.tv does not support HTTPS
loader
Verifying SSL Support. Please wait...

+ Verify HTTP/2 Support

tu.tv does not support HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Date: Sun, 29 Sep 2019 02:11:03 GMT
Server: Apache
Vary: Accept-Encoding
Content-Encoding: gzip
Content-Length: 314
Content-Type: text/html

+ DNS Lookup

Type Ip Target TTL
MX mail.tu.tv 3600
TXT 3600
A 149.36.226.226 3600
SOA 3600
Mname ns1.hispavista.com
Rname dnsadmin.hispavista.com
Serial Number 2019053000
Refresh 43200
Retry 1800
Expire 1209600
Minimum TTL 0
NS ns1.hispavista.com 3582
NS ns2.hispavista.com 3582

+ Whois Lookup

Domain Created:
2006-11-15
Domain Age:
12 years 10 months 13 days  
WhoIs:
 

whois lookup at whois.nic.tv...
Domain Name: TU.TV
Registry Domain ID: 87171756_DOMAIN_TV-VRSN
Registrar WHOIS Server: whois.psi-usa.info
Registrar URL: http://www.psi-usa.info
Updated Date: 2018-01-03T10:29:55Z
Creation Date: 2006-11-15T17:17:58Z
Registry Expiry Date: 2019-11-15T17:17:58Z
Registrar: PSI-USA, Inc. dba Domain Robot
Registrar IANA ID: 151
Registrar Abuse Contact Email: email
Registrar Abuse Contact Phone: +49.94159559482
Domain Status: ok https://icann.org/epp#ok
Name Server: NS1.HISPAVISTA.COM
Name Server: NS2.HISPAVISTA.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2019-09-29T02:11:14Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

NOTICE: The expiration date displayed in this record is the date the
registrar's sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the
expiration date of the domain name registrant's agreement with the
sponsoring registrar. Users may consult the sponsoring registrar's
Whois database to view the registrar's reported date of expiration
for this registration.

TERMS OF USE: You are not authorized to access or query our Whois
database through the use of electronic processes that are high-volume and
automated except as reasonably necessary to register domain names or
modify existing registrations; the Data in VeriSign's ("VeriSign") Whois
database is provided by VeriSign for information purposes only, and to
assist persons in obtaining information about or related to a domain name
registration record. VeriSign does not guarantee its accuracy.
By submitting a Whois query, you agree to abide by the following terms of
use: You agree that you may use this Data only for lawful purposes and that
under no cir***stances will you use this Data to: (1) allow, enable, or
otherwise support the transmission of mass unsolicited, commercial
advertising or solicitations via e-mail, telephone, or facsimile; or
(2) enable high volume, automated, electronic processes that apply to
VeriSign (or its computer systems). The compilation, repackaging,
dissemination or other use of this Data is expressly prohibited without
the prior written consent of VeriSign. You agree not to use electronic
processes that are automated and high-volume to access or query the
Whois database except as reasonably necessary to register domain names
or modify existing registrations. VeriSign reserves the right to restrict
your access to the Whois database in its sole discretion to ensure
operational stability. VeriSign may restrict or terminate your access to the
Whois database for failure to abide by these terms of use. VeriSign
reserves the right to modify these terms at any time.
Last update was 246 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with tu.tv in any way. Only publicly available statistics data are displayed.

Recently Analyzed Sites

adinovis.com
12 secs
adirakminimarket.com
21 secs
***trex.com
37 secs
65chsmsm.com
56 secs
bailbondhollywood.com
1 min
adira.one
1 min
coinmagnet247.com
1 min
allamericanremodeling.com
2 mins
adi.net
3 mins
brattonscott.com
4 mins
WHAT WE RECOMMEND:
We are using the world's No. 1 Marketing Tool to grow our website. Activate your FREE trial today!

BrowserExtension

Install HypeStat extension in your browser to see statistics and technologies used with one click.

Hide/Remove your site data

• Use Show/Hide ESTIMATED data form to hide (Website worth, Daily ads revenue, Daily Visits, Daily Pageviews)
• Use Show/Hide WHOIS data form to hide whois data
• Use Remove form to remove all data
• If you have any problem with REMOVE/HIDE your data just drop an email at support (at) hypestat.com and we will remove/hide your site data manualy.
Make custom Widget for your website
Get the code now!
tu.tv widget