Fotw.Xyz - Info fotw.xyz

fotw.xyz receives about 89,926 unique visitors and 125,897 (1.40 per visitor) page views per day which should earn about $542.61/day from advertising revenue. Estimated site value is $396,103.38. According to Alexa Traffic Rank fotw.xyz is ranked number 17,497 in the world and 0.0053% of global Internet users visit it. Site is hosted in Phoenix, Arizona, 85001, United States and links to network IP address 131.153.42.226. This server supports HTTPS and doesn't support HTTP/2.

About - fotw.xyz


Technologies used on Website

Web Servers
Nginx
Reverse Proxy
Nginx

fotw.xyz Profile

Last update was 28 days ago
loader
This can take up to 60 seconds. Please wait...

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

How popular is fotw.xyz?

89.9K daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
89,926
Monthly Unique Visitors:
2,158,224
Pages per Visit:
1.40
Daily Pageviews:
125,897
Alexa Rank:
17,497 visit alexa
Alexa Reach:
0.0053%   (of global internet users)
Avg. visit duration:
00:00
Bounce rate:
n/a
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Visitors by country

Users%Pageviews%Rank
United States 12.3%24.6%7005
Germany 6.7%5.3%3797
Spain 6.1%5.5%2019
Brazil 5.2%4.6%4614
India 5.1%4.1%11133
Italy 4.1%3.6%3266
Peru 2.7%2.7%834
Japan 2.5%1.9%18125
Saudi Arabia 2.3%2.9%1918
Taiwan 2.3%1.8%3975
United Kingdom 2.0%1.6%6727
Argentina 2.0%1.4%3417
Australia 2.0%1.5%5304
Mexico 1.9%1.6%5911
Korea, Republic of 1.7%1.2%8141
Viet Nam 1.7%1.3%2691
Algeria 1.3%1.1%2440
Pakistan 1.2%1.1%5698
Canada 1.2%0.9%13383
Venezuela 1.2%1.0%3231
Russian Federation 1.2%1.0%17270
Singapore 1.2%0.9%3312
Colombia 1.2%1.1%3292
Hong Kong 1.0%1.5%3963
Ireland 1.0%0.9%1828
Ukraine 1.0%1.1%2941
Turkey 0.9%0.7%11332
Egypt 0.9%0.6%7433
Bangladesh 0.9%0.7%3084
Malaysia 0.8%0.7%3854
Netherlands 0.8%0.6%7389
Indonesia 0.8%0.8%7146
Israel 0.7%0.9%2760
Thailand 0.6%0.4%5768
Dominican Republic 0.6%0.6%1795
Puerto Rico 0.6%0.4%972

Where do visitors go on this site?

Reach%Pageviews%PerUser
fotw.xyz
55.82%48.81%1.2
r.fotw.xyz
44.30%50.69%1.6
OTHER
0%0.49%0

Competitive Data

SEMrush
Domain:
  fotw.xyz
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 fotw.xyz?

Facebook:
  0
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:
fotw.xyz
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:
fotw.xyz
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 fotw.xyz can earn?

Daily Revenue:
$542.61
Monthly Revenue:
$16,278.30
Yearly Revenue:
$198,052.65
*All earnings values are estimates only.

Daily earning by country

PageviewsEarning
United States 30,971$355.23
Germany 6,673$32.23
Italy 4,532$15.82
Australia 1,888$14.22
United Kingdom 2,014$12.55
Brazil 5,791$10.25
India 5,162$8.26
Canada 1,133$7.94
Spain 6,924$7.69
Japan 2,392$7.65
Saudi Arabia 3,651$7.38
Israel 1,133$6.62
Hong Kong 1,888$6.52
Ireland 1,133$5.62
Taiwan 2,266$4.31
Netherlands 755$3.84
Peru 3,399$3.64
Korea, Republic of 1,511$3.50
Singapore 1,133$3.39
Malaysia 881$2.67
Russian Federation 1,259$2.56
Argentina 1,763$2.10
Mexico 2,014$1.95
Ukraine 1,385$1.90
Colombia 1,385$1.84
Puerto Rico 504$1.68
Pakistan 1,385$1.47
Dominican Republic 755$1.26
Thailand 504$1.26
Algeria 1,385$1.25
Indonesia 1,007$1.24
Viet Nam 1,637$1.19
Bangladesh 881$1.18
Turkey 881$0.96
Venezuela 1,259$0.84
Egypt 755$0.61

How much money do fotw.xyz lose due to Adblock?

Daily Revenue Loss:
$98.80
Monthly Revenue Loss:
$2,963.88
Yearly Revenue Loss:
$36,060.58
Daily Pageviews Blocked:
17,544
Monthly Pageviews Blocked:
526,312
Yearly Pageviews Blocked:
6,403,468
*All earnings values are estimates only.

Daily revenue loss by country

BlockedLost Money
United States 5,575$63.94
Germany 1,935$9.35
Australia 378$2.84
Italy 770$2.69
India 1,445$2.31
Ireland 442$2.19
United Kingdom 322$2.01
Canada 283$1.99
Saudi Arabia 767$1.55
Spain 1,316$1.46
Israel 215$1.26
Singapore 329$0.98
Indonesia 584$0.72
Taiwan 363$0.69
Netherlands 128$0.65
Hong Kong 189$0.65
Brazil 347$0.62
Pakistan 443$0.47
Peru 340$0.36
Argentina 247$0.29
Ukraine 180$0.25
Japan 72$0.23
Malaysia 71$0.21
Mexico 181$0.18
Russian Federation 76$0.15
Colombia 111$0.15
Korea, Republic of 60$0.14
Puerto Rico 25$0.08
Thailand 30$0.08
Turkey 62$0.07
Algeria 69$0.06
Dominican Republic 30$0.05
Viet Nam 65$0.05
Egypt 38$0.03
Venezuela 38$0.03
Bangladesh 18$0.02

How much is fotw.xyz worth?

Website Value:
$396,103.38

+ Where is fotw.xyz hosted?

Server IP:
131.153.42.226
ASN:
AS20454 
ISP:
SECURED SERVERS LLC 
Server Location:
Phoenix
Arizona, AZ
85001
United States, US
 

Other sites hosted on 131.153.42.226

There are no other sites hosted on this IP

+ How fast does fotw.xyz load?

Average Load Time:
(1006 ms) 78 % 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

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

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://fotw.xyz/
0 ms146 ms0 KB0 KB200text/plainDocument
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
170 ms
11 ms
182 ms
9 ms
Avoids enormous network payloads - Total size was 0 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://fotw.xyz/
0 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
9 ms
Style & Layout
8 ms
Script Parsing & Compilation
5 ms
Script Evaluation
3 ms
Rendering
1 ms
Parse HTML & CSS
1 ms
Avoids an excessive DOM size - 1 element
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
1
Maximum DOM Depth
2
Maximum Child Elements
1
Keep request counts low and transfer sizes small - 1 request • 0 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Document
10 KB
Total
10 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.

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

Efficiently encode images
Optimized images load faster and consume less cellular data. 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.

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.

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 150 ms
Time To First Byte identifies the time at which your server sends a response. 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

Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
First Contentful Paint (3G) 1253 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. 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.
Speed Index 0.7 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 0.7 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.7 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.7 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.7 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.

Screenshot Thumbnails

This is what the load of your site looked like.

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
110 ms8 ms3 ms
Avoids enormous network payloads - Total size was 0 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://fotw.xyz/
0 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
Style & Layout
43 ms
Other
41 ms
Rendering
11 ms
Script Evaluation
8 ms
Script Parsing & Compilation
3 ms
Parse HTML & CSS
2 ms
Avoids an excessive DOM size - 1 element
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
1
Maximum DOM Depth
2
Maximum Child Elements
1
Keep request counts low and transfer sizes small - 1 request • 0 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Document
10 KB
Total
10 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://fotw.xyz/
0 ms159 ms0 KB0 KB200text/plainDocument
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
187 ms
8 ms
198 ms
11 ms
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.

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.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. 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 160 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.

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

Efficiently encode images
Optimized images load faster and consume less cellular data. 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.

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.

p&lt;script src=&quot;…39;&quot;&gt;&lt;/script&gt; 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 fotw.xyz use compression?

fotw.xyz does not use compression.
Original size: 1 B
Compressed size: n/a
File reduced by: n/a

+ Google Safe Browsing

This site is not currently listed as suspicious

MyWot.com Reputation Ratings

Trustworthiness:
  n/a
Vendor reliability:
  n/a
Privacy:
  n/a
Child safety:
  n/a

+ SSL Checker - SSL Certificate Verify

fotw.xyz supports HTTPS
loader
Verifying SSL Support. Please wait...
Common Name: fotw.xyz
Organization:
Location:
Issuer: Let's Encrypt Authority X3
Valid from: Sep 1 08:01:03 2019 GMT
Valid until: Nov 30 08:01:03 2019 GMT
Authority:
Keysize:

+ Verify HTTP/2 Support

fotw.xyz does not support HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Server: nginx
Date: Tue, 22 Oct 2019 16:23:03 GMT
Content-Type: application/octet-stream
Content-Length: 1
Connection: keep-alive
Content-type: text/plain

+ DNS Lookup

Type Ip Target TTL
HINFO 3600
A 23.235.244.224 286
A 131.153.42.211 286
A 23.235.244.226 286
A 23.235.244.212 286
A 131.153.42.226 286
A 131.153.42.224 286
A 23.235.244.225 286
A 131.153.42.225 286
NS brad.ns.cloudflare.com 3586
NS erin.ns.cloudflare.com 3586

+ Whois Lookup

Domain Created:
2019-06-26
Domain Age:
3 months 26 days  
WhoIs:
 

whois lookup at whois.nic.xyz...
Domain Name: FOTW.XYZ
Registry Domain ID: D110130521-CNIC
Registrar WHOIS Server: whois.namecheap.com
Registrar URL: https://namecheap.com
Updated Date: 2019-07-01T19:20:33.0Z
Creation Date: 2019-06-26T07:24:58.0Z
Registry Expiry Date: 2020-06-26T23:59:59.0Z
Registrar: Namecheap
Registrar IANA ID: 1068
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registrant Organization: WhoisGuard, Inc.
Registrant State/Province: Panama
Registrant Country: PA
Registrant Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Admin Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Tech Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Name Server: BRAD.NS.CLOUDFLARE.COM
Name Server: ERIN.NS.CLOUDFLARE.COM
DNSSEC: unsigned
Billing Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registrar Abuse Contact Email: email
Registrar Abuse Contact Phone:
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2019-10-22T16:23:17.0Z <<<

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

>>> IMPORTANT INFORMATION ABOUT THE DEPLOYMENT OF RDAP: please visit
https://www.centralnic.com/support/rdap <<<

The Whois and RDAP services are provided by CentralNic, and contain
information pertaining to Internet domain names registered by our
our customers. By using this service you are agreeing (1) not to use any
information presented here for any purpose other than determining
ownership of domain names, (2) not to store or reproduce this data in
any way, (3) not to use any high-volume, automated, electronic processes
to obtain data from this service. Abuse of this service is monitored and
actions in contravention of these terms will result in being permanently
blacklisted. All data is (c) CentralNic Ltd (https://www.centralnic.com)

Access to the Whois and RDAP services is rate limited. For more
information, visit https://registrar-console.centralnic.com/pub/whois_guidance.
Last update was 28 days ago
loader
This can take up to 60 seconds. Please wait...

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

Recently Analyzed Sites

vissmann.de
15 secs
musicnsw.com
26 secs
mariemary1.wordpress.com
36 secs
***toyssupermart.com
48 secs
adminamerica.com
1 min
sougouwiki.com
2 mins
accutrolllc.com
2 mins
mmc.edu.au
2 mins
aapcb.com
3 mins
vissmann.com
3 mins

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!
fotw.xyz widget