cookierunstore.com Cookierunstore.com

   
쿠키런 스토어

Domain Summary

What is the traffic rank for Cookierunstore.com?

• Cookierunstore.com ranks #75,257 globally on HypeStat.

What percent of global Internet users visit Cookierunstore.com?

• 0.000373% of global Internet users visit Cookierunstore.com

How many people visit Cookierunstore.com each day?

• Cookierunstore.com receives approximately 18.4K visitors and 89,871 page impressions per day.

Which countries does Cookierunstore.com receive most of its visitors from?

• Cookierunstore.com is mostly visited by people located in United States,Canada,United Arab Emirates.

How much Cookierunstore.com can earn?

• Cookierunstore.com should earn about $390.78/day from advertising revenue.

What is Cookierunstore.com estimated value?

• Estimated value of Cookierunstore.com is $379,949.04.

What IP addresses does Cookierunstore.com resolve to?

• Cookierunstore.com resolves to the IP addresses 183.111.232.83.

Where are Cookierunstore.com servers located in?

• Cookierunstore.com has servers located in South Korea.

cookierunstore.com Profile

Title:쿠키런 스토어
Tags:
cookierun store
Category:Games / Video Games Consoles and Accessories
Edit Site Info

What technologies does cookierunstore.com use?

These are the technologies used at cookierunstore.com. cookierunstore.com has a total of 5 technologies installed in 5 different categories.
Security
HSTS HSTS
Analytics
Naver Analytics Naver Analytics
Miscellaneous
Open Graph Open Graph
Web Servers
OpenResty OpenResty
Nginx Nginx
Reverse proxies
Nginx Nginx

cookierunstore.com Traffic Analysis

Cookierunstore.com is ranked #75,257 in the world. This website is viewed by an estimated 18.4K visitors daily, generating a total of 89.9K pageviews. This equates to about 557.2K monthly visitors. Cookierunstore.com traffic has decreased by 46.82% compared to last month.
Daily Visitors18.4K
36.41%
Monthly Visits557.2K
46.82%
Pages per Visit4.89
2728.35%
Visit duration01:58
27.36%
Bounce Rate50.20%
25.11%
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
18,391
Monthly Visits:
557,247
Pages per Visit:
4.89
Daily Pageviews:
89,871
Avg. visit duration:
01:58
Bounce rate:
50.20%
Global Reach:
0.000373%
Monthly Visits (SEMrush):
446,617
Monthly Unique Visitors (SEMrush):
271,232
Monthly Visits (SimilarWeb):
540,907
HypeRank:
75,257
SEMrush Rank:
316,790
SimilarWeb Rank:
75,257
*All traffic values are estimates only.

Traffic sources

Direct:
82.55%
Referral:
1.57%
Search:
15.37%
Social:
0.21%
Paid:
0.30%

Desktop vs Mobile

Desktop:
24.70%
Mobile:
75.30%

Total Visits Last 3 Months

96K
DEC
1M
JAN
557.2K
FEB

Visitors by country

Country
Users%
 
United States 53.06%
 
Canada 4.35%
 
United Arab Emirates 3.16%
 
United Kingdom 2.65%
 
Philippines 2.03%

Which sites are competitors to cookierunstore.com?

Websites similar to cookierunstore.com 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.
Last update was 96 days ago
     
This can take up to 60 seconds. Please wait...

*HypeStat.com is not promoting or affiliated with cookierunstore.com 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:
2,370

  ▼

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:
  cookierunstore.com
Rank:
(Rank based on keywords, cost and organic traffic)
  316,790
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  1,460
Organic Traffic:
(Number of visitors coming from top 20 search results)
  5,256
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $1,557.00
Full SEMrush Report >>

Revenue report ▼

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

How much would cookierunstore.com make?

Daily Revenue:
$390.78
Monthly Revenue:
$11,723.40
Yearly Revenue:
$142,634.70
*All earnings values are estimates only.

Daily earning by country

 
CountryPageviewsEarning
 
United States 47,687$230.33
 
Canada 3,905$23.59
 
United Kingdom 2,385$6.39
 
United Arab Emirates 2,838$2.70
 
Philippines 1,827$0.37

Loss of money due to Adblock?

Daily Revenue Loss:
$48.78
Monthly Revenue Loss:
$1,463.47
Yearly Revenue Loss:
$17,805.59
Daily Pageviews Blocked:
10,467
Monthly Pageviews Blocked:
314,010
Yearly Pageviews Blocked:
3,820,456

Daily revenue loss by country

 
CountryBlockedLost Money
 
United States 8,584$41.46
 
Canada 976$5.90
 
United Kingdom 382$1.02
 
United Arab Emirates 397$0.38
 
Philippines 128$0.03

How much is cookierunstore.com worth?

Website Value:
$379.9K

Ad Experience Report ▼

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

Mobile summary

Root domain:
cookierunstore.com
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:
cookierunstore.com
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:
cookierunstore.com
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 cookierunstore.com hosted? ▼

Cookierunstore.com may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.
Server IP:
183.111.232.83
ASN:
AS4766 
ISP:
Korea Telecom 
Server Location:

South Korea, KR
 

Other sites hosted on 183.111.232.83

How fast does cookierunstore.com load? ▼

The average loading time of cookierunstore.com is 714 ms. The Desktop speed index is 88 and mobile speed index is 64.
Average Load Time:
714 ms

Page Speed (Google PageSpeed Insights) - Desktop

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

Cumulative Layout Shift (CLS)1ms 99% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 99% 0% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)788ms 75% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 75% 21% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 21% 3% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 3%
First Contentful Paint (FCP)1.9s 73% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 73% 16% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 16% 9% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 9%
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)9ms 99% of loads for this page have a fast (<200ms) Interaction To Next Paint (INP) 99% 0% of loads for this page have an average (200ms ~ 500ms) Interaction To Next Paint (INP) 0% 0% of loads for this page have a slow (>500ms) Interaction To Next Paint (INP) 0%
Largest Contentful Paint (LCP)1.9s 85% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 85% 10% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 10% 4% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 4%

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)1ms 99% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 99% 0% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)796ms 75% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 75% 21% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 21% 3% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 3%
First Contentful Paint (FCP)1.9s 73% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 73% 17% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 17% 9% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 9%
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)9ms 99% of loads for this page have a fast (<200ms) Interaction To Next Paint (INP) 99% 0% of loads for this page have an average (200ms ~ 500ms) Interaction To Next Paint (INP) 0% 0% of loads for this page have a slow (>500ms) Interaction To Next Paint (INP) 0%
Largest Contentful Paint (LCP)1.9s 85% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 85% 10% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 10% 4% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 4%

Lab Data

Total Blocking Time 10 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 Delay 70 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 Interactive 1.6 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
Forced reflow  
Many APIs, typically reading layout geometry, force the rendering engine to pause script execution in order to calculate the style and layout. Learn more about and its mitigations. forced reflow
Font display  
Consider setting to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with . font-display font metric overrides
Largest Contentful Paint 1.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
INP by phase  
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
First Meaningful Paint  
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
Long critical network tree  
by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Avoid chaining critical requests
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 about using the viewport meta tag
Optimize DOM size  
A large DOM can increase the duration of style calculations and layout reflows, impacting page responsiveness. A large DOM will also increase memory usage. Learn how to avoid an excessive DOM size
First Contentful Paint 1.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
Speed Index 2.1 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
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 how to defer third-parties with a facade
CSS Selector costs  
If Recalculate Style costs remain high, selector optimization can reduce them. with both high elapsed time and high slow-path %. Simpler selectors, fewer selectors, a smaller DOM, and a shallower DOM will all reduce matching costs. Optimize the selectors
Preconnect to required origins  
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins

Page Speed (Google PageSpeed Insights) - Mobile

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

Cumulative Layout Shift (CLS)0ms 99% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 99% 0% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)794ms 75% of loads for this page have a fast (<800s) Time To First Byte (TTFB) 75% 18% of loads for this page have an average (800s ~ 1800s) Time To First Byte (TTFB) 18% 6% of loads for this page have a slow (>1800s) Time To First Byte (TTFB) 6%
First Contentful Paint (FCP)1.9s 73% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 73% 13% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 13% 12% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 12%
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)61ms 99% of loads for this page have a fast (<200s) Interactive To Next Paint (INP) 98% 1% of loads for this page have an average (200s ~ 500s) Interactive To Next Paint (INP) 1% 0% of loads for this page have a slow (>500s) Interactive To Next Paint (INP) 0%
Largest Contentful Paint (LCP)1.9s 85% of loads for this page have a fast (<2500s) Largest Contentful Paint (LCP) 82% 10% of loads for this page have an average (2500s ~ 4000s) Largest Contentful Paint (LCP) 10% 6% of loads for this page have a slow (>4000s) Largest Contentful Paint (LCP) 6%

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 99% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 99% 0% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)794ms 75% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 75% 18% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 18% 6% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 6%
First Contentful Paint (FCP)1.9s 73% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 73% 13% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 13% 12% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 12%
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)61ms 98% of loads for this page have a fast (<0.2s) Interactive To Next Paint (INP) 98% 1% of loads for this page have an average (0.2s ~ 0.5s) Interactive To Next Paint (INP) 1% 0% of loads for this page have a slow (>0.5s) Interactive To Next Paint (INP) 0%
Largest Contentful Paint (LCP)1.9s 82% of loads for this page have a fast (<2.5s)Largest Contentful Paint (LCP) 82% 10% of loads for this page have an average (2.5s ~ 4s)Largest Contentful Paint (LCP) 10% 6% of loads for this page have a slow (>4s)Largest Contentful Paint (LCP) 6%

Lab Data

INP by phase  
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
First Meaningful Paint  
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
Forced reflow  
Many APIs, typically reading layout geometry, force the rendering engine to pause script execution in order to calculate the style and layout. Learn more about and its mitigations. forced reflow
CSS Selector costs  
If Recalculate Style costs remain high, selector optimization can reduce them. with both high elapsed time and high slow-path %. Simpler selectors, fewer selectors, a smaller DOM, and a shallower DOM will all reduce matching costs. Optimize the selectors
Font display  
Consider setting to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with . font-display font metric overrides
First Contentful Paint 5.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
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 how to defer third-parties with a facade
Optimize DOM size  
A large DOM can increase the duration of style calculations and layout reflows, impacting page responsiveness. A large DOM will also increase memory usage. Learn how to avoid an excessive DOM size
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 about using the viewport meta tag
Time to Interactive 6.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
Preconnect to required origins  
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins
Max Potential First Input Delay 50 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
Long critical network tree  
by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Avoid chaining critical requests
Largest Contentful Paint 6.6 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 5.3 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric

Does cookierunstore.com 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 cookierunstore.com are reduced by 71%.
cookierunstore.com use gzip compression.
Original size: 54.07 KB
Compressed size: 15.29 KB
File reduced by: 38.78 KB (71%)

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. cookierunstore.com has 80 Safety Reputations.
Status:
  SAFE
Safety Reputations:
  80
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. cookierunstore.com supports HTTPS.
 cookierunstore.com supports HTTPS
     
Verifying SSL Support. Please wait...
Common Name: cookierunstore.com
Organization:
Location:
Issuer: R10
Valid from: Feb 16 15:08:36 2025 GMT
Valid until: May 17 15:08:35 2025 GMT
Authority: CA:FALSE
Keysize: 2048 Bits
Common Name: R10
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.
 cookierunstore.com 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: openresty
date: Mon, 17 Mar 2025 00:20:42 GMT
content-type: text/html; charset=utf-8
vary: Accept-Encoding
p3p: CP="NOI ADM DEV PSAi COM NAV OUR OTR STP IND DEM"
expires: Mon, 26 Jul 1997 05:00:00 GMT
cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
pragma: no-cache
x-cache-valid: YES
strict-transport-security: max-age=31536000
referrer-policy: strict-origin-when-cross-origin
x-content-type-options: nosniff
x-hrpcs-signal: 1
x-hrpcs-ttl: 300s
last-modified: Mon, 17 Mar 2025 00:20:42 GMT
x-xss-protection: 1;mode=block
content-encoding: gzip
x-hurl: /devsisters1view_pcUSagent_pc
x-iscacheurl: YES
x-ttl: 300.000
x-cache: MISS
x-hits: 0
x-anigif: 
accept-ranges: bytes

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 google-site-verification=aBGOwze-qDuHdVJTRt9HN_SLm3aVBjejf-XQp1vTOE4 1800
SOA 1800
Mname cookierunstore.com
Rname postmaster.cookierunstore.com
Serial Number 20200327
Refresh 10800
Retry 3600
Expire 3600000
Minimum TTL 43200
MX ASPMX.L.GOOGLE.com 1800
MX ALT4.ASPMX.L.GOOGLE.com 1800
MX ALT2.ASPMX.L.GOOGLE.com 1800
MX ALT1.ASPMX.L.GOOGLE.com 1800
MX ALT3.ASPMX.L.GOOGLE.com 1800
A 183.111.232.84 1749
A 183.111.232.83 1749
NS ns1.cafe24.com 1800
NS ns2.cafe24.com 1800
NS ns1.cafe24.co.kr 1800
NS ns2.cafe24.co.kr 1800

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 March 9, 2020 and will expire on March 9, 2026 if not renewed. This website is now assigned through the registrar Gabia, Inc.. The WHOIS data for this website's domain was last updated on February 7, 2025.
Domain Created:
2020-03-09
Domain Expires:
2026-03-09
Domain Updated:
2025-02-07
Domain Age:
5 years 3 months 12 days
Domain Registrar:
Gabia, Inc.
WhoIs:
 

   Domain Name: COOKIERUNSTORE.COM
   Registry Domain ID: 2501424559_DOMAIN_COM-VRSN
   Registrar WHOIS Server: whois.gabia.com
   Registrar URL: http://www.gabia.com
   Updated Date: 2025-02-07T05:23:02Z
   Creation Date: 2020-03-09T05:50:05Z
   Registry Expiry Date: 2026-03-09T05:50:05Z
   Registrar: Gabia, Inc.
   Registrar IANA ID: 244
   Registrar Abuse Contact Email: email
   Registrar Abuse Contact Phone: +82.28293543
   Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
   Name Server: DNS1.CAFE24.CO.KR
   Name Server: DNS1.CAFE24.COM
   Name Server: DNS2.CAFE24.CO.KR
   Name Server: DNS2.CAFE24.COM
   DNSSEC: unsigned
   URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2025-03-17T00:21:17Z