hospitals.tw Hospitals.tw

   
台灣醫院診所門診時間表|看診進度|網路掛號查詢|醫師資訊|看診流程

Domain Summary

What is the traffic rank for Hospitals.tw?

• Hospitals.tw ranks #952,031 globally on HypeStat.

What percent of global Internet users visit Hospitals.tw?

• 2.61E-5% of global Internet users visit Hospitals.tw

How many people visit Hospitals.tw each day?

• Hospitals.tw receives approximately 1.3K visitors and 1,955 page impressions per day.

Which countries does Hospitals.tw receive most of its visitors from?

• Hospitals.tw is mostly visited by people located in Taiwan,United States.

How much Hospitals.tw can earn?

• Hospitals.tw should earn about $1.27/day from advertising revenue.

What is Hospitals.tw estimated value?

• Estimated value of Hospitals.tw is $1,157.48.

What IP addresses does Hospitals.tw resolve to?

• Hospitals.tw resolves to the IP addresses 2606:4700:20::681a:6b, 172.67.69.251.

Where are Hospitals.tw servers located in?

• Hospitals.tw has servers located in United States.

hospitals.tw Profile

Title:台灣醫院診所門診時間表|看診進度|網路掛號查詢|醫師資訊|看診流程 Description:台醫網提供台灣大醫院看診流程、醫師相關資訊、看診說明、著作、衛教文章、媒體報導訪問與看診經驗分享。
Category:Health / Other Health
Edit Site Info

What technologies does hospitals.tw use?

These are the technologies used at hospitals.tw. hospitals.tw has a total of 12 technologies installed in 12 different categories.
WordPress plugins
a3 Lazy Load a3 Lazy Load
RankMath SEO RankMath SEO
Performance
a3 Lazy Load a3 Lazy Load
CDN
CloudFlare CloudFlare
Advertising
Google AdSense Google AdSense
Miscellaneous
HTTP/3 HTTP/3
Open Graph Open Graph
JavaScript Libraries
jQuery jQuery
jQuery Migrate jQuery Migrate
WordPress themes
Kadence WP Kadence Kadence WP Kadence
Programming Languages
PHP PHP
SEO
RankMath SEO RankMath SEO
CMS
WordPress WordPress
Blogs
WordPress WordPress
Databases
MySQL MySQL

hospitals.tw Traffic Analysis

Hospitals.tw is ranked #952,031 in the world. This website is viewed by an estimated 1.3K visitors daily, generating a total of 2K pageviews. This equates to about 39.1K monthly visitors. Hospitals.tw traffic has increased by 20.32% compared to last month.
Daily Visitors1.3K
71.66%
Monthly Visits39.1K
20.32%
Pages per Visit1.52
44.35%
Visit duration03:19
92.17%
Bounce Rate55.45%
29.4%
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
1,289
Monthly Visits:
39,057
Pages per Visit:
1.52
Daily Pageviews:
1,955
Avg. visit duration:
03:19
Bounce rate:
55.45%
Global Reach:
2.61E-5%
Monthly Visits (SEMrush):
47,968
Monthly Unique Visitors (SEMrush):
42,488
Monthly Visits (SimilarWeb):
38,278
HypeRank:
952,031
SEMrush Rank:
6,903,299
SimilarWeb Rank:
952,031
*All traffic values are estimates only.

Traffic sources

Direct:
29.84%
Referral:
1.09%
Search:
67.97%
Social:
0%
Paid:
1.09%

Desktop vs Mobile

Desktop:
33.59%
Mobile:
66.41%

Total Visits Last 3 Months

61.6K
DEC
32.5K
JAN
39.1K
FEB

Visitors by country

Country
Users%
 
Taiwan 90.90%
 
United States 9.10%

Which sites are competitors to hospitals.tw?

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

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

Search Engine Indexes ▼

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

  ▼

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:
  hospitals.tw
Rank:
(Rank based on keywords, cost and organic traffic)
  6,903,299
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  145
Organic Traffic:
(Number of visitors coming from top 20 search results)
  14
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 $1.3 per day if the source of income were advertisements, which equates to an estimated monthly revenue of $38.1 and annual gross revenue of approximately $463.6. Based on these figures, the site's net worth is estimated at around $1.2K.

How much would hospitals.tw make?

Daily Revenue:
$1.27
Monthly Revenue:
$38.10
Yearly Revenue:
$463.55
*All earnings values are estimates only.

Daily earning by country

 
CountryPageviewsEarning
 
United States 178$0.86
 
Taiwan 1,777$0.41

Loss of money due to Adblock?

Daily Revenue Loss:
$0.22
Monthly Revenue Loss:
$6.60
Yearly Revenue Loss:
$80.30
Daily Pageviews Blocked:
316
Monthly Pageviews Blocked:
9,491
Yearly Pageviews Blocked:
115,470

Daily revenue loss by country

 
CountryBlockedLost Money
 
United States 32$0.15
 
Taiwan 284$0.07

How much is hospitals.tw worth?

Website Value:
$1.2K

Ad Experience Report ▼

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

Mobile summary

Root domain:
hospitals.tw
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:
hospitals.tw
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:
hospitals.tw
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 hospitals.tw hosted? ▼

Hospitals.tw may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.
Server IP:
2606:4700:20::681a:6b, 172.67.69.251
ASN:
AS13335 
ISP:
Cloudflare Inc 
Server Location:

United States, US
 

Other sites hosted on 172.67.69.251

How fast does hospitals.tw load? ▼

The average loading time of hospitals.tw is 49 ms. The Desktop speed index is 100 and mobile speed index is 65.
Average Load Time:
49 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 FAST speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Cumulative Layout Shift (CLS)0ms 94% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 94% 0% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 0% 5% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 5%
Time To First Byte (TTFB)161ms 98% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 98% 1% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 1% 0% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 0%
First Contentful Paint (FCP)986ms 94% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 94% 4% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 4% 1% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 1%
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)955ms 96% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 96% 1% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 1% 1% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 1%

Origin Data

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

Cumulative Layout Shift (CLS)0ms 93% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 93% 5% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 5% 1% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 1%
Time To First Byte (TTFB)373ms 91% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 91% 6% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 6% 1% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 1%
First Contentful Paint (FCP)1.7s 80% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 80% 15% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 15% 4% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 4%
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)56ms 95% of loads for this page have a fast (<200ms) Interaction To Next Paint (INP) 95% 2% of loads for this page have an average (200ms ~ 500ms) Interaction To Next Paint (INP) 2% 2% of loads for this page have a slow (>500ms) Interaction To Next Paint (INP) 2%
Largest Contentful Paint (LCP)1.8s 87% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 87% 7% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 7% 5% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 5%

Lab Data

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.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
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
Total Blocking Time 50 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
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
LCP request discovery  
Optimize LCP by making the LCP image from the HTML immediately, and discoverable avoiding lazy-loading
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
Largest Contentful Paint image was not lazily loaded  
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading
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
INP by phase  
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
First Meaningful Paint  
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
Largest Contentful Paint 0.4 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Time to Interactive 1.2 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric
Speed Index 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 80 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
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
Preload Largest Contentful Paint image  
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements

Page Speed (Google PageSpeed Insights) - Mobile

65
0-49 50-89 90-100 i

Field Data

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

Cumulative Layout Shift (CLS)0ms 94% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 99% 0% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)163ms 98% of loads for this page have a fast (<800s) Time To First Byte (TTFB) 96% 0% of loads for this page have an average (800s ~ 1800s) Time To First Byte (TTFB) 0% 2% of loads for this page have a slow (>1800s) Time To First Byte (TTFB) 2%
First Contentful Paint (FCP)1.1s 94% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 89% 7% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 7% 3% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 3%
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)915ms 96% of loads for this page have a fast (<2500s) Largest Contentful Paint (LCP) 96% 1% of loads for this page have an average (2500s ~ 4000s) Largest Contentful Paint (LCP) 1% 1% of loads for this page have a slow (>4000s) Largest Contentful Paint (LCP) 1%

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.

Cumulative Layout Shift (CLS)52ms 47% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 47% 16% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 16% 36% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 36%
Time To First Byte (TTFB)464ms 91% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 91% 5% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 5% 2% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 2%
First Contentful Paint (FCP)1.6s 82% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 82% 13% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 13% 4% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 4%
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)147ms 87% of loads for this page have a fast (<0.2s) Interactive To Next Paint (INP) 87% 10% of loads for this page have an average (0.2s ~ 0.5s) Interactive To Next Paint (INP) 10% 1% of loads for this page have a slow (>0.5s) Interactive To Next Paint (INP) 1%
Largest Contentful Paint (LCP)1.6s 93% of loads for this page have a fast (<2.5s)Largest Contentful Paint (LCP) 93% 3% of loads for this page have an average (2.5s ~ 4s)Largest Contentful Paint (LCP) 3% 2% of loads for this page have a slow (>4s)Largest Contentful Paint (LCP) 2%

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. Learn more about the Total Blocking Time metric
First Contentful Paint 5.2 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First 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
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
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
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
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
LCP request discovery  
Optimize LCP by making the LCP image from the HTML immediately, and discoverable avoiding lazy-loading
INP by phase  
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
Speed Index 5.6 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index 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
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
Largest Contentful Paint 5.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Time to Interactive 5.8 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric
Preload Largest Contentful Paint image  
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements
Largest Contentful Paint image was not lazily loaded  
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading
Max Potential First Input Delay 50 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

Does hospitals.tw 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 hospitals.tw are reduced by 89%.
hospitals.tw use br compression.
Original size: 330.89 KB
Compressed size: 33.52 KB
File reduced by: 297.37 KB (89%)

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. hospitals.tw supports HTTPS.
 hospitals.tw supports HTTPS
     
Verifying SSL Support. Please wait...
Common Name: hospitals.tw
Organization:
Location:
Issuer: WE1
Valid from: Feb 18 08:48:26 2025 GMT
Valid until: May 19 09:48:12 2025 GMT
Authority: CA:FALSE
Keysize:
Common Name: WE1
Organization: Google Trust Services
Location: US
Issuer: GTS Root R4
Valid from: Dec 13 09:00:00 2023 GMT
Valid until: Feb 20 14:00:00 2029 GMT
Authority: CA:TRUE
Keysize:
Common Name: GTS Root R4
Organization: Google Trust Services LLC
Location: US
Issuer: GlobalSign Root CA
Valid from: Nov 15 03:43:21 2023 GMT
Valid until: Jan 28 00:00:42 2028 GMT
Authority: CA:TRUE
Keysize:

Verify HTTP/2 Support ▼

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

Http Header ▼

HTTP headers are extra portions of records despatched among a consumer (which include an internet browser) and a server at some stage in an HTTP request or response. They offer instructions, metadata, or manipulate parameters for the conversation among the consumer and server. 
date: Sat, 29 Mar 2025 00:44:42 GMT
content-type: text/html; charset=UTF-8
cf-ray: 927b571b1ce68c0a-ORD
cf-cache-status: HIT
age: 74263
cache-control: max-age=86400
last-modified: Thu, 27 Mar 2025 17:23:26 GMT
link: <https://hospitals.tw/wp-json/>; rel="https://api.w.org/", <https://hospitals.tw/wp-json/wp/v2/pages/7073>; rel="alternate"; title="JSON"; type="application/json", <https://hospitals.tw/>; rel=shortlink, </wp-includes/js/wp-emoji-release.min.js?ver=6.7.1>; rel=preload; as=script, </wp-content/plugins/stackable-ultimate-gutenberg-blocks/dist/frontend_blocks.css?ver=3.13.11>; rel=preload; as=style, </wp-content/plugins/stackable-ultimate-gutenberg-blocks/dist/frontend_blocks_responsive.css?ver=3.13.11>; rel=preload; as=style, </wp-includes/css/dist/block-library/style.min.css?ver=6.7.1>; rel=preload; as=style, </wp-content/plugins/ultimate-blocks/dist/blocks.style.build.css?ver=67e5898d06bbd>; rel=preload; as=style, </wp-content/plugins/ultimate-blocks/src/extensions/style.css?ver=6.7.1>; rel=preload; as=style, </wp-content/themes/kadence/assets/css/global.min.css?ver=1.2.14>; rel=preload; as=style, </wp-content/themes/kadence/assets/css/header.min.css?ver=1.2.14>; rel=preload; as=style, </wp-content/themes/kadence/assets/css/content.min.css?ver=1.2.14>; rel=preload; as=style, </wp-content/themes/kadence/assets/css/sidebar.min.css?ver=1.2.14>; rel=preload; as=style, </wp-content/themes/kadence/assets/css/footer.min.css?ver=1.2.14>; rel=preload; as=style, </wp-content/themes/kadence/assets/css/rankmath.min.css?ver=1.2.14>; rel=preload; as=style, </wp-includes/js/jquery/jquery.min.js?ver=3.7.1>; rel=preload; as=script, </wp-includes/js/jquery/jquery-migrate.min.js?ver=3.4.1>; rel=preload; as=script, </wp-content/plugins/stackable-ultimate-gutenberg-blocks/dist/deprecated/frontend_blocks_deprecated_v2.css?ver=3.13.11>; rel=preload; as=style, </wp-content/plugins/ultimate-blocks/src/blocks/content-toggle/front.build.js?ver=3.2.6>; rel=preload; as=script, </wp-content/themes/kadence/assets/js/navigation.min.js?ver=1.2.14>; rel=preload; as=script, </wp-content/plugins/stackable-ultimate-gutenberg-blocks/dist/deprecated/frontend_blocks_deprecated_v2.js?ver=3.13.11>; rel=preload; as=script
vary: Accept-Encoding
cf-apo-via: tcache
cf-edge-cache: cache,platform=wordpress
x-powered-by: PHP/7.4.3
x-powered-by: ASP.NET
report-to: {"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=OHOKuw33OrFSjKDYkTYZg%2F%2F6Blgx4Cbk6tvZyvTJBI9I%2Bm3m9AG9G0WUTOso1auBi1dAcXnrI85gHTqjjUD5KGsuLfhal7NxBgRE68Qz1jeiTYbAqmf9LGIiyn8gvQ%3D%3D"}],"group":"cf-nel","max_age":604800}
nel: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
server: cloudflare
content-encoding: br
alt-svc: h3=":443"; ma=86400
server-timing: cfL4;desc="?proto=TCP&rtt=2295&min_rtt=2268&rtt_var=690&sent=7&recv=10&lost=0&retrans=0&sent_bytes=3429&recv_bytes=892&delivery_rate=1248814&cwnd=158&unsent_bytes=0&cid=c32b34985e9a1c40&ts=37&x=0"

DNS Lookup ▼

DNS entries (Domain Name System) are a critical component of the Internet infrastructure. They act as directories that translate human-readable domain names (such as example.com) to machine-readable IP addresses. DNS records are stored on DNS servers and help forward internet traffic efficiently.
Type Ip Target/Txt TTL
AAAA 2606:4700:20::ac43:45fb 185
AAAA 2606:4700:20::681a:16b 185
AAAA 2606:4700:20::681a:6b 185
A 104.26.0.107 185
A 172.67.69.251 185
A 104.26.1.107 185
NS violet.ns.cloudflare.com 3485
NS jakub.ns.cloudflare.com 3485
HINFO 3600

Whois Lookup ▼

Domain WHOIS is a public database that provides information about domain names, including registered owners, contact information, domain registrars, registration and expiration dates, name servers, and other relevant information.
WhoIs:
 

Domain Name: hospitals.tw
   Domain Status: clientTransferProhibited
   Registrant:
      
      Domain Protection Services, Inc.
      email
      US
      (Redacted for privacy)

   Administrative Contact:
      (Redacted for privacy)

   Technical Contact:
      (Redacted for privacy)

   Record expires on 2025-06-27 11:23:34 (UTC+8)
   Record created on 2024-06-27 11:23:34 (UTC+8)

   Domain servers in listed order:
      jakub.ns.cloudflare.com      
      violet.ns.cloudflare.com     

Registration Service Provider: Name.com
Registration Service URL: http://www.name.com/
Provided by Registry Services, LLC. Registry Gateway Services