Xtls.github.io
Project X
Domain Summary
What is the traffic rank for Xtls.github.io?
• Xtls.github.io ranks #1,239,322 globally on HypeStat.
What percent of global Internet users visit Xtls.github.io?
• 9.63E-5% of global Internet users visit Xtls.github.io
How many people visit Xtls.github.io each day?
• Xtls.github.io receives approximately 4.7K visitors and 30,904 page impressions per day.
Which countries does Xtls.github.io receive most of its visitors from?
• Xtls.github.io is mostly visited by people located in China,Russian Federation,United States.
How much Xtls.github.io can earn?
• Xtls.github.io should earn about $40.70/day from advertising revenue.
What is Xtls.github.io estimated value?
• Estimated value of Xtls.github.io is $39,934.58.
What IP addresses does Xtls.github.io resolve to?
• Xtls.github.io resolves to the IP addresses 2606:50c0:8001::153, 185.199.110.153.
Where are Xtls.github.io servers located in?
• Xtls.github.io has servers located in California, United States.
xtls.github.io Profile
Title:Project X
Description:Xray 官方文档
What technologies does xtls.github.io use?
These are the technologies used at xtls.github.io. xtls.github.io has a total of 6 technologies installed in 6 different categories.
xtls.github.io Traffic Analysis
Xtls.github.io is ranked #1,239,322 in the world. This website is viewed by an estimated 4.7K visitors daily, generating a total of 30.9K pageviews. This equates to about 143.8K monthly visitors. Xtls.github.io traffic has decreased by 12.21% compared to last month.Daily Visitors4.7K
5.42%
Monthly Visits143.8K
12.21%
Pages per Visit6.51
0.66%
Visit duration03:41
75.21%
Bounce Rate41.21%
28.94%
Is this your site?Verify your site's metrics.
- Daily Unique Visitors:
- 4,747
- Monthly Visits:
- 143,834
- Pages per Visit:
- 6.51
- Daily Pageviews:
- 30,904
- Avg. visit duration:
- 03:41
- Bounce rate:
- 41.21%
- Global Reach:
- 9.63E-5%
- Monthly Visits (SEMrush):
- 96,065
- Monthly Unique Visitors (SEMrush):
- 58,070
- Monthly Visits (SimilarWeb):
- 141,005
- HypeRank:
- 1,239,322
- SEMrush Rank:
- 518,829
- SimilarWeb Rank:
- 186,503
Traffic sources
- Direct:
- 50.72%
- Referral:
- 6.49%
- Search:
- 29.15%
- Social:
- 13.63%
- Paid:
- 0%
Desktop vs Mobile
- Desktop:
- 93.07%
- Mobile:
- 6.93%
Total Visits Last 3 Months
164.6K
JUL
163.8K
AUG
143.8K
SEP
Visitors by country
- Country
- Users%
- China 42.81%
- Russian Federation 26.37%
- United States 7.76%
- Singapore 3.85%
- Hong Kong 2.17%
▼
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.- Domain:
- xtls.github.io
- Rank:
(Rank based on keywords, cost and organic traffic) - 518,829
- Organic Keywords:
(Number of keywords in top 20 Google SERP) - 489
- Organic Traffic:
(Number of visitors coming from top 20 search results) - 2,716
- Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords) - $617.00
Backlinks Report ▼
Xtls.github.io has a total of 30,331 backlinks from 685 referring domains and most of them comes from United States.- Total Backlinks:
- 30,331
- Follow Links:
- n/a
- Nofollow Links:
- n/a
- Referring Domains:
- 685
- Referring IPs:
- 716
- Authority Domain Score:
- 29
Backlinks by country
- Country
- Domains
- United States 201
- China 33
- Hong Kong 28
- Singapore 23
- Japan 23
Backlinks by TLDs
- TLD Distribution
- Domains
- .com
- 210
- .io
- 47
- .org
- 46
- .edu
- 0
- .gov
- 0
Which sites are competitors to xtls.github.io?
Websites similar to xtls.github.io 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.- Domain
- CompareDaily Visitors
- cloudflare.com
- Compare >2M
- linux.do
- Compare >229.7K
- hostloc.com
- Compare >28.3K
- v2fly.org
- Compare >21.7K
- itdog.cn
- Compare >21.5K
- outlinekeys.com
- Compare >15.3K
- securitylab.ru
- Compare >14.9K
- 51xiazai.cn
- Compare >14.8K
- topersoft.com
- Compare >14.6K
- vpnproxymaster.com
- Compare >11.2K
- ssldragon.com
- Compare >5.3K
- racevpn.com
- Compare >4.9K
- opentunnel.net
- Compare >4.8K
- matsuridayo.github.io
- Compare >4.6K
- chaitin.cn
- Compare >3.2K
Last update was 110 days ago
This can take up to 60 seconds. Please wait...
This can take up to 60 seconds. Please wait...
*HypeStat.com is not promoting or affiliated with xtls.github.io in any way. Only publicly available statistics data are displayed.
Revenue report ▼
Google.com would generate approximately $40.7 per day if the source of income were advertisements, which equates to an estimated monthly revenue of $1.2K and annual gross revenue of approximately $14.9K. Based on these figures, the site's net worth is estimated at around $39.9K.How much would xtls.github.io make?
- Daily Revenue:
- $40.70
- Monthly Revenue:
- $1,221.00
- Yearly Revenue:
- $14,855.50
Daily earning by country
- CountryPageviewsEarning
- United States 2,397$11.58
- Russian Federation 8,151$3.34
- Singapore 1,191$2.24
- China 13,229$1.32
- Hong Kong 672$0.74
Loss of money due to Adblock?
- Daily Revenue Loss:
- $3.18
- Monthly Revenue Loss:
- $95.39
- Yearly Revenue Loss:
- $1,160.52
- Daily Pageviews Blocked:
- 3,053
- Monthly Pageviews Blocked:
- 91,583
- Yearly Pageviews Blocked:
- 1,114,261
Daily revenue loss by country
- CountryBlockedLost Money
- United States 431$2.08
- Singapore 345$0.65
- Russian Federation 489$0.20
- China 1,720$0.17
- Hong Kong 67$0.07
How much is xtls.github.io worth?
- Website Value:
- $39.9K
Ad Experience Report ▼
Summary of the ad experience rating of a website for a specific platform.Mobile summary
- Root domain:
- xtls.github.io
- 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:
- xtls.github.io
- 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:
- xtls.github.io
- 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 xtls.github.io hosted? ▼
Xtls.github.io may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.- Server IP:
- 2606:50c0:8001::153, 185.199.110.153
- ASN:
- AS54113
- ISP:
- Fastly
- Server Location:
- California, CA
United States, US
Other sites hosted on 185.199.110.153
How fast does xtls.github.io load? ▼
The average loading time of xtls.github.io is 170 ms. The Desktop speed index is 100 and mobile speed index is 83.- Average Load Time:
- 170 ms
Page Speed (Google PageSpeed Insights) - Desktop
Field Data
Over the last 30 days, the field data shows that this page has a AVERAGE 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
Time To First Byte (TTFB)0
First Contentful Paint (FCP)2.1s
First Input Delay (FID)2ms
Interaction To Next Paint (INP)0
Largest Contentful Paint (LCP)0
Origin Data
All pages served from this origin have an AVERAGE 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)7ms
Time To First Byte (TTFB)0
First Contentful Paint (FCP)2.0s
First Input Delay (FID)2ms
Interaction To Next Paint (INP)0
Largest Contentful Paint (LCP)2.3s
Lab Data
Speed Index 0.5 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more
Speed Index shows how quickly the contents of a page are visibly populated. Learn more
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 more
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
Max Potential First Input Delay 100 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more
Largest Contentful Paint 0.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more
Largest Contentful Paint marks the time at which the largest 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
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more
Avoids `unload` event listeners
The `unload` event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Use `pagehide` or `visibilitychange` events instead. Learn more
The `unload` event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Use `pagehide` or `visibilitychange` events instead. Learn more
Total Blocking Time 20 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more
Timing budget
Set a timing budget to help you keep an eye on the performance of your site. Performant sites load fast and respond to user input events quickly. Learn more
Set a timing budget to help you keep an eye on the performance of your site. Performant sites load fast and respond to user input events quickly. 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
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more
Has 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
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
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 more
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn more
First Meaningful Paint 0.5 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more
First Meaningful Paint measures when the primary content of a page is visible. Learn more
First Contentful Paint 0.5 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more
First Contentful Paint marks the time at which the first text or image is painted. Learn more
Page Speed (Google PageSpeed Insights) - Mobile
Field Data
Over the last 30 days, the field data shows that this page has a AVERAGE 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
Time To First Byte (TTFB)0
First Contentful Paint (FCP)2.1s
First Input Delay (FID)11ms
Interactive To Next Paint (INP)0
Largest Contentful Paint (LCP)2.3s
Origin Data
All pages served from this origin have an AVERAGE 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
Time To First Byte (TTFB)0
First Contentful Paint (FCP)2.1s
First Input Delay (FID)11ms
Interactive To Next Paint (INP)0
Largest Contentful Paint (LCP)2.3s
Lab Data
Avoids `unload` event listeners
The `unload` event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Use `pagehide` or `visibilitychange` events instead. Learn more
The `unload` event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Use `pagehide` or `visibilitychange` events instead. Learn more
Time to Interactive 3.3 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more
First Meaningful Paint 2.2 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more
First Meaningful Paint measures when the primary content of a page is visible. Learn more
Has 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
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
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 more
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn more
Max Potential First Input Delay 340 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more
Largest Contentful Paint 3.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more
Largest Contentful Paint marks the time at which the largest text or image is painted. 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
First Contentful Paint marks the time at which the first text or image is painted. Learn more
Speed Index 2.2 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more
Speed Index shows how quickly the contents of a page are visibly populated. Learn more
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more
Total Blocking Time 340 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more
First Contentful Paint (3G) 3971 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more
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 more
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
Timing budget
Set a timing budget to help you keep an eye on the performance of your site. Performant sites load fast and respond to user input events quickly. Learn more
Set a timing budget to help you keep an eye on the performance of your site. Performant sites load fast and respond to user input events quickly. Learn more
Does xtls.github.io 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 xtls.github.io are reduced by 81%.
xtls.github.io use gzip compression.
Original size: 59.91 KB
Compressed size: 11.15 KB
File reduced by: 48.75 KB (81%)
Compressed size: 11.15 KB
File reduced by: 48.75 KB (81%)
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.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. xtls.github.io supports HTTPS. xtls.github.io supports HTTPS
Verifying SSL Support. Please wait...
Common Name: *.github.io
Organization:
Location:
Issuer: Sectigo RSA Domain Validation Secure Server CA
Valid from: Mar 7 00:00:00 2025 GMT
Valid until: Mar 7 23:59:59 2026 GMT
Authority: CA:FALSE
Keysize: 2048 Bits
Organization:
Location:
Issuer: Sectigo RSA Domain Validation Secure Server CA
Valid from: Mar 7 00:00:00 2025 GMT
Valid until: Mar 7 23:59:59 2026 GMT
Authority: CA:FALSE
Keysize: 2048 Bits
Common Name: Sectigo RSA Domain Validation Secure Server CA
Organization: Sectigo Limited
Location: Salford, Greater Manchester, GB
Issuer: USERTrust RSA Certification Authority
Valid from: Nov 2 00:00:00 2018 GMT
Valid until: Dec 31 23:59:59 2030 GMT
Authority: CA:TRUE
Keysize: 2048 Bits
Organization: Sectigo Limited
Location: Salford, Greater Manchester, GB
Issuer: USERTrust RSA Certification Authority
Valid from: Nov 2 00:00:00 2018 GMT
Valid until: Dec 31 23:59:59 2030 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
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. xtls.github.io 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.server: GitHub.com
content-type: text/html; charset=utf-8
x-origin-cache: HIT
last-modified: Sun, 19 Oct 2025 10:36:47 GMT
access-control-allow-origin: *
strict-transport-security: max-age=31556952
etag: W/"68f4bf3f-efa1"
expires: Sun, 19 Oct 2025 15:48:33 GMT
cache-control: max-age=600
content-encoding: gzip
x-proxy-cache: MISS
x-github-request-id: 9451:132B74:2FE936:3086D2:68F505F9
accept-ranges: bytes
age: 0
date: Sun, 19 Oct 2025 19:29:31 GMT
via: 1.1 varnish
x-served-by: cache-par-lfpg1960059-PAR
x-cache: HIT
x-cache-hits: 0
x-timer: S1760902171.490513,VS0,VE117
vary: Accept-Encoding
x-fastly-request-id: 5f2400112b863d0c70da36f93f097fa4dd9291a9
content-length: 11420
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 |
| A | 185.199.110.153 | 3361 | |
| A | 185.199.109.153 | 3361 | |
| A | 185.199.111.153 | 3361 | |
| A | 185.199.108.153 | 3361 | |
| AAAA | 2606:50c0:8002::153 | 2813 | |
| AAAA | 2606:50c0:8003::153 | 2813 | |
| AAAA | 2606:50c0:8000::153 | 2813 | |
| AAAA | 2606:50c0:8001::153 | 2813 |