Coop-Land.Ru - Info receives about 68,208 unique visitors and 315,804 (4.63 per visitor) page views per day which should earn about $500.73/day from advertising revenue. Estimated site value is $317,741.01. According to Alexa Traffic Rank is ranked number 15,485 in the world and 0.00402% of global Internet users visit it. Site is hosted in San Francisco, CA, 94107, United States and links to network IP address This server supports HTTPS and HTTP/2.

About -

Кооперативные игры, игры с мультиплеером - сетевыми режимами и совместным прохождением для друзей, как бесплатно играть по сети. Большой каталог игр и свежие новости. Информация о режимах, поиск друзей и прохождения, форум для обмена и поиска игр.
Edit Site Info

Technologies used on Website

Advertising Networks
DataLife Engine
Font Scripts
Font Awesome
Google Font API
JavaScript Frameworks
Programming Languages
Web Servers
Apache Profile

Title: - Страна кооперативных и сетевых игр
Description: Кооперативные игры, игры с мультиплеером - сетевыми режимами и совместным прохождением для друзей. Большой каталог игр, поиск напарников и форум с подбором игр.
Keywords: Кооперативные игры, совместное прохождение, инди, Coop, сетевые, бесплатно, по сети, мультиплеер, раздача, splitscreen, описание, онлайн, LAN, скачать
Last update was 20 days ago
This can take up to 60 seconds. Please wait...

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

How popular is

68.2K daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
Monthly Unique Visitors:
Pages per Visit:
Daily Pageviews:
Alexa Rank:
15,485 visit alexa
Alexa Reach:
0.00402%   (of global internet users)
Avg. visit duration:
Bounce rate:
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Traffic sources


Visitors by country

Russian Federation 62.6%60.2%1844
Ukraine 5.2%6.0%3119
Belarus 2.9%4.1%1852
Uzbekistan 2.7%3.9%1582
Kazakhstan 2.5%3.7%3069
Estonia 2.0%6.1%764
Viet Nam 1.7%2.2%13818
Latvia 1.4%0.6%2228

Where do visitors go on this site?


Competitive Data

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

+ Moz Data

Domain Authority:
Page Authority:

+ How socially engaged is

Google +:

+ Ad Experience Report

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

Desktop summary

Root domain:
Last Change Time:
(The last time that the site changed status.)
2018-12-11 15:10:21
(The Ad Standard region to which this site has been assigned.)
Ad filtering:
(Chrome is not filtering ads on your site.)
(The status of the site that is reviewed for the Better Ads Standards.)

Mobile summary

Last Change Time:
(The last time that the site changed status.)
2019-09-16 05:30:42
(The Ad Standard region to which this site has been assigned.)
Ad filtering:
(Ad filtering is pending.)
2019-10-16 05:30:42
(The status of the site that is reviewed for the Better Ads Standards.)

+ Abusive Experience Report

Root domain:
Last Change Time:
(The last time that the site changed status.)
2018-12-11 15:10:20
(Chrome is not preventing your site from opening new windows or tabs.)
(The status of the site reviewed for the abusive experiences.)

+ How much can earn?

Daily Revenue:
Monthly Revenue:
Yearly Revenue:
*All earnings values are estimates only.

Daily earning by country

Russian Federation 190,114$385.93
Estonia 19,264$40.26
Ukraine 18,948$25.96
Belarus 12,948$17.61
Uzbekistan 12,316$15.03
Kazakhstan 11,685$8.30
Viet Nam 6,948$5.07
Latvia 1,895$2.58

How much money do lose due to Adblock?

Daily Revenue Loss:
Monthly Revenue Loss:
Yearly Revenue Loss:
Daily Pageviews Blocked:
Monthly Pageviews Blocked:
Yearly Pageviews Blocked:
*All earnings values are estimates only.

Daily revenue loss by country

BlockedLost Money
Russian Federation 11,407$23.16
Estonia 5,009$10.47
Ukraine 2,463$3.37
Uzbekistan 1,971$2.40
Belarus 1,295$1.76
Latvia 322$0.44
Kazakhstan 351$0.25
Viet Nam 278$0.20

How much is worth?

Website Value:

+ Where is hosted?

Server IP:
Cloudflare Inc 
Server Location:
San Francisco
United States, US

Other sites hosted on

+ How fast does load?

Average Load Time:
(2510 ms) 32 % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

Currently Not Available

Page Speed (Google PageSpeed Insights) - Mobile

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.

First Contentful Paint (FCP)2.3s % of loads for this page have a fast (<1s) First Contentful Paint (FCP) 57% 33% of loads for this page have an average (1s ~ 2.5s) First Contentful Paint (FCP) 33% 8% of loads for this page have a slow (>2.5s) First Contentful Paint (FCP) 8%
First Input Delay (FID)279ms 78% of loads for this page have a fast (<50ms) First Input Delay (FID) 78% 13% of loads for this page have an average (50ms ~ 250ms) First Input Delay (FID) 13% 8% of loads for this page have a slow (>250ms) First Input Delay (FID) 8%

Origin Data

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

First Contentful Paint (FCP)2.1s 65% of loads for this page have a fast (<1s) First Contentful Paint (FCP) 65% 27% of loads for this page have an average (1s ~ 2.5s) First Contentful Paint (FCP) 27% 7% of loads for this page have a slow (>2.5s) First Contentful Paint (FCP) 7%
First Input Delay (FID)284ms % of loads for this page have a fast (<50ms) First Input Delay (FID) 75% 14% of loads for this page have an average 50ms ~ 250ms) First Input Delay (FID) 14% 9% of loads for this page have a slow (>250ms) First Input Delay (FID) 9%

Lab Data

Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 2.2 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 360 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 8.2 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
First Contentful Paint (3G) 4172 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 660 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Estimated Input Latency 90 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 4.9 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 7.3 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 2.2 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Avoids an excessive DOM size - 615 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](, and produce costly [layout reflows]( Learn more.

Total DOM Elements
Maximum DOM Depth
Maximum Child Elements
Avoid multiple page redirects - Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

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

TypeStart TimeDuration
Mark1646 ms0 ms
Mark1648 ms0 ms
Mark2316 ms0 ms
Mark2359 ms0 ms
Mark2367 ms0 ms
Mark2463 ms0 ms
Mark2463 ms0 ms
Mark2463 ms0 ms
Mark2479 ms0 ms
Mark2746 ms0 ms
Mark2749 ms0 ms
Mark2751 ms0 ms
Mark2791 ms0 ms
Mark2791 ms0 ms
Mark2791 ms0 ms
Mark2802 ms0 ms
Keep request counts low and transfer sizes small - 70 requests • 851 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
70851 KB
15456 KB
25255 KB
176 KB
424 KB
2122 KB
418 KB
00 KB
43533 KB
Eliminate render-blocking resources - Potential savings of 1,110 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

SizePotential Savings
3 KB180
7 KB180
7 KB180
38 KB930
2 KB180
Network Requests
Lists the network requests that were made during page load.

Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
0 ms203 ms0 KB0 KB301
203 ms717 ms10 KB39 KB200text/htmlDocument
738 ms768 ms3 KB6 KB200text/cssStylesheet
738 ms769 ms7 KB24 KB200text/cssStylesheet
739 ms780 ms7 KB30 KB200text/cssStylesheet
739 ms1288 ms38 KB158 KB200text/javascriptScript
739 ms768 ms6 KB5 KB200image/webpImage
740 ms846 ms10 KB10 KB200image/webpImage
880 ms911 ms9 KB9 KB200image/webpImage
908 ms932 ms3 KB2 KB200image/webpImage
912 ms947 ms15 KB14 KB200image/webpImage
933 ms972 ms14 KB14 KB200image/webpImage
948 ms984 ms10 KB10 KB200image/webpImage
973 ms1031 ms10 KB9 KB200image/webpImage
984 ms1026 ms15 KB15 KB200image/webpImage
1027 ms1057 ms13 KB12 KB200image/webpImage
1032 ms1063 ms11 KB10 KB200image/webpImage
1057 ms1083 ms2 KB1 KB200image/webpImage
740 ms783 ms2 KB4 KB200text/cssStylesheet
773 ms879 ms33 KB91 KB200application/javascriptScript
847 ms878 ms21 KB72 KB200application/javascriptScript
879 ms907 ms10 KB38 KB200application/javascriptScript
1064 ms1091 ms9 KB23 KB200application/javascriptScript
1083 ms1125 ms1 KB2 KB200application/javascriptScript
1092 ms1398 ms2 KB1 KB200image/pngImage
1339 ms1624 ms0 KB0 KB200application/jsonXHR
1342 ms1628 ms15 KB52 KB200application/javascriptScript
1376 ms1525 ms1 KB0 KB302
1384 ms1408 ms4 KB3 KB200image/webpImage
1386 ms1967 ms76 KB75 KB200application/octet-streamFont
1447 ms1472 ms2 KB1 KB200image/pngImage
1447 ms1542 ms15 KB14 KB200image/webpImage;r;s412*660*24;uhttps%3A//;0.2765634445991534
1497 ms2061 ms0 KB0 KB302text/html
1498 ms2337 ms40 KB133 KB200application/javascriptScript
1376 ms1525 ms1 KB0 KB302XHR
1526 ms1686 ms1 KB0 KB200application/jsonXHR
1643 ms2215 ms175 KB1095 KB200text/javascriptScript
1644 ms1969 ms17 KB64 KB200text/javascriptScript
2042 ms2310 ms4 KB11 KB200application/x-javascriptXHR;t21.6;r;s412*660*24;uhttps%3A//;0.2765634445991534
2061 ms2205 ms2 KB2 KB200image/gifImage
2438 ms2438 ms0 KB0 KB200image/svg+xmlImage
2485 ms2742 ms5 KB11 KB200application/x-javascriptXHR
2487 ms2782 ms55 KB55 KB200image/webpImage
2505 ms2645 ms8 KB29 KB200text/javascriptScript
2646 ms2809 ms1 KB0 KB302
2700 ms2843 ms0 KB0 KB200image/gifImage
2732 ms2876 ms6 KB22 KB200text/htmlDocument
2646 ms2809 ms2 KB0 KB302XHR
2809 ms2960 ms1 KB0 KB200application/jsonXHR
2817 ms2962 ms55 KB55 KB200image/webpImage
2826 ms3243 ms6 KB22 KB200text/htmlDocument
2894 ms3071 ms37 KB105 KB200application/javascriptScript
2894 ms3475 ms0 KB0 KB200image/pngImage
2963 ms2972 ms0 KB0 KB-1Other
2964 ms3108 ms1 KB0 KB200application/jsonXHR
2965 ms2972 ms0 KB0 KB-1Other
2965 ms2973 ms0 KB0 KB-1Other
3138 ms3284 ms40 KB133 KB200application/javascriptScript
3139 ms3313 ms1 KB0 KB200application/jsonFetch
3318 ms3327 ms10 KB24 KB200text/javascriptScript
3319 ms3339 ms1 KB0 KB302image/gif
3319 ms3339 ms1 KB0 KB302image/gif
3336 ms3480 ms1 KB0 KB200application/jsonXHR>d=
3339 ms3355 ms1 KB0 KB302image/gif>d=
3340 ms3356 ms1 KB0 KB302image/gif
3354 ms3366 ms2 KB2 KB200text/javascriptScript
3356 ms3382 ms1 KB0 KB200image/gifImage
3356 ms3370 ms1 KB0 KB200image/gifImage
3369 ms3387 ms1 KB0 KB200image/gifImage
3482 ms3491 ms0 KB0 KB200text/htmlDocument
Serve static assets with an efficient cache policy - 32 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

Cache TTLSize
3600000 ms40 KB
3600000 ms40 KB
3600000 ms38 KB
3600000 ms15 KB
3600000 ms0 KB
259200000 ms76 KB
259200000 ms33 KB
259200000 ms21 KB
259200000 ms15 KB
259200000 ms15 KB
259200000 ms15 KB
259200000 ms14 KB
259200000 ms13 KB
259200000 ms11 KB
259200000 ms10 KB
259200000 ms10 KB
259200000 ms10 KB
259200000 ms10 KB
259200000 ms9 KB
259200000 ms9 KB
259200000 ms7 KB
259200000 ms7 KB
259200000 ms6 KB
259200000 ms4 KB
259200000 ms3 KB
259200000 ms3 KB
259200000 ms2 KB
259200000 ms2 KB
259200000 ms2 KB
259200000 ms1 KB
604800000 ms55 KB
604800000 ms55 KB
Third-Party Usage - 5 Third-Parties Found
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.

SizeMain Thread Time
216 KB1490 ms
85 KB845 ms
96 KB631 ms
15 KB36 ms
2 KB0 ms
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
739 ms
14 ms
757 ms
6 ms
1309 ms
91 ms
1400 ms
41 ms
1446 ms
15 ms
1464 ms
12 ms
1477 ms
19 ms
1497 ms
14 ms
1512 ms
6 ms
1521 ms
18 ms
1649 ms
18 ms
1667 ms
10 ms
1988 ms
10 ms
1998 ms
35 ms
2037 ms
25 ms
2238 ms
59 ms
2330 ms
178 ms
2508 ms
11 ms
2533 ms
155 ms
2688 ms
19 ms
2729 ms
9 ms
2740 ms
11 ms
2761 ms
62 ms
2837 ms
7 ms
2897 ms
6 ms
2904 ms
10 ms
2979 ms
11 ms
2992 ms
24 ms
3098 ms
67 ms
3264 ms
7 ms
3273 ms
8 ms
3310 ms
15 ms
3336 ms
20 ms
3362 ms
12 ms
3496 ms
5 ms
3512 ms
7 ms
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Potential Savings
581 ms
Reduce JavaScript execution time - 3.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Total CPU TimeScript EvaluationScript Parse
1517 ms159 ms12 ms
1080 ms774 ms27 ms
845 ms734 ms61 ms
312 ms168 ms144 ms
265 ms238 ms10 ms
216 ms173 ms39 ms
143 ms116 ms5 ms
137 ms95 ms25 ms
97 ms90 ms7 ms
82 ms69 ms8 ms
68 ms52 ms14 ms
50 ms34 ms15 ms
Defer offscreen images - Potential savings of 94 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

SizePotential Savings
15 KB15 KB
14 KB14 KB
14 KB14 KB
12 KB12 KB
10 KB10 KB
10 KB10 KB
9 KB9 KB
9 KB9 KB
2 KB2 KB
Remove unused CSS - Potential savings of 28 KB
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.

SizePotential Savings
.fd5209c22{opacity:1 !important;white-space:normal !important;visibility:visible !important} ...
11 KB8 KB
7 KB7 KB
.dc9beafc5{opacity:1 !important;white-space:normal !important;visibility:visible !important} ...
9 KB6 KB
7 KB5 KB
3 KB2 KB
Avoids enormous network payloads - Total size was 851 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

175 KB
76 KB
55 KB
55 KB
40 KB
40 KB
38 KB
37 KB
33 KB
21 KB
Minimize main-thread work - 4.9 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.

Time Spent
Script Evaluation
2737 ms
Style & Layout
704 ms
692 ms
Script Parsing & Compilation
392 ms
202 ms
Parse HTML & CSS
93 ms
Garbage Collection
51 ms
Minimize Critical Requests Depth - 9 chains found
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.

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

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.

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.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. 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.

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 1 blocking script resources and 3 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.Remove render-blocking JavaScript:
Optimize CSS Delivery of the following:

Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources: (expiration not specified) (60 minutes) (60 minutes) (60 minutes) (3 days) (3 days) (3 days) (3 days) (3 days) (3 days) (3 days) (3 days) (3 days) (3 days) (3 days) (3 days) (3 days) (3 days) (3 days) (3 days) (3 days) (3 days)***_poster.jpg (3 days) (3 days) (3 days) (3 days) (3 days) (3 days) (3 days) (3 days) (3 days) (3 days)

Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 62.2KiB (57% reduction).

Compressing could save 23.8KiB (56% reduction).
Compressing could save 19.6KiB (62% reduction).
Compressing could save 14.7KiB (60% reduction).
Compressing could save 2.9KiB (56% reduction).
Compressing could save 831B (24% reduction).
Compressing could save 315B (21% reduction).

Reduce server response time

In our test, your server responded in 0.37 seconds.

There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.

Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and *** time.

Minify JavaScript for the following resources to reduce their size by 3.7KiB (15% reduction).

Minifying could save 3.7KiB (15% reduction) after compression.

Minify CSS

Compacting CSS code can save many bytes of data and speed up download and p*** times.

Minify CSS for the following resources to reduce their size by 230B (17% reduction).

Minifying could save 230B (17% reduction) after compression.

Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a href="https://coop-l…ser/Nightfall/">Nightfall</a> and 2 others are close to other tap targets.
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.
Configure the viewport
Your page specifies a viewport matching the device's size, which allows it to render properly on all devices. Learn more about configuring viewports.
Enable compression
You have compression enabled. Learn more about enabling compression.
Minify HTML
Your HTML is minified. Learn more about minifying HTML.
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.
Use legible font sizes
The text on your page is legible. Learn more about using legible font sizes.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does use compression? use gzip compression.
Original size: 94.15 KB
Compressed size: 22.5 KB
File reduced by: 71.65 KB (76%)

+ Google Safe Browsing

This site is not currently listed as suspicious Reputation Ratings

Vendor reliability:
Child safety:

+ SSL Checker - SSL Certificate Verify supports HTTPS
Verifying SSL Support. Please wait...
Common Name: COMODO ECC Certification Authority
Organization: COMODO CA Limited
Location: Salford, Greater Manchester, GB
Issuer: AddTrust External CA Root
Valid from: May 30 10:48:38 2000 GMT
Valid until: May 30 10:48:38 2020 GMT
Authority: Is a CA
Keysize: 832 Bits

+ Verify HTTP/2 Support supports HTTP/2
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Date: Sat, 23 Nov 2019 02:02:03 GMT
Transfer-Encoding: chunked
Connection: keep-alive
Cache-Control: max-age=3600
Expires: Sat, 23 Nov 2019 03:02:03 GMT
Vary: Accept-Encoding
Server: cloudflare
CF-RAY: 539f8f0acbcac63b-MSP

HTTP/1.1 200 OK
Date: Sat, 23 Nov 2019 02:02:04 GMT
Content-Type: text/html; charset=windows-1251
Transfer-Encoding: chunked
Connection: keep-alive
Set-Cookie: __cfduid=dcb84fef2d8b6c3bc2276e0ff22d6d0de1574474523; expires=Mon, 23-Dec-19 02:02:03 GMT; path=/;; HttpOnly; Secure
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Set-Cookie: PHPSESSID=b9m6osmumcig5ulsfcd9hu8rm2; path=/;; HttpOnly
X-Frame-Options: SAMEORIGIN
Strict-Transport-Security: max-age=86400; includeSubDomains
CF-Cache-Status: DYNAMIC
Expect-CT: max-age=604800, report-uri=""
Server: cloudflare
CF-RAY: 539f8f0dca4a4247-MSP
Content-Encoding: gzip

+ DNS Lookup

Type Ip Target TTL
HINFO 3600
NS 3599
NS 3599

+ Whois Lookup

Domain Created:
Domain Age:
8 years 2 months 15 days  

whois lookup at
% By submitting a query to RIPN's Whois Service
% you agree to abide by the following terms of use:
% (in Russian)
% (in English).

domain: COOP-LAND.RU
person: Private Person
registrar: REGRU-RU
created: 2011-09-07T18:22:29Z
paid-till: 2020-09-07T19:22:29Z
free-date: 2020-10-08
source: TCI

Last updated on 2019-09-30T13:01:33Z
Last update was 20 days ago
This can take up to 60 seconds. Please wait...

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

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) and we will remove/hide your site data manualy.


Install HypeStat extension in your browser to see statistics and technologies used with one click.
Make custom Widget for your website
Get the code now! widget