tokimeki.blue Tokimeki.blue

   
TOKIMEKI - Bluesky client project

Domain Summary

What is the traffic rank for Tokimeki.blue?

• Tokimeki.blue ranks #206,716 globally on HypeStat.

What percent of global Internet users visit Tokimeki.blue?

• 0.0001591% of global Internet users visit Tokimeki.blue

How many people visit Tokimeki.blue each day?

• Tokimeki.blue receives approximately 7.8K visitors and 38,049 page impressions per day.

Which countries does Tokimeki.blue receive most of its visitors from?

• Tokimeki.blue is mostly visited by people located in Japan,Czech Republic,United States.

How much Tokimeki.blue can earn?

• Tokimeki.blue should earn about $28.85/day from advertising revenue.

What is Tokimeki.blue estimated value?

• Estimated value of Tokimeki.blue is $28,015.69.

What IP addresses does Tokimeki.blue resolve to?

• Tokimeki.blue resolves to the IP addresses 76.76.21.21.

Where are Tokimeki.blue servers located in?

• Tokimeki.blue has servers located in Walnut, California, 91789, United States.

tokimeki.blue Profile

Title:TOKIMEKI - Bluesky client project Description:TOKIMEKI is a Bluesky browser client with multi-column and multi-account support.
Category:Arts and Entertainment / Animation and Comics
Edit Site Info

What technologies does tokimeki.blue use?

These are the technologies used at tokimeki.blue. tokimeki.blue has a total of 4 technologies installed in 3 different categories.
Security
HSTS HSTS
Miscellaneous
Open Graph Open Graph
PWA PWA
Web Servers
Vercel Vercel

tokimeki.blue Traffic Analysis

Tokimeki.blue is ranked #206,716 in the world. This website is viewed by an estimated 7.8K visitors daily, generating a total of 38K pageviews. This equates to about 237.6K monthly visitors. Tokimeki.blue traffic has increased by 25.67% compared to last month.
Daily Visitors7.8K
2.93%
Monthly Visits237.6K
25.67%
Pages per Visit4.85
21.99%
Visit duration09:11
14.8%
Bounce Rate30.78%
46.36%
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
7,842
Monthly Visits:
237,613
Pages per Visit:
4.85
Daily Pageviews:
38,049
Avg. visit duration:
09:11
Bounce rate:
30.78%
Global Reach:
0.0001591%
Monthly Visits (SEMrush):
135,918
Monthly Unique Visitors (SEMrush):
24,477
Monthly Visits (SimilarWeb):
232,945
HypeRank:
206,716
SEMrush Rank:
3,242,816
SimilarWeb Rank:
206,716
*All traffic values are estimates only.

Traffic sources

Direct:
98.72%
Referral:
0.82%
Search:
0%
Social:
0.47%
Paid:
0%

Desktop vs Mobile

Desktop:
88.98%
Mobile:
11.02%

Total Visits Last 3 Months

434K
DEC
189.1K
JAN
237.6K
FEB

Visitors by country

Country
Users%
 
Japan 66.66%
 
Czech Republic 16.62%
 
United States 5.76%
 
Spain 4.83%
 
Brazil 3.98%

Which sites are competitors to tokimeki.blue?

Websites similar to tokimeki.blue 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 87 days ago
     
This can take up to 60 seconds. Please wait...

*HypeStat.com is not promoting or affiliated with tokimeki.blue 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:
23

  ▼

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:
  tokimeki.blue
Rank:
(Rank based on keywords, cost and organic traffic)
  3,242,816
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  85
Organic Traffic:
(Number of visitors coming from top 20 search results)
  128
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $7.00
Full SEMrush Report >>

Revenue report ▼

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

How much would tokimeki.blue make?

Daily Revenue:
$28.85
Monthly Revenue:
$865.50
Yearly Revenue:
$10,530.25
*All earnings values are estimates only.

Daily earning by country

 
CountryPageviewsEarning
 
United States 2,192$10.59
 
Japan 25,364$9.13
 
Czech Republic 6,325$2.91
 
Brazil 1,515$2.01
 
Spain 1,837$0.88

Loss of money due to Adblock?

Daily Revenue Loss:
$2.76
Monthly Revenue Loss:
$82.76
Yearly Revenue Loss:
$1,006.90
Daily Pageviews Blocked:
2,228
Monthly Pageviews Blocked:
66,835
Yearly Pageviews Blocked:
813,153

Daily revenue loss by country

 
CountryBlockedLost Money
 
United States 394$1.91
 
Czech Republic 633$0.29
 
Japan 761$0.27
 
Spain 349$0.17
 
Brazil 91$0.12

How much is tokimeki.blue worth?

Website Value:
$28K

Ad Experience Report ▼

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

Mobile summary

Root domain:
tokimeki.blue
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:
tokimeki.blue
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:
tokimeki.blue
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 tokimeki.blue hosted? ▼

Tokimeki.blue 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

How fast does tokimeki.blue load? ▼

The average loading time of tokimeki.blue is 136 ms. The Desktop speed index is 78 and mobile speed index is 57.
Average Load Time:
136 ms

Page Speed (Google PageSpeed Insights) - Desktop

78
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)6ms 80% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 80% 12% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 12% 7% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 7%
Time To First Byte (TTFB)259ms 93% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 93% 4% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 4% 1% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 1%
First Contentful Paint (FCP)1.0s 90% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 90% 5% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 5% 3% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 3%
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)85ms 94% of loads for this page have a fast (<200ms) Interaction To Next Paint (INP) 94% 4% of loads for this page have an average (200ms ~ 500ms) Interaction To Next Paint (INP) 4% 1% of loads for this page have a slow (>500ms) Interaction To Next Paint (INP) 1%
Largest Contentful Paint (LCP)3.2s 60% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 60% 23% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 23% 15% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 15%

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)6ms 79% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 79% 12% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 12% 7% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 7%
Time To First Byte (TTFB)253ms 93% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 93% 4% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 4% 1% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 1%
First Contentful Paint (FCP)1.0s 90% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 90% 5% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 5% 3% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 3%
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)86ms 94% of loads for this page have a fast (<200ms) Interaction To Next Paint (INP) 94% 4% of loads for this page have an average (200ms ~ 500ms) Interaction To Next Paint (INP) 4% 1% of loads for this page have a slow (>500ms) Interaction To Next Paint (INP) 1%
Largest Contentful Paint (LCP)3.2s 61% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 61% 23% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 23% 15% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 15%

Lab Data

Speed Index 1.5 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Max Potential First Input Delay 200 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
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
Total Blocking Time 150 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
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
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
First Meaningful Paint  
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
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
Time to Interactive 2.7 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
Largest Contentful Paint 2.7 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest 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
INP by phase  
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
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
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

Page Speed (Google PageSpeed Insights) - Mobile

57
0-49 50-89 90-100 i

Field Data

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.

Cumulative Layout Shift (CLS)7ms 80% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 84% 8% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 8% 7% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 7%
Time To First Byte (TTFB)464ms 93% of loads for this page have a fast (<800s) Time To First Byte (TTFB) 88% 8% of loads for this page have an average (800s ~ 1800s) Time To First Byte (TTFB) 8% 2% of loads for this page have a slow (>1800s) Time To First Byte (TTFB) 2%
First Contentful Paint (FCP)1.9s 90% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 72% 15% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 15% 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)288ms 94% of loads for this page have a fast (<200s) Interactive To Next Paint (INP) 51% 41% of loads for this page have an average (200s ~ 500s) Interactive To Next Paint (INP) 41% 7% of loads for this page have a slow (>500s) Interactive To Next Paint (INP) 7%
Largest Contentful Paint (LCP)4.3s 60% of loads for this page have a fast (<2500s) Largest Contentful Paint (LCP) 44% 26% of loads for this page have an average (2500s ~ 4000s) Largest Contentful Paint (LCP) 26% 28% of loads for this page have a slow (>4000s) Largest Contentful Paint (LCP) 28%

Origin Data

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.

Cumulative Layout Shift (CLS)7ms 82% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 82% 9% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 9% 7% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 7%
Time To First Byte (TTFB)460ms 89% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 89% 8% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 8% 2% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 2%
First Contentful Paint (FCP)1.9s 71% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 71% 16% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 16% 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)288ms 51% of loads for this page have a fast (<0.2s) Interactive To Next Paint (INP) 51% 40% of loads for this page have an average (0.2s ~ 0.5s) Interactive To Next Paint (INP) 40% 8% of loads for this page have a slow (>0.5s) Interactive To Next Paint (INP) 8%
Largest Contentful Paint (LCP)4.3s 44% of loads for this page have a fast (<2.5s)Largest Contentful Paint (LCP) 44% 26% of loads for this page have an average (2.5s ~ 4s)Largest Contentful Paint (LCP) 26% 28% of loads for this page have a slow (>4s)Largest Contentful Paint (LCP) 28%

Lab Data

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
Largest Contentful Paint 15.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
Max Potential First Input Delay 200 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 by phase  
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
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
Speed Index 6.4 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
First Contentful Paint 6.4 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
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
Time to Interactive 15.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
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
Total Blocking Time 160 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
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
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
First Meaningful Paint  
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric

Does tokimeki.blue 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 tokimeki.blue are reduced by 63%.
tokimeki.blue use br compression.
Original size: 2.28 KB
Compressed size: 854 B
File reduced by: 1.45 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.
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. tokimeki.blue supports HTTPS.
 tokimeki.blue supports HTTPS
     
Verifying SSL Support. Please wait...
Common Name: tokimeki.blue
Organization:
Location:
Issuer: R11
Valid from: Jan 30 18:04:24 2025 GMT
Valid until: Apr 30 18:04:23 2025 GMT
Authority: CA:FALSE
Keysize: 2048 Bits
Common Name: R11
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.
 tokimeki.blue 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. 
age: 0
cache-control: public, max-age=0, must-revalidate
content-encoding: br
content-type: text/html
date: Wed, 19 Mar 2025 02:26:42 GMT
etag: W/"1k3ymui"
link: <./_app/immutable/entry/start.Dp4Y0PoU.js>; rel="modulepreload"; nopush, <./_app/immutable/chunks/Bm-4_2z5.js>; rel="modulepreload"; nopush, <./_app/immutable/chunks/BlqrjN2I.js>; rel="modulepreload"; nopush, <./_app/immutable/chunks/DDsuJTt6.js>; rel="modulepreload"; nopush, <./_app/immutable/chunks/BJdZ9E1B.js>; rel="modulepreload"; nopush, <./_app/immutable/entry/app.ACjt1MWW.js>; rel="modulepreload"; nopush, <./_app/immutable/chunks/BDyN-mGn.js>; rel="modulepreload"; nopush, <./_app/immutable/chunks/BlQtdjyz.js>; rel="modulepreload"; nopush, <./_app/immutable/chunks/C0jyNEL3.js>; rel="modulepreload"; nopush, <./_app/immutable/chunks/Mt2fxJ4S.js>; rel="modulepreload"; nopush, <./_app/immutable/chunks/CtnQwDsH.js>; rel="modulepreload"; nopush, <./_app/immutable/chunks/CKdvTso-.js>; rel="modulepreload"; nopush, <./_app/immutable/chunks/CWj6FrbW.js>; rel="modulepreload"; nopush, <./_app/immutable/chunks/COnqW9_w.js>; rel="modulepreload"; nopush, <./_app/immutable/chunks/Dfr2CcaC.js>; rel="modulepreload"; nopush, <./_app/immutable/chunks/BOJgcnHT.js>; rel="modulepreload"; nopush, <./_app/immutable/chunks/BYiNhCRa.js>; rel="modulepreload"; nopush, <./_app/immutable/chunks/BcLvq4fh.js>; rel="modulepreload"; nopush
server: Vercel
strict-transport-security: max-age=63072000
x-sveltekit-page: true
x-vercel-cache: MISS
x-vercel-id: cle1::sfo1::vlhwx-1742351202206-b16f8efe5d55

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 3600
Mname dns01.muumuu-domain.com
Rname postmaster.tokimeki.blue
Serial Number 1710335416
Refresh 3600
Retry 1800
Expire 604800
Minimum TTL 3600
TXT google-site-verification=Hf5Hg60rPdA_lF_G7ODhM1G1F1ywZenZXnQq63kAp28 3600
A 76.76.21.21 3546
NS dns01.muumuu-domain.com 3546
NS dns02.muumuu-domain.com 3546

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 April 13, 2023 and will expire on April 13, 2026 if not renewed. This website is now assigned through the registrar GMO Internet, Inc.. The WHOIS data for this website's domain was last updated on March 15, 2025.
Domain Created:
2023-04-13
Domain Expires:
2026-04-13
Domain Updated:
2025-03-15
Domain Age:
2 years 2 months 1 days
Domain Registrar:
GMO Internet, Inc.
Domain Owner:
Whois Privacy Protection Service by MuuMuuDomain
WhoIs:
 

Domain Name: tokimeki.blue
Registry Domain ID: 3e3aa5ce6fbb4f8aa317d5e91b95382d-DONUTS
Registrar WHOIS Server: whois.discount-domain.com
Registrar URL: http://www.onamae.com
Updated Date: 2025-03-15T08:09:41Z
Creation Date: 2023-04-13T11:44:08Z
Registrar Registration Expiration Date: 2026-04-13T11:44:08Z
Registrar: GMO Internet, Inc.
Registrar IANA ID: 49
Registrar Abuse Contact Email: email
Registrar Abuse Contact Phone: +81.337709199
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID: 1a713993f57bf6
Registrant Name: Whois Privacy Protection Service by MuuMuuDomain
Registrant Organization: Whois Privacy Protection Service by MuuMuuDomain
Registrant Street: 2-7-21 Tenjin Chuo-ku
Registrant Street: Tenjin Prime 8F
Registrant City: Fukuoka-shi
Registrant State/Province: Fukuoka
Registrant Postal Code: 810-0001
Registrant Country: JP
Registrant Phone: +81.927137999
Registrant Phone Ext:
Registrant Fax: +81.927137944
Registrant Fax Ext:
Registrant Email: email
Registry Admin ID: 1a72429379d2d8
Admin Name: Whois Privacy Protection Service by MuuMuuDomain
Admin Organization: Whois Privacy Protection Service by MuuMuuDomain
Admin Street: 2-7-21 Tenjin Chuo-ku
Admin Street: Tenjin Prime 8F
Admin City: Fukuoka-shi
Admin State/Province: Fukuoka
Admin Postal Code: 810-0001
Admin Country: JP
Admin Phone: +81.927137999
Admin Phone Ext:
Admin Fax: +81.927137944
Admin Fax Ext:
Admin Email: email
Registry Tech ID: 1a83f37da62fc6
Tech Name: Whois Privacy Protection Service by MuuMuuDomain
Tech Organization: Whois Privacy Protection Service by MuuMuuDomain
Tech Street: 2-7-21 Tenjin Chuo-ku
Tech Street: Tenjin Prime 8F
Tech City: Fukuoka-shi
Tech State/Province: Fukuoka
Tech Postal Code: 810-0001
Tech Country: JP
Tech Phone: +81.927137999
Tech Phone Ext:
Tech Fax: +81.927137944
Tech Fax Ext:
Tech Email: email
Name Server: dns01.muumuu-domain.com
Name Server: dns02.muumuu-domain.com
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2025-03-15T08:09:41Z