e-health.kz E-health.kz

   
IIS Windows Server

Domain Summary

What percent of global Internet users visit E-health.kz?

• 6.0E-7% of global Internet users visit E-health.kz

How many people visit E-health.kz each day?

• E-health.kz receives approximately 29 visitors and 29 page impressions per day.

How much E-health.kz can earn?

• E-health.kz should earn about $0.12/day from advertising revenue.

What is E-health.kz estimated value?

• Estimated value of E-health.kz is $127.69.

What IP addresses does E-health.kz resolve to?

• E-health.kz resolves to the IP addresses 109.233.110.108.

Where are E-health.kz servers located in?

• E-health.kz has servers located in Kazakhstan.

e-health.kz Profile

Title:IIS Windows Server
Edit Site Info

What technologies does e-health.kz use?

These are the technologies used at e-health.kz. e-health.kz has a total of 2 technologies installed in 2 different categories.
Web Servers
IIS IIS
Operating Systems
Windows Server Windows Server

e-health.kz Traffic Analysis

This website is viewed by an estimated 29 visitors daily, generating a total of 29 pageviews. This equates to about 878.7 monthly visitors. E-health.kz traffic has increased by 1384.72% compared to last month.
Daily Visitors29
1189.37%
Monthly Visits878.7
1384.72%
Pages per Visit1.00
4%
Visit duration29:33
44225%
Bounce Rate100.00%
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
29
Monthly Visits:
879
Pages per Visit:
1.00
Daily Pageviews:
29
Avg. visit duration:
29:33
Bounce rate:
100.00%
Global Reach:
6.0E-7%
Monthly Visits (SEMrush):
10,200
Monthly Unique Visitors (SEMrush):
8,858
Monthly Visits (SimilarWeb):
883
HypeRank:
n/a
*All traffic values are estimates only.

Traffic sources

Direct:
80.26%
Referral:
13.16%
Search:
0%
Social:
6.58%
Paid:
0%

Desktop vs Mobile

Desktop:
19.74%
Mobile:
80.26%

Total Visits Last 3 Months

0
JAN
59.2
FEB
878.7
MAR
Last update was 6 days ago
     
This can take up to 60 seconds. Please wait...

*HypeStat.com is not promoting or affiliated with e-health.kz in any way. Only publicly available statistics data are displayed.

  ▼

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:
  e-health.kz
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
Full SEMrush Report >>

Revenue report ▼

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

How much would e-health.kz make?

Daily Revenue:
$0.12
Monthly Revenue:
$3.60
Yearly Revenue:
$43.80
*All earnings values are estimates only.

How much is e-health.kz worth?

Website Value:
$127.7

Ad Experience Report ▼

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

Mobile summary

Root domain:
e-health.kz
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:
e-health.kz
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:
e-health.kz
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 e-health.kz hosted? ▼

E-health.kz may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.
Server IP:
109.233.110.108
ASN:
AS48716 
ISP:
PS Internet Company LLC 
Server Location:

Kazakhstan, KZ
 

Other sites hosted on 109.233.110.108

There are no other sites hosted on this IP

How fast does e-health.kz load? ▼

The average loading time of e-health.kz is 829 ms. The Desktop speed index is 100 and mobile speed index is 100.
Average Load Time:
829 ms

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.

Cumulative Layout Shift (CLS)0 0% of loads for this page have a fast (<0s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have an average (0s ~ 0s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have a slow (>0s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)0 0% of loads for this page have a fast (<0s) Time To First Byte (TTFB) 0% 0% of loads for this page have an average (0s ~ 0s) Time To First Byte (TTFB) 0% 0% of loads for this page have a slow (>0s) Time To First Byte (TTFB) 0%
First Contentful Paint (FCP)0 0% of loads for this page have a fast (<0s) First Contentful Paint (FCP) 0% 0% of loads for this page have an average (0s ~ 0s) First Contentful Paint (FCP) 0% 0% of loads for this page have a slow (>0s) First Contentful Paint (FCP) 0%
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)0 0% of loads for this page have a fast (<0ms) Interaction To Next Paint (INP) 0% 0% of loads for this page have an average (0ms ~ 0ms) Interaction To Next Paint (INP) 0% 0% of loads for this page have a slow (>0ms) Interaction To Next Paint (INP) 0%
Largest Contentful Paint (LCP)0 0% of loads for this page have a fast (<0ms) Largest Contentful Paint (LCP) 0% 0% of loads for this page have an average (0ms ~ 0ms) Largest Contentful Paint (LCP) 0% 0% of loads for this page have a slow (>0ms) Largest Contentful Paint (LCP) 0%

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.

Cumulative Layout Shift (CLS)0 0% of loads for this page have a fast (<0s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have an average (0s ~ 0s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have a slow (>0s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)0 0% of loads for this page have a fast (<0s) Time To First Byte (TTFB) 0% 0% of loads for this page have an average (0s ~ 0s) Time To First Byte (TTFB) 0% 0% of loads for this page have a slow (>0s) Time To First Byte (TTFB) 0%
First Contentful Paint (FCP)0 0% of loads for this page have a fast (<0s) First Contentful Paint (FCP) 0% 0% of loads for this page have an average (0s ~ 0s) First Contentful Paint (FCP) 0% 0% of loads for this page have a slow (>0s) First Contentful Paint (FCP) 0%
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)0 0% of loads for this page have a fast (<0ms) Interaction To Next Paint (INP) 0% 0% of loads for this page have an average (0ms ~ 0ms) Interaction To Next Paint (INP) 0% 0% of loads for this page have a slow (>0ms) Interaction To Next Paint (INP) 0%
Largest Contentful Paint (LCP)0 0% of loads for this page have a fast (<0ms) Largest Contentful Paint (LCP) 0% 0% of loads for this page have an average (0ms ~ 0ms) Largest Contentful Paint (LCP) 0% 0% of loads for this page have a slow (>0ms) Largest Contentful Paint (LCP) 0%

Lab Data

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
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
Minimize 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 how to minimize third-party impact
Time to Interactive 0.5 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
Largest Contentful Paint 0.5 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 Meaningful Paint  
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint 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
Speed Index 0.9 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Max Potential First Input Delay 20 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
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
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
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`  
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents . a 300 millisecond delay to user input Learn more about using the viewport meta tag
Total Blocking Time 0 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
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
INP by phase  
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
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
Third parties  
Third party code can significantly impact load performance. to prioritize your page's content. Reduce and defer loading of third party code

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.

Cumulative Layout Shift (CLS)0 0% of loads for this page have a fast (<0s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have an average (0s ~ 0s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have a slow (>0s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)0 0% of loads for this page have a fast (<0s) Time To First Byte (TTFB) 0% 0% of loads for this page have an average (0s ~ 0s) Time To First Byte (TTFB) 0% 0% of loads for this page have a slow (>0s) Time To First Byte (TTFB) 0%
First Contentful Paint (FCP)0 0% of loads for this page have a fast (<0s) First Contentful Paint (FCP) 0% 0% of loads for this page have an average (0s ~ 0s) First Contentful Paint (FCP) 0% 0% of loads for this page have a slow (>0s) First Contentful Paint (FCP) 0%
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)0 0% of loads for this page have a fast (<0s) Interactive To Next Paint (INP) 0% 0% of loads for this page have an average (0s ~ 0s) Interactive To Next Paint (INP) 0% 0% of loads for this page have a slow (>0s) Interactive To Next Paint (INP) 0%
Largest Contentful Paint (LCP)0 0% of loads for this page have a fast (<0s) Largest Contentful Paint (LCP) 0% 0% of loads for this page have an average (0s ~ 0s) Largest Contentful Paint (LCP) 0% 0% of loads for this page have a slow (>0s) Largest Contentful Paint (LCP) 0%

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.

Cumulative Layout Shift (CLS)0 0% of loads for this page have a fast (<0s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have an average (0s ~ 0s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have a slow (>0s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)0 0% of loads for this page have a fast (<0s) Time To First Byte (TTFB) 0% 0% of loads for this page have an average (0s ~ 0s) Time To First Byte (TTFB) 0% 0% of loads for this page have a slow (>0s) Time To First Byte (TTFB) 0%
First Contentful Paint (FCP)0 0% of loads for this page have a fast (<0s) First Contentful Paint (FCP) 0% 0% of loads for this page have an average (0s ~ 0s) First Contentful Paint (FCP) 0% 0% of loads for this page have a slow (>0s) First Contentful Paint (FCP) 0%
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)0 0% of loads for this page have a fast (<0s) Interactive To Next Paint (INP) 0% 0% of loads for this page have an average (0s ~ 0s) Interactive To Next Paint (INP) 0% 0% of loads for this page have a slow (>0s) Interactive To Next Paint (INP) 0%
Largest Contentful Paint (LCP)0 0% of loads for this page have a fast (<0s)Largest Contentful Paint (LCP) 0% 0% of loads for this page have an average (0s ~ 0s)Largest Contentful Paint (LCP) 0% 0% of loads for this page have a slow (>0s)Largest Contentful Paint (LCP) 0%

Lab Data

Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`  
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents . a 300 millisecond delay to user input Learn more about using the viewport meta tag
INP by phase  
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
Total Blocking Time 0 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
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
Largest Contentful Paint 1.5 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 Meaningful Paint  
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
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
Time to Interactive 1.5 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
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
First Contentful Paint 0.9 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
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
Minimize 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 how to minimize third-party impact
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
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
Max Potential First Input Delay 20 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
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
Third parties  
Third party code can significantly impact load performance. to prioritize your page's content. Reduce and defer loading of third party code
Speed Index 1.9 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric

Does e-health.kz 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 e-health.kz are reduced by %.
e-health.kz does not use compression.
Original size: 703 B
Compressed size: n/a
File reduced by: (%)

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. e-health.kz supports HTTPS.
 e-health.kz supports HTTPS
     
Verifying SSL Support. Please wait...
Common Name: *.e-health.kz
Organization:
Location:
Issuer: GoGetSSL RSA DV CA
Valid from: Mar 17 00:00:00 2025 GMT
Valid until: Apr 16 23:59:59 2026 GMT
Authority: CA:FALSE
Keysize: 4096 Bits
Common Name: GoGetSSL RSA DV CA
Organization: GoGetSSL
Location: Riga, LV
Issuer: USERTrust RSA Certification Authority
Valid from: Sep 6 00:00:00 2018 GMT
Valid until: Sep 5 23:59:59 2028 GMT
Authority: CA:TRUE
Keysize: 2048 Bits
Common Name: USERTrust RSA Certification Authority
Organization: The USERTRUST Network
Location: Jersey City, New Jersey, US
Issuer: AAA Certificate Services
Valid from: Mar 12 00:00:00 2019 GMT
Valid until: Dec 31 23:59:59 2028 GMT
Authority: CA:TRUE
Keysize: 4096 Bits

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.
 e-health.kz 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. 
content-type: text/html
last-modified: Mon, 11 Apr 2022 08:16:32 GMT
accept-ranges: bytes
etag: "9aa8ed737c4dd81:0"
server: Microsoft-IIS/10.0
date: Sat, 12 Apr 2025 07:16:43 GMT
content-length: 703

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
MX mx.yandex.net 3600
TXT yandex-verification: 8b376334653d6e8b 3600
TXT update_dns_zone 3600
TXT v=spf1 redirect=_spf.yandex.net 3600
SOA 3600
Mname ns1.hoster.kz
Rname support.hoster.kz
Serial Number 2025041001
Refresh 36000
Retry 3600
Expire 1360000
Minimum TTL 136
A 109.233.110.108 3563
NS ns2.hoster.kz 3600
NS ns1.hoster.kz 3600
NS ns3.hoster.kz 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 February 5, 2017 and will expire on April 18, 2025 if not renewed. This website is now assigned through the registrar HOSTER.KZ. The WHOIS data for this website's domain was last updated on November 29, 2019.
Domain Created:
2017-02-05
Domain Updated:
2019-11-29
Domain Age:
8 years 2 months 13 days
Domain Registrar:
HOSTER.KZ
Domain Owner:
Yussichev Anton Petrovich
WhoIs:
 

Whois Server for the KZ top level domain name.
This server is maintained by KazNIC Organization, a ccTLD manager for Kazakhstan Republic.

Domain Name............: e-health.kz

Organization Using Domain Name
Name...................: Yussichev Anton Petrovich
Organization Name......: Yussichev Anton Petrovich
Street Address.........: ul. Buketova, 57
City...................: Petropavlovsk
State..................: -
Postal Code............: 150000
Country................: KZ

Administrative Contact/Agent
NIC Handle.............: HOSTERKZ-297468
Name...................: Hostmaster
Phone Number...........: +77470949284 
Fax Number.............: +77272379284 
Email Address..........: email

Nameserver in listed order

Primary server.........: ns1.hoster.kz
Primary ip address.....: 185.116.195.38

Secondary server.......: ns2.hoster.kz
Secondary ip address...: 185.121.81.104

Secondary server.......: ns3.hoster.kz
Secondary ip address...: 89.35.125.31


Domain created: 2017-02-05 07:27:02 (GMT+0:00)
Last modified : 2019-11-29 13:51:02 (GMT+0:00)
Domain status : clientDeleteProhibited - status prevent domain deletion from the Register (статус предотвращает удаление домена из реестра)
                clientTransferProhibited - status prohibits domain transfer without documents (статус запрещает трансфер домена без предоставления документов)
                clientRenewProhibited - status prevent domain auto renewal without payment (статус предотвращает авто продление без оплаты)
                
Registar created: HOSTER.KZ
Current Registar: HOSTER.KZ