digle.tokyo Digle.tokyo

   
DIGLE

Domain Summary

What is the traffic rank for Digle.tokyo?

• Digle.tokyo ranks #3,318,991 globally on HypeStat.

What percent of global Internet users visit Digle.tokyo?

• 0.000126% of global Internet users visit Digle.tokyo

How many people visit Digle.tokyo each day?

• Digle.tokyo receives approximately 6.2K visitors and 11,256 page impressions per day.

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

• Digle.tokyo is mostly visited by people located in Japan,United States,Korea, Republic of.

How much Digle.tokyo can earn?

• Digle.tokyo should earn about $4.81/day from advertising revenue.

What is Digle.tokyo estimated value?

• Estimated value of Digle.tokyo is $4,580.89.

What IP addresses does Digle.tokyo resolve to?

• Digle.tokyo resolves to the IP addresses 54.178.249.143.

Where are Digle.tokyo servers located in?

• Digle.tokyo has servers located in Tokyo, Tokyo, 151-0053, Japan.

digle.tokyo Profile

Title:DIGLE Description:『DIGLE』（ディグル）は世界１億人のユーザーを誇る音楽ストリーミングサービス『Spotify』をベースにした音楽共有プラットフォーム です。 ミュージシャンやDJ、音楽メディア、そして自分の友人がお気に入りのプレイリストをシェアしてくれて、いつでもすぐ聞くことが出来ます。お互いのお気に入りを教えあって音楽を通じた楽しい毎日をみんなで作りましょう！
Category:Arts and Entertainment / Other Arts and Entertainment
About: Digle.tokyo is an innovative online platform designed to facilitate the discovery and sharing of digital content, focusing on the intersection of technology and culture in Tokyo. The website offers a user-friendly interface characterized by a clean, minimalist design that prioritizes accessibility and ease of navigation. Key features include curated content collections, user-generated submissions, and interactive community forums, enabling users to engage with a diverse array of topics ranging from art and design to technology and local events. By fostering collaboration and dialogue among users, Digle.tokyo serves as a vital resource for both locals and visitors seeking to explore the dynamic cultural landscape of Tokyo.
Edit Site Info

What technologies does digle.tokyo use?

These are the technologies used at digle.tokyo. digle.tokyo has a total of 5 technologies installed in 4 different categories.
Web Servers
Amazon EC2 Amazon EC2
Apache HTTP Server Apache HTTP Server
PaaS
Amazon Web Services Amazon Web Services
Web Server Extensions
OpenSSL OpenSSL
Programming Languages
PHP PHP

digle.tokyo Traffic Analysis

Digle.tokyo is ranked #3,318,991 in the world. This website is viewed by an estimated 6.2K visitors daily, generating a total of 11.3K pageviews. This equates to about 188.2K monthly visitors. Digle.tokyo traffic has decreased by 68.92% compared to last month.
Daily Visitors6.2K
37.26%
Monthly Visits188.2K
68.92%
Pages per Visit1.81
15.61%
Visit duration01:27
2.6%
Bounce Rate59.85%
2.21%
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
6,211
Monthly Visits:
188,193
Pages per Visit:
1.81
Daily Pageviews:
11,256
Avg. visit duration:
01:27
Bounce rate:
59.85%
Global Reach:
0.000126%
Monthly Visits (SEMrush):
124,514
Monthly Unique Visitors (SEMrush):
110,949
Monthly Visits (SimilarWeb):
190,137
HypeRank:
3,318,991
SEMrush Rank:
3,343,366
SimilarWeb Rank:
229,337
*All traffic values are estimates only.

Traffic sources

Direct:
12.97%
Referral:
0.67%
Search:
86.23%
Social:
0.13%
Paid:
0%

Desktop vs Mobile

Desktop:
36.55%
Mobile:
63.45%

Total Visits Last 3 Months

244.9K
DEC
605.5K
JAN
188.2K
FEB

Visitors by country

Country
Users%
 
Japan 95.81%
 
United States 1.42%
 
Korea, Republic of 1.03%
 
Viet Nam 1.03%
 
Taiwan 0.69%

digle.tokyo Traffic Flow

The largest share of traffic to digle.tokyo comes from Google organic visits (59.78%). After leaving the site, the most common destination is rakuten.co.jp and google.com .

  ▼

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:
  digle.tokyo
Rank:
(Rank based on keywords, cost and organic traffic)
  3,343,366
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  398
Organic Traffic:
(Number of visitors coming from top 20 search results)
  127
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $18.00
Full SEMrush Report >>

Which sites are competitors to digle.tokyo?

Websites similar to digle.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.
Domain
CompareDaily Visitors
teket.jp
Compare >8.1K
skream.jp
Compare >7.7K
Last update was 162 days ago
     
This can take up to 60 seconds. Please wait...

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

Revenue report ▼

digle.tokyo would generate approximately $4.8 per day if the source of income were advertisements, which equates to an estimated monthly revenue of $144.3 and annual gross revenue of approximately $1.8K. Based on these figures, the site's net worth is estimated at around $4.6K.

How much would digle.tokyo make?

Daily Revenue:
$4.81
Monthly Revenue:
$144.30
Yearly Revenue:
$1,755.65
*All earnings values are estimates only.

Daily earning by country

 
CountryPageviewsEarning
 
Japan 10,784$3.88
 
United States 160$0.77
 
Korea, Republic of 116$0.07
 
Viet Nam 115$0.05
 
Taiwan 78$0.02

Loss of money due to Adblock?

Daily Revenue Loss:
$0.26
Monthly Revenue Loss:
$7.90
Yearly Revenue Loss:
$96.10
Daily Pageviews Blocked:
374
Monthly Pageviews Blocked:
11,222
Yearly Pageviews Blocked:
136,534

Daily revenue loss by country

 
CountryBlockedLost Money
 
United States 29$0.14
 
Japan 324$0.12
 
Taiwan 13$0.00
 
Korea, Republic of 5$0.00
 
Viet Nam 5$0.00

How much is digle.tokyo worth?

Website Value:
$4.6K

Ad Experience Report ▼

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

Mobile summary

Root domain:
digle.tokyo
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:
digle.tokyo
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:
digle.tokyo
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 digle.tokyo hosted? ▼

Digle.tokyo may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.
Server IP:
54.178.249.143
ASN:
AS16509 
ISP:
Amazon.com, Inc. 
Server Location:
Tokyo
Tokyo, 13
151-0053
Japan, JP
 

Other sites hosted on 54.178.249.143

There are no other sites hosted on this IP

How fast does digle.tokyo load? ▼

The average loading time of digle.tokyo is 1278 ms. The Desktop speed index is 100 and mobile speed index is 100.
Average Load Time:
1278 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

First Contentful Paint 0.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
Time to Interactive 0.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
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
INP breakdown  
Start investigating by looking at the longest subpart. how to improve INP
Largest Contentful Paint 0.2 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 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
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
LCP request discovery  
by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading Optimize LCP

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

INP breakdown  
Start investigating by looking at the longest subpart. how to improve INP
Time to Interactive 0.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
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
First Contentful Paint 0.8 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
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
Largest Contentful Paint 0.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
Speed Index 2.2 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
LCP request discovery  
by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading Optimize LCP

Does digle.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 digle.tokyo are reduced by %.
digle.tokyo does not use compression.
Original size: 954 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. digle.tokyo supports HTTPS.
 digle.tokyo supports HTTPS
     
Verifying SSL Support. Please wait...
Common Name: digle.tokyo
Organization:
Location:
Issuer: R12
Valid from: Jan 12 02:31:54 2026 GMT
Valid until: Apr 12 02:31:53 2026 GMT
Authority: CA:FALSE
Keysize: 2048 Bits
Common Name: R12
Organization: Let's Encrypt
Location: US
Issuer: ISRG Root X1
Valid from: Mar 13 00:00:00 2024 GMT
Valid until: Mar 12 23:59:59 2027 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.
 digle.tokyo 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. 
last-modified: Fri, 16 Aug 2024 02:49:30 GMT
etag: "3ba-61fc4022ca847"
accept-ranges: bytes
content-length: 954
content-type: text/html; charset=UTF-8
date: Tue, 31 Mar 2026 18:22:24 GMT
server: Apache/2.4.61 (Amazon) OpenSSL/1.0.2k-fips PHP/7.2.34

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
SOA 86400
Mname dns01.gmoserver.jp
Rname hostmaster.digle.tokyo
Serial Number 2021122102
Refresh 28800
Retry 7200
Expire 604800
Minimum TTL 600
MX mx10.gmoserver.jp 600
NS dns02.gmoserver.jp 600
NS dns01.gmoserver.jp 600
A 54.178.249.143 600
TXT v=spf1 include:spf10.gmoserver.jp include:mail.zendesk.com ~all 600

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: DIGLE.TOKYO
Registry Domain ID: DO791175-GMO
Registrar WHOIS Server:
Registrar URL: http://www.onamae.com/
Updated Date: 2025-12-22T07:09:57.0Z
Creation Date: 2016-10-23T05:53:14.0Z
Registry Expiry Date: 2026-10-23T23:59:59.0Z
Registrar: GMO Internet Group, Inc.
Registrar IANA ID: 49
Registrar Abuse Contact Email: email
Registrar Abuse Contact Phone: +81.337709199
Domain Status: ok https://icann.org/epp#ok
Registrant State/Province:
Registrant Country:
Registrant Email:
Admin Email:
Tech Email:
Name Server: DNS01.GMOSERVER.JP
Name Server: DNS02.GMOSERVER.JP
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2026-03-31T18:23:11.0Z