dmm.co.jp Dmm.co.jp

   
年齢認証 - FANZA

Domain Summary

What is the traffic rank for Dmm.co.jp?

• Dmm.co.jp ranks #9,464 globally on HypeStat.

What percent of global Internet users visit Dmm.co.jp?

0.1501749% of global Internet users visit Dmm.co.jp

How many people visit Dmm.co.jp each day?

• Dmm.co.jp receives approximately 7.4M visitors and 62,511,120 page impressions per day.

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

• Dmm.co.jp is mostly visited by people located in Japan,China,Taiwan.

How much Dmm.co.jp can earn?

• Dmm.co.jp should earn about $31,416.38/day from advertising revenue.

What is Dmm.co.jp estimated value?

• Estimated value of Dmm.co.jp is $35,908,368.71.

What IP addresses does Dmm.co.jp resolve to?

• Dmm.co.jp resolves to the IP addresses 13.248.196.236.

Where are Dmm.co.jp servers located in?

• Dmm.co.jp has servers located in Tokyo, Tokyo, 190-0031, United States.

dmm.co.jp Profile

Title:年齢認証 - FANZA
Description:成人向けコンテンツを取り扱うアダルト総合サイト。18歳未満の方のアクセスは固くお断りいたします。
Tags:
Category:Adult / Adult

What technologies does dmm.co.jp use?

These are the technologies used at dmm.co.jp. dmm.co.jp has a total of 5 technologies installed in 5 different categories.

dmm.co.jp Traffic Analysis

Dmm.co.jp is ranked #9,464 in the world. This website is viewed by an estimated 7.4M visitors daily, generating a total of 62.5M pageviews. This equates to about 224.3M monthly visitors. Dmm.co.jp traffic has increased by 11.58% compared to last month.
Daily Visitors7.4M
8.19%
Monthly Visits224.3M
11.58%
Pages per Visit8.44
7.29%
Visit duration07:33
7.41%
Bounce Rate34.13%
0.39%
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
7,403,510
Monthly Visits:
224,326,353
Pages per Visit:
8.44
Daily Pageviews:
62,511,120
Avg. visit duration:
07:33
Bounce rate:
34.13%
Global Reach:
0.1501749%
Monthly Visits (SEMrush):
409,449,493
Monthly Unique Visitors (SEMrush):
90,407,091
Monthly Visits (SimilarWeb):
219,906,224
HypeRank:
9,464
SEMrush Rank:
35,449
SimilarWeb Rank:
121
*All traffic values are estimates only.

Traffic sources

Direct:
50.59%
Referral:
18.08%
Search:
22.21%
Social:
9.12%
Paid:
0%

Desktop vs Mobile

Desktop:
9.27%
Mobile:
90.73%

Total Visits Last 3 Months

185.3M
NOV
201M
DEC
224.3M
JAN

Visitors by country

Country
Users%
 
Japan 91.18%
 
China 2.30%
 
Taiwan 1.82%
 
Korea, Republic of 0.83%
 
United States 0.71%

Where do visitors go on dmm.co.jp?

 
Reach%Pageviews%PerUser
dmm.co.jp
74.16%79.01%7.11
al.dmm.co.jp
15.99%2.40%1.0
games.dmm.co.jp
8.06%2.89%2.4
special.dmm.co.jp
7.96%1.27%1.1
accounts.dmm.co.jp
7.65%1.66%1.4
Last update was 17 days ago
     
This can take up to 60 seconds. Please wait...

*HypeStat.com is not promoting or affiliated with dmm.co.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:
17,500,000
Bing Index:
483,000
Baidu Index:
11

Moz Data

Domain Authority (DA) is a metric developed by Moz. DA is a score that predicts the ranking potential of a website on search engine result pages (SERPs). Moz calculates Domain Authority on a logarithmic scale from 1 to 100, with higher scores indicating a greater likelihood of ranking well in search results. Moz Domain Authority of dmm.co.jp is 85.
Domain Authority:
  85
Page Authority:
  60
MozRank:
  6

 

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:
  dmm.co.jp
Rank:
(Rank based on keywords, cost and organic traffic)
  35,449
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  18,415
Organic Traffic:
(Number of visitors coming from top 20 search results)
  56,924
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $90,287.00

Revenue report

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

How much would dmm.co.jp make?

Daily Revenue:
$31,416.38
Monthly Revenue:
$942,491.40
Yearly Revenue:
$11,466,978.70
*All earnings values are estimates only.

Daily earning by country

 
CountryPageviewsEarning
 
Japan 56,999,924$20,519.97
 
United States 446,353$2,155.88
 
Korea, Republic of 520,755$312.45
 
Taiwan 1,139,512$262.09
 
China 1,438,365$143.84

Loss of money due to Adblock?

Daily Revenue Loss:
$1,076.79
Monthly Revenue Loss:
$32,303.67
Yearly Revenue Loss:
$393,027.97
Daily Pageviews Blocked:
2,180,481
Monthly Pageviews Blocked:
65,414,421
Yearly Pageviews Blocked:
795,875,457

Daily revenue loss by country

 
CountryBlockedLost Money
 
Japan 1,709,998$615.60
 
United States 80,343$388.06
 
Taiwan 182,322$41.93
 
China 186,987$18.70
 
Korea, Republic of 20,830$12.50

How much is dmm.co.jp worth?

Website Value:
$35.9M

Ad Experience Report

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

Mobile summary

Root domain:
dmm.co.jp
Last Change Time:
(The last time that the site changed status.)
2022-02-25 05:09:36
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.)
Passing

Desktop summary

Root domain:
dmm.co.jp
Last Change Time:
(The last time that the site changed status.)
2022-02-25 05:09:36
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.)
Passing

Abusive Experience Report

Summary of the abusive experience rating of a website.
Root domain:
dmm.co.jp
Last Change Time:
(The last time that the site changed status.)
2022-02-25 05:09:36
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.)
Passing

Where is dmm.co.jp hosted?

Dmm.co.jp may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.
Server IP:
13.248.196.236
ASN:
AS16509 
ISP:
Amazon.com, Inc. 
Server Location:
Tokyo
Tokyo, 13
190-0031
United States, US
 

Other sites hosted on 13.248.196.236

There are no other sites hosted on this IP

How fast does dmm.co.jp load?

The average loading time of dmm.co.jp is 4136 ms. The Desktop speed index is 66 and mobile speed index is 43.
Average Load Time:
4136 ms

Page Speed (Google PageSpeed Insights) - Desktop

66
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)1.3s 84% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 84% 9% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 9% 6% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 6%
First Input Delay (FID)1ms 97% of loads for this page have a fast (<100ms) First Input Delay (FID) 97% 1% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 1% 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 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.8s 73% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 73% 18% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 18% 7% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 7%
First Input Delay (FID)3ms 98% of loads for this page have a fast (<100ms) First Input Delay (FID) 98% 1% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 1% 0% of loads for this page have a slow (>300ms) First Input Delay (FID) 0%

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
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
Total Blocking Time 480 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
Time to Interactive 2.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive. 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
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
First Meaningful Paint 1.1 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more
Does not have 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
Largest Contentful Paint 1.2 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more
Max Potential First Input Delay 440 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more
Performance budget  
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more
Speed Index 3.1 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more

Page Speed (Google PageSpeed Insights) - Mobile

43
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)1.9s 84% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 72% 18% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 18% 9% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 9%
First Input Delay (FID)181ms 67% of loads for this page have a fast (<100ms) First Input Delay (FID) 67% 14% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 14% 17% of loads for this page have a slow (>300ms) First Input Delay (FID) 17%

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)2.0s 69% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 69% 22% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 22% 8% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 8%
First Input Delay (FID)36ms 98% of loads for this page have a fast (<100ms) First Input Delay (FID) 83% 8% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 8% 7% of loads for this page have a slow (>300ms) First Input Delay (FID) 7%

Lab Data

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 4.2 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
First Meaningful Paint 3.3 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more
Speed Index 7.8 s
Speed Index shows how quickly the contents of a page are visibly populated. 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
First Contentful Paint (3G) 7005.5 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 3.3 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more
Total Blocking Time 1,040 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more
Performance budget  
Keep the quantity and size of network requests under the targets set by the provided performance budget. 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
Time to Interactive 9.7 s
Time to interactive is the amount of time it takes for the page to become fully interactive. 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 580 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more

Does dmm.co.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 dmm.co.jp are reduced by 63%.
dmm.co.jp use gzip compression.
Original size: 18.32 KB
Compressed size: 6.62 KB
File reduced by: 11.7 KB (63%)

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. dmm.co.jp has 86 Safety Reputations.
Status:
  SAFE
Safety Reputations:
  86
Safety Confidence:
  39
Child Safety Reputations:
  11
Child Safety Confidence:
  37

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. dmm.co.jp supports HTTPS.
 dmm.co.jp supports HTTPS
     
Verifying SSL Support. Please wait...
Common Name: *.dmm.co.jp
Organization: DMM.com LLC
Location: Minato-ku, Tokyo, JP
Issuer: GlobalSign RSA OV SSL CA 2018
Valid from: Apr 19 01:41:25 2023 GMT
Valid until: May 20 01:41:24 2024 GMT
Authority: CA:FALSE
Keysize: 2048 Bits
Common Name: GlobalSign RSA OV SSL CA 2018
Organization: GlobalSign nv-sa
Location: BE
Issuer: GlobalSign
Valid from: Nov 21 00:00:00 2018 GMT
Valid until: Nov 21 00:00:00 2028 GMT
Authority: CA:TRUE
Keysize: 2048 Bits
Common Name: GlobalSign
Organization: GlobalSign
Location:
Issuer: GlobalSign Root CA
Valid from: Sep 19 00:00:00 2018 GMT
Valid until: Jan 28 12:00:00 2028 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.
 dmm.co.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.
server: awselb/2.0
date: Fri, 01 Mar 2024 20:39:04 GMT
content-type: text/html
content-length: 134
location: https://www.dmm.co.jp:443/

HTTP/2 302 
content-type: text/html; charset=iso-8859-1
content-length: 187
location: https://www.dmm.co.jp/top/
date: Fri, 01 Mar 2024 20:39:05 GMT
server: Apache
vary: Accept-Encoding
content-encoding: gzip
x-cache: Miss from cloudfront
via: 1.1 43b9d5592d1dc6a44adc7ebaaf183280.cloudfront.net (CloudFront)
x-amz-cf-pop: FRA56-P9
x-amz-cf-id: o4JyEyABCWPCeUXwaySb7_ngb_VkX8GBOgfWZXXD8Djrgrvg8RZ9sw==

HTTP/2 302 
content-type: text/html; charset=UTF-8
content-length: 92
location: https://www.dmm.co.jp/age_check/=/?rurl=https%3A%2F%2Fwww.dmm.co.jp%2Ftop%2F
date: Fri, 01 Mar 2024 20:39:06 GMT
server: uvicorn
encoding: utf-8
content-security-policy: frame-ancestors 'none';
cache-control: no-store
vary: User-Agent
set-cookie: top_pv_uid=0946297d-baa4-449f-ad0b-47831cac217f; Domain=.dmm.co.jp; Max-Age=31536000; Path=/; Secure
set-cookie: top_dummy=a173c87a-c4e0-476d-9758-1ae1a4a216f3; Domain=.dmm.co.jp; Max-Age=31536000; Path=/; Secure
x-cache: Miss from cloudfront
via: 1.1 43b9d5592d1dc6a44adc7ebaaf183280.cloudfront.net (CloudFront)
x-amz-cf-pop: FRA56-P9
x-amz-cf-id: laVDAS0LOdyTx39_rysF5FuwL1QTX0VTL7oskhBLWC9kmFUfXrejIg==

HTTP/2 200 
content-type: text/html; charset=UTF-8
content-length: 6779
date: Fri, 01 Mar 2024 20:39:07 GMT
server: Apache
set-cookie: ckcy=2; expires=Sat, 01-Mar-2025 20:39:07 GMT; path=/; domain=dmm.co.jp
set-cookie: cklg=ja; expires=Sat, 01-Mar-2025 20:39:07 GMT; path=/; domain=dmm.co.jp
pragma: no-cache
cache-control: no-cache
vary: Accept-Encoding,User-Agent
content-encoding: gzip
x-cache: Miss from cloudfront
via: 1.1 43b9d5592d1dc6a44adc7ebaaf183280.cloudfront.net (CloudFront)
x-amz-cf-pop: FRA56-P9
x-amz-cf-id: qDlyNuj0V1XPor6GhHk_iElX0Tq3ydzYeAs4-5Ps5ygV7xO-3GH1Tw==

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
MX swiss.dmm.co.jp 900
TXT google-site-verification=J_DConcX7NP6-GoMx6i3zLb9FtVd6o96c_VjkAmXjfA 3600
TXT google-site-verification=1X3BJ3lM80OZt5pggJD1Rkygcg8-bNBxni9lrUas4dY 3600
TXT google-site-verification=QkffC_LJoz60tqjWTUDwamUlzLvcHP5jOvTrKTX5Xp0 3600
TXT v=spf1 ip4:203.209.144.0/20 ip4:202.6.244.0/22 ip4:103.254.144.0/22 ip4:157.112.88.58/32 include:cust-spf.exacttarget.com include:md93.maildealer.jp -all 3600
TXT google-site-verification=woCIjqAdinOBUmubEGTcJ9_6xGNQSxB9gyGAejoo5lU 3600
TXT google-site-verification=qGTSGF6UUF0izRJGixvWd1UR4jhE2TzIe0ql08VyMXY 3600
TXT google-site-verification=gEWB9py1UwtAA52457BNxah-YeGF_jpiBx2dwIg_-c0 3600
TXT amazonses:qv0RaqRbY/aNsIUOzwskhSDBZI+nJPAFIC8zXRj84Zs= 3600
TXT google-site-verification=0ckwE20OPaP5en5hOmGdeX4QY5sSm72N9D3twPrGa0o 3600
TXT google-site-verification=_Ci92-uIvOKSTOj3ddmCQL6F6C3Y6eJk4LE0G2HEzrE 3600
TXT google-site-verification=JtyOrlh0YaMUYl9bsrBknfQUdQWx4AUF9F53QhOHHSI 3600
SOA 300
Mname ns1.p201.dns.oraclecloud.net
Rname hostmaster.dmm.co.jp
Serial Number 2019073778
Refresh 3600
Retry 600
Expire 604800
Minimum TTL 1800
A 13.248.196.236 222
NS a18-66.akam.net 86322
NS a1-198.akam.net 86322
NS ns4.p201.dns.oraclecloud.net 86322
NS ns3.p201.dns.oraclecloud.net 86322
NS ns2.p201.dns.oraclecloud.net 86322
NS ns1.p201.dns.oraclecloud.net 86322
NS a13-64.akam.net 86322
NS a14-65.akam.net 86322
NS a9-67.akam.net 86322
NS a12-67.akam.net 86322

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 July 10, 2006 and will expire on March 19, 2024 if not renewed. This website is now assigned through the registrar . The WHOIS data for this website's domain was last updated on January 26, 2024.
Domain Created:
2006-07-10
Domain Updated:
2024-01-26
Domain Age:
17 years 8 months 9 days
Domain Owner:
DMM.com LLC
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:
a. [Domain Name]                DMM.CO.JP
g. [Organization]               DMM.com LLC
l. [Organization Type]          Limited Liability Company
m. [Administrative Contact]     TN46930JP
n. [Technical Contact]          TM49224JP
p. [Name Server]                a1-198.akam.net
p. [Name Server]                a12-67.akam.net
p. [Name Server]                a13-64.akam.net
p. [Name Server]                a14-65.akam.net
p. [Name Server]                a18-66.akam.net
p. [Name Server]                a9-67.akam.net
p. [Name Server]                ns1.p201.dns.oraclecloud.net
p. [Name Server]                ns2.p201.dns.oraclecloud.net
p. [Name Server]                ns3.p201.dns.oraclecloud.net
p. [Name Server]                ns4.p201.dns.oraclecloud.net
s. [Signing Key]                
[State]                         Connected (2024/07/31)
[Registered Date]               2006/07/10
[Connected Date]                2006/07/10
[Last Update]                   2024/01/26 13:52:39 (JST)