myfans.jp Myfans.jp

   
人気投稿の検索 | myfans[マイファンズ]

Domain Summary

What is the traffic rank for Myfans.jp?

• Myfans.jp ranks #795,814 globally on HypeStat.

What percent of global Internet users visit Myfans.jp?

• 0.0035968% of global Internet users visit Myfans.jp

How many people visit Myfans.jp each day?

• Myfans.jp receives approximately 177.3K visitors and 1,301,949 page impressions per day.

Which countries does Myfans.jp receive most of its visitors from?

• Myfans.jp is mostly visited by people located in Japan,Korea, Republic of,Taiwan.

How much Myfans.jp can earn?

• Myfans.jp should earn about $1,250.35/day from advertising revenue.

What is Myfans.jp estimated value?

• Estimated value of Myfans.jp is $1,256,969.88.

What IP addresses does Myfans.jp resolve to?

• Myfans.jp resolves to the IP addresses 76.76.21.21.

Where are Myfans.jp servers located in?

• Myfans.jp has servers located in Walnut, California, 91789, United States.

myfans.jp Profile

Title:人気投稿の検索 | myfans[マイファンズ]
Description:安全安心プライベートなSNS myfans[マイファンズ]。他のSNSでは載せられないお気に入りの裏アカウント（裏垢）を見つけよう！コスプレイヤー、人妻、元AV女優から元アイドルの裏アカウント（裏垢）が多数！日常系の動画、画像からちょっと過激な動画、画像まで多数のコンテンツを用意してます。
Category:Adult / Adult
Edit Site Info

What technologies does myfans.jp use?

These are the technologies used at myfans.jp. myfans.jp has a total of 7 technologies installed in 7 different categories.
JavaScript Frameworks
Ant Design Ant Design
Emotion Emotion
Development
Emotion Emotion
Tag Managers
Google Tag Manager Google Tag Manager
Security
HSTS HSTS
Miscellaneous
Open Graph Open Graph
JavaScript Libraries
Swiper Swiper
Web Servers
Vercel Vercel

myfans.jp Traffic Analysis

Myfans.jp is ranked #795,814 in the world. This website is viewed by an estimated 177.3K visitors daily, generating a total of 1.3M pageviews. This equates to about 5.4M monthly visitors. Myfans.jp traffic has decreased by 10.91% compared to last month.
Daily Visitors177.3K
23.65%
Monthly Visits5.4M
10.91%
Pages per Visit7.34
2.32%
Visit duration04:29
0.34%
Bounce Rate44.95%
1.15%
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
177,317
Monthly Visits:
5,372,705
Pages per Visit:
7.34
Daily Pageviews:
1,301,949
Avg. visit duration:
04:29
Bounce rate:
44.95%
Global Reach:
0.0035968%
Monthly Visits (SEMrush):
12,520,552
Monthly Unique Visitors (SEMrush):
4,608,573
Monthly Visits (SimilarWeb):
5,266,855
HypeRank:
795,814
SEMrush Rank:
279,382
SimilarWeb Rank:
8,240
*All traffic values are estimates only.

Traffic sources

Direct:
50.18%
Referral:
4.02%
Search:
15.41%
Social:
30.39%
Paid:
0%

Desktop vs Mobile

Desktop:
14.32%
Mobile:
85.68%

Total Visits Last 3 Months

5.2M
JAN
6M
FEB
5.4M
MAR

Visitors by country

Country
Users%
 
Japan 66.11%
 
Korea, Republic of 9.67%
 
Taiwan 4.68%
 
China 4.24%
 
United States 3.33%

Where do visitors go on myfans.jp?

 
Reach%Pageviews%PerUser
myfans.jp
95.39%93.98%2.2
url5871.myfans.jp
7.44%5.86%2
OTHER
0%0.15%0
Last update was 12 days ago
     
This can take up to 60 seconds. Please wait...

*HypeStat.com is not promoting or affiliated with myfans.jp 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:
782
Bing Index:
36

  ▼

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:
  myfans.jp
Rank:
(Rank based on keywords, cost and organic traffic)
  279,382
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  468
Organic Traffic:
(Number of visitors coming from top 20 search results)
  5,088
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $229.00
Full SEMrush Report >>

Revenue report ▼

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

How much would myfans.jp make?

Daily Revenue:
$1,250.35
Monthly Revenue:
$37,510.50
Yearly Revenue:
$456,377.75
*All earnings values are estimates only.

Daily earning by country

 
CountryPageviewsEarning
 
Japan 860,705$309.85
 
United States 43,331$209.29
 
Korea, Republic of 125,884$75.53
 
Taiwan 60,940$14.02
 
China 55,170$5.52

Loss of money due to Adblock?

Daily Revenue Loss:
$52.95
Monthly Revenue Loss:
$1,588.45
Yearly Revenue Loss:
$19,326.16
Daily Pageviews Blocked:
55,579
Monthly Pageviews Blocked:
1,667,357
Yearly Pageviews Blocked:
20,286,175

Daily revenue loss by country

 
CountryBlockedLost Money
 
United States 7,800$37.67
 
Japan 25,821$9.30
 
Korea, Republic of 5,035$3.02
 
Taiwan 9,750$2.24
 
China 7,172$0.72

How much is myfans.jp worth?

Website Value:
$1.3M

Ad Experience Report ▼

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

Mobile summary

Root domain:
myfans.jp
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:
myfans.jp
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:
myfans.jp
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 myfans.jp hosted? ▼

Myfans.jp may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.
Server IP:
76.76.21.21
ASN:
AS16509 
ISP:
Amazon.com, Inc. 
Server Location:
Walnut
California, CA
91789
United States, US
 

Other sites hosted on 76.76.21.21

There are no other sites hosted on this IP

How fast does myfans.jp load? ▼

The average loading time of myfans.jp is 51 ms. The Desktop speed index is 94 and mobile speed index is 59.
Average Load Time:
51 ms

Page Speed (Google PageSpeed Insights) - Desktop

94
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.

First Contentful Paint (FCP)1.7s 78% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 78% 12% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 12% 9% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 9%
First Input Delay (FID)2ms 99% of loads for this page have a fast (<100ms) First Input Delay (FID) 99% 0% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>300ms) First Input Delay (FID) 0%

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.

First Contentful Paint (FCP)942ms 90% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 90% 4% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 4% 4% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 4%
First Input Delay (FID)1ms 99% of loads for this page have a fast (<100ms) First Input Delay (FID) 99% 0% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>300ms) First Input Delay (FID) 0%

Lab Data

First Meaningful Paint 1.1 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more
Speed Index 1.1 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more
First Contentful Paint 1.1 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more
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
Performance budget  
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more
Largest Contentful Paint 1.3 s
Largest Contentful Paint marks the time at which the largest text or image is painted. 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
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
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
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
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
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
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

Page Speed (Google PageSpeed Insights) - Mobile

59
0-49 50-89 90-100 i

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.

First Contentful Paint (FCP)2.4s 78% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 57% 27% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 27% 15% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 15%
First Input Delay (FID)21ms 94% of loads for this page have a fast (<100ms) First Input Delay (FID) 94% 3% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 3% 1% of loads for this page have a slow (>300ms) First Input Delay (FID) 1%

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.

First Contentful Paint (FCP)1.3s 86% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 86% 9% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 9% 4% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 4%
First Input Delay (FID)18ms 99% of loads for this page have a fast (<100ms) First Input Delay (FID) 93% 4% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 4% 2% of loads for this page have a slow (>300ms) First Input Delay (FID) 2%

Lab Data

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
Max Potential First Input Delay 280 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. 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
Time to Interactive 5.9 s
Time to interactive is the amount of time it takes for the page to become fully interactive. 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
Largest Contentful Paint 6.3 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more
First Contentful Paint (3G) 11730 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 5.3 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more
First Meaningful Paint 5.3 s
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
Speed Index 5.3 s
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
Total Blocking Time 120 ms
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

Does myfans.jp 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 myfans.jp are reduced by 78%.
myfans.jp use br compression.
Original size: 40.2 KB
Compressed size: 8.67 KB
File reduced by: 31.53 KB (78%)

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. myfans.jp has 80 Safety Reputations.
Status:
  SAFE
Safety Reputations:
  80
Safety Confidence:
  51
Child Safety Reputations:
  10
Child Safety Confidence:
  51

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. myfans.jp supports HTTPS.
 myfans.jp supports HTTPS
     
Verifying SSL Support. Please wait...
Common Name: myfans.jp
Organization:
Location:
Issuer: R3
Valid from: Mar 28 20:52:40 2024 GMT
Valid until: Jun 26 20:52:39 2024 GMT
Authority: CA:FALSE
Keysize: 2048 Bits
Common Name: R3
Organization: Let's Encrypt
Location: US
Issuer: ISRG Root X1
Valid from: Sep 4 00:00:00 2020 GMT
Valid until: Sep 15 16:00:00 2025 GMT
Authority: CA:TRUE
Keysize: 2048 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.
 myfans.jp 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. 
access-control-allow-origin: *
age: 109144
cache-control: public, max-age=0, must-revalidate
content-disposition: inline; filename="ja"
content-encoding: br
content-type: text/html; charset=utf-8
date: Wed, 17 Apr 2024 18:23:12 GMT
etag: W/"c630087d69b2c7abb9e0c75f66739951"
server: Vercel
strict-transport-security: max-age=63072000
x-matched-path: /ja
x-vercel-cache: HIT
x-vercel-id: cle1::mwzcb-1713378192229-f6aa106fa531

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
TXT v=spf1 include:_spf.google.com include:sendgrid.net include:mail.zendesk.com ~all 300
TXT google-site-verification=o9scZF-IA16thisAS-NRs59zBY5mcJKIlhVzEF_lEFk 300
TXT google-site-verification=lKUVd3BCSo9-Qnz_rZAEq2astpf-hh-6kTIIzG3h5Ho 300
MX uwcqpkz2yidyqij2t2t2b2rbubxgjsupin7oztia3foyxysdryga.mx-verification.google.com 300
MX alt3.aspmx.l.google.com 300
MX alt1.aspmx.l.google.com 300
MX aspmx.l.google.com 300
MX alt2.aspmx.l.google.com 300
MX alt4.aspmx.l.google.com 300
SOA 900
Mname ns-1214.awsdns-23.org
Rname awsdns-hostmaster.amazon.com
Serial Number 1
Refresh 7200
Retry 900
Expire 1209600
Minimum TTL 86400
A 76.76.21.21 236
NS ns-610.awsdns-12.net 86335
NS ns-1214.awsdns-23.org 86335
NS ns-2011.awsdns-59.co.uk 86335
NS ns-232.awsdns-29.com 86335

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 June 11, 2021 and will expire on June 30, 2024 if not renewed. This website is now assigned through the registrar . The WHOIS data for this website's domain was last updated on April 9, 2024.
Domain Created:
2021-06-11
Domain Expires:
2024-06-30
Domain Updated:
2024-04-09
Domain Age:
2 years 10 months 19 days
Domain Owner:
(Not displayed by registrant's request)
WhoIs:
 

[ JPRS database provides information on network administration. Its use is    ]
[ restricted to network administration purposes. For further information,     ]
[ use 'whois -h whois.jprs.jp help'. To suppress Japanese output, add'/e'     ]
[ at the end of command, e.g. 'whois -h whois.jprs.jp ***/e'.                 ]
Domain Information:
[Domain Name]                   MYFANS.JP

[Registrant]                    (Not displayed by registrant's request)
                                For details -> https://jprs.jp/about/dom-rule/whois-concealment/ (only in Japanese)

[Name Server]                   ns-1214.awsdns-23.org
[Name Server]                   ns-610.awsdns-12.net
[Name Server]                   ns-232.awsdns-29.com
[Name Server]                   ns-2011.awsdns-59.co.uk
[Signing Key]                   

[Created on]                    2021/06/11
[Expires on]                    2024/06/30
[Status]                        Active
[Last Updated]                  2024/04/09 10:15:40 (JST)

Contact Information:
[Name]                          Whois Privacy Protection Service by onamae.com
[Email]                         email
[Web Page]                       
[Postal code]                   150-8512
[Postal Address]                Shibuya-ku
                                26-1 Sakuragaoka-cho
                                Cerulean Tower 11F
[Phone]                         +81.354562560
[Fax]