xfans.tokyo

Xfans.tokyo

#35,821 Global
Xfans(エックスファンズ) | SNSには載せられない特別な動画を毎日更新
Last Updated 49 mins ago
     
This can take up to 60 seconds. Please wait...
Update will be available in 24 hours

Domain Summary

What is the traffic rank for Xfans.tokyo?

Xfans.tokyo ranks #35,821 globally on HypeStat.

What percent of global Internet users visit Xfans.tokyo?

0.00126% of global Internet users visit Xfans.tokyo

How many people visit Xfans.tokyo each day?

Xfans.tokyo receives approximately 75.6K visitors and 576,168 page impressions per day.

Which countries does Xfans.tokyo receive most of its visitors from?

Xfans.tokyo is mostly visited by people located in Japan,Korea, Republic of,Taiwan.

How much Xfans.tokyo can earn?

Xfans.tokyo should earn about $328.77/day from advertising revenue.

What is Xfans.tokyo estimated value?

Estimated value of Xfans.tokyo is $293,279.91.

What IP addresses does Xfans.tokyo resolve to?

Xfans.tokyo resolves to the IP addresses 104.26.4.139.

xfans.tokyo Profile

Title
xfans(エックスファンズ) | SNSには載せられない特別な動画を毎日更新
Description
xfans(エックスファンズ)では 他のSNSには載せられないYouTuber、裏垢女子、インフルエンサーの特別な動画を安心安全にご視聴いただけます。
Category
Adult / Adult

What technologies does xfans.tokyo use?

These are the technologies used at xfans.tokyo. xfans.tokyo has a total of 11 technologies installed in 9 different categories.

xfans.tokyo Traffic Analysis

Xfans.tokyo is ranked #35,821 in the world. This website is viewed by an estimated 75.6K visitors daily, generating a total of 576.2K pageviews. This equates to about 2.3M monthly visitors. Xfans.tokyo traffic has increased by 5.83% compared to last month.

Daily Visitors
75.6K
75,614 unique
▲ 11.28%
Monthly Visits
2.3M
▲ 5.83%
Pages per Visit
7.62
▼ 7.65%
Visit Duration
02:50
▼ 24.07%
Bounce Rate
48.28%
▼ 3.18%
Is this your site?Verify your site's metrics.
Daily Unique Visitors
75,614
Monthly Visits
2,291,104
Pages per Visit
7.62
Daily Pageviews
576,168
Avg. Visit Duration
02:50
Bounce Rate
48.28%
Global Reach
0.00126%
Monthly Visits (SEMrush)
1,705,226
Monthly Unique Visitors (SEMrush)
929,375
Monthly Visits (SimilarWeb)
2,291,324
HypeRank
35,821
SEMrush Rank
3,970,154
SimilarWeb Rank
16,939

*All traffic values are estimates only.

Traffic Sources

Direct
53.53%
Referral
11.88%
Search
27.54%
Social
7.06%
Paid
0%

Desktop vs Mobile

Desktop
20.46%
Mobile
79.54%

Total Visits Last 3 Months

2.3M
JUL
2.2M
AUG
2.3M
SEP

Visitors by Country

CountryUsers %
Japan 67.68%
Korea, Republic of 9.59%
Taiwan 8.30%
United States 4.80%
Singapore 2.29%

xfans.tokyo Traffic Flow

The largest share of traffic to xfans.tokyo comes from Direct visits (37.46%). After leaving the site, the most common destination is google.com and emerchantpay.net.

SEO

xfans.tokyo SEMrush Overview

SEMrush is a complete online advertising and marketing platform that gives a wide variety of tools and features to help businesses and marketers improve their online visibility and optimize their digital marketing strategies.

SemRushSemRush
Domain
xfans.tokyo
RankBased on keywords, cost and organic traffic
3,970,154
Organic KeywordsKeywords in top 20 Google SERP
80
Organic TrafficVisitors coming from top 20 search results
93
Organic CostEquivalent Google Ads spend for the same traffic
$0.00
Full SEMrush Report →

Which sites are competitors to xfans.tokyo?

Websites similar to xfans.tokyo 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.

DomainDaily Visitors
dmm.co.jp 6.3M Compare →
dlsite.com 2.7M Compare →
e-***.org 1.2M Compare →
sokmil.com 197K Compare →
dxlive.com 120K Compare →
duga.jp 91.7K Compare →
angel-live.com 81K Compare →
akiba-online.com 45.7K Compare →
hdouga.com 30.4K Compare →
youskbe.com 29.6K Compare →
tokyo-hot.com 21.6K Compare →
onani-daisuki.com 18.8K Compare →
crystalmiss.com 7.8K Compare →
h4610.com 4.4K Compare →
clean***host.com 3.6K Compare →
peepsamurai.com 660 Compare →
xfreehosting.com 521 Compare →
dotup.org 493 Compare →
nichedsites.com 4 Compare →
seekbang.com n/a Compare →
Monetization

Revenue Report

xfans.tokyo would generate approximately $328.8 per day if the source of income were advertisements, which equates to an estimated monthly revenue of $9.9K and annual gross revenue of approximately $120K. Based on these figures, the site's net worth is estimated at around $293.3K.

How much would xfans.tokyo make?

Daily Revenue
$328.77
Monthly Revenue
$9,863.10
Yearly Revenue
$120,001.05

How much is xfans.tokyo worth?

Website Value
$293.3K

*All earnings values are estimates only.

Daily Earning by Country

CountryPageviewsEarning
Japan 389,943 $136.17
United States 27,660 $109.55
Korea, Republic of 55,251 $31.82
Singapore 13,220 $17.65
Taiwan 47,805 $9.24

Daily Revenue Loss by Country

CountryBlockedLost
United States 4,979 $24.05
Singapore 3,834 $7.21
Japan 11,698 $4.21
Taiwan 7,649 $1.76
Korea, Republic of 2,210 $1.33

Impact of Ad Blockers

Daily Revenue Loss
$38.55
Monthly Revenue Loss
$1,156.57
Yearly Revenue Loss
$14,071.57
Daily Pageviews Blocked
30,370
Monthly Pageviews Blocked
911,097
Yearly Pageviews Blocked
11,085,009

Ad Experience Report

Summary of the ad and abusive experience ratings Google assigns to xfans.tokyo, per platform.

Mobile Summary

Root Domain
xfans.tokyo
Ad FilteringChrome is not filtering ads on your site.
Off
StatusReviewed against the Better Ads Standards
Not reviewed

Desktop Summary

Root Domain
xfans.tokyo
Ad FilteringChrome is not filtering ads on your site.
Off
StatusReviewed against the Better Ads Standards
Not reviewed

Abusive Experience

Root Domain
xfans.tokyo
EnforcementChrome is not preventing your site from opening new windows or tabs.
Off
StatusReviewed for abusive experiences
Not reviewed
Technical

Where is xfans.tokyo hosted?

Xfans.tokyo may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.

Server IP
104.26.4.139
ASN
AS13335
ISP
Cloudflare, Inc.
Server Location


Other sites hosted on 104.26.4.139

There are no other sites hosted on this IP.

How fast does xfans.tokyo load?

The average loading time of xfans.tokyo is 472 ms. The Desktop speed index is 39 and mobile speed index is 32.

39
Poor
0–49 · Poor
50–89 · Needs Improvement
90–100 · Good
How is this scored? →
Average Load Time
472 ms

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.

CLSCumulative Layout Shift
11ms
71% fast16% avg12% slow
TTFBTime To First Byte
610ms
85% fast12% avg1% slow
FCPFirst Contentful Paint
919ms
94% fast3% avg1% slow
FIDFirst Input Delay
0
0% fast0% avg0% slow
INPInteraction To Next Paint
80ms
92% fast5% avg2% slow
LCPLargest Contentful Paint
5.0s
25% fast32% avg42% slow

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.

CLSCumulative Layout Shift
8ms
80% fast14% avg5% slow
TTFBTime To First Byte
963ms
66% fast28% avg5% slow
FCPFirst Contentful Paint
1.4s
86% fast9% avg3% slow
FIDFirst Input Delay
0
0% fast0% avg0% slow
INPInteraction To Next Paint
62ms
95% fast3% avg1% slow
LCPLargest Contentful Paint
4.1s
44% fast29% avg25% slow
Largest Contentful Paint5.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
Total Blocking Time830 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 Paint0.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
Max Potential First Input Delay390 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
INP breakdown
Start investigating by looking at the longest subpart. how to improve INP
LCP request discovery
by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading Optimize LCP
Speed Index4.3 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Time to Interactive6.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
32
Poor
0–49 · Poor
50–89 · Needs Improvement
90–100 · Good
How is this scored? →
Average Load Time
472 ms

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.

CLSCumulative Layout Shift
70ms
32% fast10% avg57% slow
TTFBTime To First Byte
714ms
81% fast15% avg2% slow
FCPFirst Contentful Paint
1.2s
90% fast6% avg2% slow
FIDFirst Input Delay
0
0% fast0% avg0% slow
INPInteraction To Next Paint
174ms
79% fast15% avg4% slow
LCPLargest Contentful Paint
9.3s
11% fast7% avg80% slow

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.

CLSCumulative Layout Shift
51ms
39% fast10% avg50% slow
TTFBTime To First Byte
1.1s
60% fast32% avg7% slow
FCPFirst Contentful Paint
1.7s
78% fast14% avg7% slow
FIDFirst Input Delay
0
0% fast0% avg0% slow
INPInteraction To Next Paint
142ms
85% fast11% avg3% slow
LCPLargest Contentful Paint
7.2s
22% fast19% avg58% slow
LCP request discovery
by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading Optimize LCP
First Contentful Paint3.3 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
Largest Contentful Paint33.3 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Total Blocking Time1,720 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
Max Potential First Input Delay590 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
Time to Interactive34.0 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 Index16.0 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
INP breakdown
Start investigating by looking at the longest subpart. how to improve INP

Does xfans.tokyo 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 xfans.tokyo are reduced by 79%.

79%
Reduced
Original
311.2 KB
Compressed
64.12 KB

Saved 247.08 KB off the original size

xfans.tokyo use br compression.

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

WOT 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 browser. It provides authentication and encryption, ensuring that data transmitted between the server and the browser remains private and protected. xfans.tokyo supports HTTPS.

xfans.tokyo supports HTTPS
Verifying SSL Support. Please wait...
Common Name: xfans.tokyo
Organization:
Location:
Issuer: WE1
Valid from: Sep 24 16:54:02 2026 GMT
Valid until: Dec 23 17:53:56 2026 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:

Security Headers

HTTP security headers tell browsers how to protect visitors: force HTTPS, block clickjacking and limit what scripts can do. xfans.tokyo sends 3 of the 6 recommended security headers, and its SSL certificate is issued by Google Trust Services.

D Security headers grade
Strict-Transport-Security
present
Content-Security-Policy
present
X-Frame-Options
present
X-Content-Type-Options
missing
Referrer-Policy
missing
Permissions-Policy
missing
SSL issuer
Google Trust Services
SSL expires
2026-12-23 in 62 days

Email Security

SPF, DKIM and DMARC are DNS records that prove which servers may send email for a domain and tell receivers what to do with forged messages. Missing or weak records make emails from xfans.tokyo more likely to land in spam and the domain easier to spoof.

Email provider
Google Workspace
SPF
missing
DMARC
none (monitoring only)
DKIM
not found on common selectors
DNSSEC
not signed

AI Crawlers

Websites use robots.txt to allow or block AI crawlers that collect content for training and AI search. xfans.tokyo blocks 9 of 26 known AI crawlers.

OpenAI
blocked GPTBot
Anthropic
blocked ClaudeBot
Google
blocked Google-Extended
Apple
blocked Applebot-Extended
Common Crawl
blocked CCBot
ByteDance
blocked Bytespider
Meta
blocked meta-externalagent, FacebookBot
Cohere
blocked cohere-ai
OpenAI
partly blocked ChatGPT-User, OAI-SearchBot
Anthropic
partly blocked Claude-User, Claude-SearchBot
Perplexity
partly blocked PerplexityBot, Perplexity-User
llms.txt
not found

Verify HTTP/2 & HTTP/3 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. HTTP/3 goes a step further and runs over QUIC instead of TCP, for faster connections and better performance on unreliable networks.

xfans.tokyo supports HTTP/2
xfans.tokyo does not support HTTP/3
Verifying HTTP/2 and HTTP/3 Support. Please wait...
Details

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.

HTTP/1.1
date: Wed, 21 Oct 2026 06:09:33 GMT
content-type: text/plain
location: https://www.xfans.tokyo/
cache-control: public, max-age=0, must-revalidate
server: cloudflare
strict-transport-security: max-age=63072000
x-vercel-id: fra1::7bmj8-1792562973448-9457f4b595de
cf-cache-status: DYNAMIC
nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
report-to: {"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=YxDGl3S70I%2BhyNAGQF245Ww4xwtYNfdWE9Ivkb2yef8QK4IHUMuI3dc7e60pYwoaYhxgyElRQ54yKVD6lQA0udK6xd7XFjsXSnJf2JwqJRWoM1xJbsJGJyl%2BDbI68WKgd8Exbh%2FzaRxW"}]}
cf-ray: a4de1817a9834ae6-TXL

HTTP/2 200 
date: Wed, 21 Oct 2026 06:09:33 GMT
content-type: text/html; charset=utf-8
age: 0
cache-control: private, no-cache, no-store, max-age=0, must-revalidate
report-to: {"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=bbVhZteumqzUUcGKxBWE8%2FcEer49d3UWBN%2FpVVF1hEEqr%2BN8ghPfdpa1z5PhNl63vFabu1gRe2dWmIikawGdOXyZD4HuEjTzFvfkNPZLJdUAyk0dQbLclsbKw8IbHWEVl5E7B6toIrIGtfKc4Q%3D%3D"}]}
content-security-policy: frame-ancestors 'self'
link: <https://www.xfans.tokyo/>; rel="alternate"; hreflang="ja", <https://www.xfans.tokyo/zh-CN>; rel="alternate"; hreflang="zh-CN", <https://www.xfans.tokyo/zh-TW>; rel="alternate"; hreflang="zh-TW", <https://www.xfans.tokyo/ko>; rel="alternate"; hreflang="ko", <https://www.xfans.tokyo/en>; rel="alternate"; hreflang="en", <https://www.xfans.tokyo/es>; rel="alternate"; hreflang="es", <https://www.xfans.tokyo/>; rel="alternate"; hreflang="x-default"
link: </_next/static/media/1e41be92c43b3255-s.p.woff2>; rel=preload; as="font"; crossorigin=""; type="font/woff2", </_next/static/media/4c9affa5bc8f420e-s.p.woff2>; rel=preload; as="font"; crossorigin=""; type="font/woff2", </_next/static/media/fea9bcfa8bc9e724-s.p.woff2>; rel=preload; as="font"; crossorigin=""; type="font/woff2"
server: cloudflare
set-cookie: NEXT_LOCALE=en; Path=/; Expires=Thu, 21 Oct 2027 06:09:33 GMT; Max-Age=31536000
set-cookie: FORCE_LOCALE_TO_JA=1; Path=/; Expires=Thu, 21 Oct 2027 06:09:33 GMT; Max-Age=31536000
set-cookie: CLIENT_COUNTRY=DE; Path=/; Expires=Thu, 22 Oct 2026 06:09:33 GMT; Max-Age=86400
strict-transport-security: max-age=63072000
vary: RSC, Next-Router-State-Tree, Next-Router-Prefetch
vary: accept-encoding
x-frame-options: SAMEORIGIN
x-matched-path: /[locale]
x-powered-by: Next.js
x-vercel-cache: MISS
x-vercel-id: fra1::iad1::tctdq-1792562973544-ba5ca402a5d1
cf-cache-status: DYNAMIC
nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
content-encoding: br
cf-ray: a4de181889fbd7b4-TXL

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.

TypeIPTarget / TXTTTL
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
Notice: Effective May 1, 2026, the WHOIS service has been retired in accordance with ICANN's RDAP transition policy. All registration data queries are now served via RDAP. The Registration Data Access Protocol (RDAP) base URL is: https://rdap.gmoregistry.net/rdap/
More on HypeStat
Activity

Recently Analyzed Sites

789b111.tv
HTTP/2 supportedHTTPS supported 4 secs
jtaqb0qu.com
HTTP/3 supportedHTTPS supported 41 secs
dbsiggnature.in
HTTP/3 supportedHTTPS supported 1 min
nyasaneain.com
HTTP/3 supportedHTTPS supported 1 min
p569r.com
HTTP/3 supportedHTTPS supported 2 mins
p8j6ic.com
HTTP/3 supportedHTTPS supported 2 mins
chaoxun123.com
HTTP/3 supportedHTTPS supported 4 mins
jackpot168zen.top
HTTP/3 supportedHTTPS supported 4 mins
j8xj7j.com
HTTP/3 supportedHTTPS supported 4 mins
pazarlamailetisimi.com
HTTP/2 supportedHTTPS supported 5 mins
sangetods.com
HTTP/2 supportedHTTPS supported 5 mins
cung88.net
HTTP/3 supportedHTTPS supported 5 mins
malosolka.com
HTTP/2 supportedHTTPS supported 6 mins
cicijitu-profes.xyz
HTTP/3 supportedHTTPS supported 6 mins
fsonline.one
HTTP/3 supportedHTTPS supported 6 mins
Resources

Custom Widget

xfans.tokyo
Daily Visitors 75.6K
Monthly Visits 2.3M
Pages / Visit 7.62
HypeRank #35,821
Powered by HypeStat
Embed a live, always up-to-date stats card like this on your own site.
Get the embed code →

Hide/Remove your site data

• Use Show/Hide ESTIMATED data form to hide (Website worth, Daily ads revenue, Daily Visits, Daily Pageviews)
• Use Show/Hide WHOIS data form to hide whois data
• Use Remove form to remove all data
• If you have any problem with REMOVE/HIDE your data just drop an email at support (at) hypestat.com and we will remove/hide your site data manualy.