ticketdive.com Ticketdive.com

   
トップ | TicketDive

Domain Summary

What is the traffic rank for Ticketdive.com?

• Ticketdive.com ranks #144,763 globally on HypeStat.

What percent of global Internet users visit Ticketdive.com?

• 0.0002717% of global Internet users visit Ticketdive.com

How many people visit Ticketdive.com each day?

• Ticketdive.com receives approximately 13.4K visitors and 28,790 page impressions per day.

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

• Ticketdive.com is mostly visited by people located in Japan,Taiwan,Hong Kong.

How much Ticketdive.com can earn?

• Ticketdive.com should earn about $10.87/day from advertising revenue.

What is Ticketdive.com estimated value?

• Estimated value of Ticketdive.com is $10,140.30.

What IP addresses does Ticketdive.com resolve to?

• Ticketdive.com resolves to the IP addresses 199.36.158.100.

Where are Ticketdive.com servers located in?

• Ticketdive.com has servers located in United States.

ticketdive.com Profile

Title:トップ | TicketDive Description:TicketDiveは、ライブイベントに特化したチケットサービスです。アイドルのライブチケットを申込・購入・販売することができます。
Category:Arts and Entertainment / Other Arts and Entertainment
Edit Site Info

What technologies does ticketdive.com use?

These are the technologies used at ticketdive.com. ticketdive.com has a total of 9 technologies installed in 9 different categories.
Databases
Firebase Firebase
Security
HSTS HSTS
Miscellaneous
HTTP/3 HTTP/3
Open Graph Open Graph
PWA PWA
JavaScript Frameworks
Nuxt.js Nuxt.js
Vue.js Vue.js
Web Frameworks
Nuxt.js Nuxt.js
Web Servers
Nuxt.js Nuxt.js
Static Site Generator
Nuxt.js Nuxt.js
JavaScript Libraries
Swiper Swiper
Programming Languages
Node.js Node.js

ticketdive.com Traffic Analysis

Ticketdive.com is ranked #144,763 in the world. This website is viewed by an estimated 13.4K visitors daily, generating a total of 28.8K pageviews. This equates to about 405.8K monthly visitors. Ticketdive.com traffic has increased by 3.55% compared to last month.
Daily Visitors13.4K
0.72%
Monthly Visits405.8K
3.55%
Pages per Visit2.15
21.85%
Visit duration03:10
17.55%
Bounce Rate64.95%
5.83%
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
13,393
Monthly Visits:
405,808
Pages per Visit:
2.15
Daily Pageviews:
28,790
Avg. visit duration:
03:10
Bounce rate:
64.95%
Global Reach:
0.0002717%
Monthly Visits (SEMrush):
351,454
Monthly Unique Visitors (SEMrush):
82,793
Monthly Visits (SimilarWeb):
397,822
HypeRank:
144,763
SEMrush Rank:
2,564,300
SimilarWeb Rank:
144,763
*All traffic values are estimates only.

Traffic sources

Direct:
46.68%
Referral:
17.17%
Search:
9.69%
Social:
26.47%
Paid:
0%

Desktop vs Mobile

Desktop:
10.50%
Mobile:
89.50%

Total Visits Last 3 Months

528.3K
DEC
391.9K
JAN
405.8K
FEB

Visitors by country

Country
Users%
 
Japan 96.15%
 
Taiwan 1.54%
 
Hong Kong 1.20%
 
Korea, Republic of 0.49%
 
Indonesia 0.34%

Which sites are competitors to ticketdive.com?

Websites similar to ticketdive.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.
Domain
CompareDaily Visitors
oricon.co.jp
Compare >2.1M
natalie.mu
Compare >1M
only-five.jp
Compare >5.2K
Last update was 90 days ago
     
This can take up to 60 seconds. Please wait...

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

  ▼

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:
  ticketdive.com
Rank:
(Rank based on keywords, cost and organic traffic)
  2,564,300
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  60
Organic Traffic:
(Number of visitors coming from top 20 search results)
  213
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $0.00
Full SEMrush Report >>

Revenue report ▼

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

How much would ticketdive.com make?

Daily Revenue:
$10.87
Monthly Revenue:
$326.10
Yearly Revenue:
$3,967.55
*All earnings values are estimates only.

Daily earning by country

 
CountryPageviewsEarning
 
Japan 27,683$9.97
 
Hong Kong 347$0.38
 
Taiwan 442$0.10
 
Korea, Republic of 141$0.08
 
Indonesia 98$0.01

Loss of money due to Adblock?

Daily Revenue Loss:
$0.36
Monthly Revenue Loss:
$10.89
Yearly Revenue Loss:
$132.50
Daily Pageviews Blocked:
998
Monthly Pageviews Blocked:
29,952
Yearly Pageviews Blocked:
364,417

Daily revenue loss by country

 
CountryBlockedLost Money
 
Japan 830$0.30
 
Hong Kong 35$0.04
 
Taiwan 71$0.02
 
Indonesia 57$0.01
 
Korea, Republic of 6$0.00

How much is ticketdive.com worth?

Website Value:
$10.1K

Ad Experience Report ▼

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

Mobile summary

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

Ticketdive.com may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.
Server IP:
199.36.158.100
ASN:
AS54113 
ISP:
Fastly 
Server Location:

United States, US
 

Other sites hosted on 199.36.158.100

How fast does ticketdive.com load? ▼

The average loading time of ticketdive.com is 309 ms. The Desktop speed index is 85 and mobile speed index is 72.
Average Load Time:
309 ms

Page Speed (Google PageSpeed Insights) - Desktop

85
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a FAST speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Cumulative Layout Shift (CLS)3ms 78% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 78% 3% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 3% 17% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 17%
Time To First Byte (TTFB)502ms 88% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 88% 7% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 7% 3% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 3%
First Contentful Paint (FCP)942ms 93% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 93% 4% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 4% 2% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 2%
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)63ms 95% of loads for this page have a fast (<200ms) Interaction To Next Paint (INP) 95% 2% of loads for this page have an average (200ms ~ 500ms) Interaction To Next Paint (INP) 2% 1% of loads for this page have a slow (>500ms) Interaction To Next Paint (INP) 1%
Largest Contentful Paint (LCP)1.4s 92% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 92% 5% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 5% 1% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 1%

Origin Data

All pages served from this origin have an FAST speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Cumulative Layout Shift (CLS)1ms 91% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 91% 2% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 2% 5% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 5%
Time To First Byte (TTFB)559ms 87% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 87% 9% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 9% 2% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 2%
First Contentful Paint (FCP)832ms 95% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 95% 2% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 2% 2% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 2%
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)39ms 97% of loads for this page have a fast (<200ms) Interaction To Next Paint (INP) 97% 1% of loads for this page have an average (200ms ~ 500ms) Interaction To Next Paint (INP) 1% 1% of loads for this page have a slow (>500ms) Interaction To Next Paint (INP) 1%
Largest Contentful Paint (LCP)1.1s 94% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 94% 3% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 3% 2% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 2%

Lab Data

First Meaningful Paint  
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint 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
Largest Contentful Paint 2.4 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Render blocking requests  
Requests are blocking the page's initial render, which may delay LCP. can move these network requests out of the critical path. Deferring or inlining
INP by phase  
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
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
Total Blocking Time 100 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
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
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
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
Max Potential First Input Delay 150 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
Speed Index 1.2 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index 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
Time to Interactive 2.4 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

Page Speed (Google PageSpeed Insights) - Mobile

72
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a FAST speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Cumulative Layout Shift (CLS)1ms 78% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 79% 3% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 3% 17% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 17%
Time To First Byte (TTFB)525ms 88% of loads for this page have a fast (<800s) Time To First Byte (TTFB) 89% 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.1s 93% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 92% 5% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 5% 1% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 1%
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)100ms 95% of loads for this page have a fast (<200s) Interactive To Next Paint (INP) 93% 5% of loads for this page have an average (200s ~ 500s) Interactive To Next Paint (INP) 5% 1% of loads for this page have a slow (>500s) Interactive To Next Paint (INP) 1%
Largest Contentful Paint (LCP)1.6s 92% of loads for this page have a fast (<2500s) Largest Contentful Paint (LCP) 90% 6% of loads for this page have an average (2500s ~ 4000s) Largest Contentful Paint (LCP) 6% 2% of loads for this page have a slow (>4000s) Largest Contentful Paint (LCP) 2%

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)5ms 76% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 76% 5% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 5% 17% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 17%
Time To First Byte (TTFB)822ms 73% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 73% 21% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 21% 4% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 4%
First Contentful Paint (FCP)1.2s 90% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 90% 6% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 6% 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%
Interactive To Next Paint (INP)116ms 91% of loads for this page have a fast (<0.2s) Interactive To Next Paint (INP) 91% 7% of loads for this page have an average (0.2s ~ 0.5s) Interactive To Next Paint (INP) 7% 1% of loads for this page have a slow (>0.5s) Interactive To Next Paint (INP) 1%
Largest Contentful Paint (LCP)1.9s 83% of loads for this page have a fast (<2.5s)Largest Contentful Paint (LCP) 83% 9% of loads for this page have an average (2.5s ~ 4s)Largest Contentful Paint (LCP) 9% 6% of loads for this page have a slow (>4s)Largest Contentful Paint (LCP) 6%

Lab Data

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
Largest Contentful Paint 10.4 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
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
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 10.4 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
Speed Index 3.7 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index 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
Total Blocking Time 130 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
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
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
Max Potential First Input Delay 180 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 Meaningful Paint  
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
Render blocking requests  
Requests are blocking the page's initial render, which may delay LCP. can move these network requests out of the critical path. Deferring or inlining
First Contentful Paint 0.9 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric

Does ticketdive.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 ticketdive.com are reduced by 81%.
ticketdive.com use gzip compression.
Original size: 87.09 KB
Compressed size: 15.81 KB
File reduced by: 71.27 KB (81%)

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. ticketdive.com supports HTTPS.
 ticketdive.com supports HTTPS
     
Verifying SSL Support. Please wait...
Common Name: ticketdive.com
Organization:
Location:
Issuer: WR3
Valid from: Feb 16 14:20:02 2025 GMT
Valid until: May 17 15:19:23 2025 GMT
Authority: CA:FALSE
Keysize: 2048 Bits
Common Name: WR3
Organization: Google Trust Services
Location: US
Issuer: GTS Root R1
Valid from: Dec 13 09:00:00 2023 GMT
Valid until: Feb 20 14:00:00 2029 GMT
Authority: CA:TRUE
Keysize: 2048 Bits
Common Name: GTS Root R1
Organization: Google Trust Services LLC
Location: US
Issuer: GlobalSign Root CA
Valid from: Jun 19 00:00:42 2020 GMT
Valid until: Jan 28 00:00:42 2028 GMT
Authority: CA:TRUE
Keysize: 4096 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.
 ticketdive.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. 
accept-ranges: none
cache-control: private
content-encoding: gzip
content-type: text/html; charset=utf-8
etag: "15c58-x5VtiD2+76K3nLij+QO/oXsCFGY"
server: Google Frontend
strict-transport-security: max-age=31556926
x-country-code: US
date: Sun, 16 Mar 2025 22:35:42 GMT
x-served-by: cache-chi-kigq8000153-CHI
x-cache: MISS
x-cache-hits: 0
x-timer: S1742164543.618834,VS0,VE287
vary: Accept-Encoding,cookie,need-authorization, x-fh-requested-host, accept-encoding
alt-svc: h3=":443";ma=86400,h3-29=":443";ma=86400,h3-27=":443";ma=86400

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 stripe-verification=030ffb0a1ffb6c5a2ddb4adb275d0a25fb037001557739ab7835e3452083ee30 86400
TXT firebase=playyte-ticket-prod 86400
TXT v=spf1 include:_spf.firebasemail.com ~all 86400
TXT google-site-verification=C-sxGmBhGfFH9dPIng2c9v5222QgqquPE_hHO07xsmU 86400
TXT stripe-verification=3712095b977d9cf55f598f6c2c9ef905f146079e95ea836767f2673fb8ac0fa8 86400
MX alt3.aspmx.l.google.com 3600
MX alt4.aspmx.l.google.com 3600
MX alt2.aspmx.l.google.com 3600
MX alt1.aspmx.l.google.com 3600
MX aspmx.l.google.com 3600
SOA 86400
Mname 01.dnsv.jp
Rname hostmaster.dnsv.jp
Serial Number 1712459056
Refresh 3600
Retry 900
Expire 604800
Minimum TTL 300
A 199.36.158.100 86338
NS 04.dnsv.jp 86400
NS 01.dnsv.jp 86400
NS 02.dnsv.jp 86400
NS 03.dnsv.jp 86400

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 December 15, 2022 and will expire on December 15, 2025 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 November 30, 2024.
Domain Created:
2022-12-15
Domain Expires:
2025-12-15
Domain Updated:
2024-11-30
Domain Age:
2 years 6 months
Domain Registrar:
GMO Internet, Inc.
Domain Owner:
Whois Privacy Protection Service by onamae.com
WhoIs:
 

Domain Name: ticketdive.com
Registry Domain ID: 2744914126_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.discount-domain.com
Registrar URL: http://www.onamae.com
Updated Date: 2024-11-30T01:02:31Z
Creation Date: 2022-12-15T16:58:52Z
Registrar Registration Expiration Date: 2025-12-15T16:58:52Z
Registrar: GMO Internet, Inc.
Registrar IANA ID: 49
Registrar Abuse Contact Email: email
Registrar Abuse Contact Phone: +81.337709199
Domain Status: ok https://icann.org/epp#ok
Registry Registrant ID: Not Available From Registry
Registrant Name: Whois Privacy Protection Service by onamae.com
Registrant Organization: Whois Privacy Protection Service by onamae.com
Registrant Street: 26-1 Sakuragaoka-cho
Registrant Street: Cerulean Tower 11F
Registrant City: Shibuya-ku
Registrant State/Province: Tokyo
Registrant Postal Code: 150-8512
Registrant Country: JP
Registrant Phone: +81.354562560
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: email
Registry Admin ID: Not Available From Registry
Admin Name: Whois Privacy Protection Service by onamae.com
Admin Organization: Whois Privacy Protection Service by onamae.com
Admin Street: 26-1 Sakuragaoka-cho
Admin Street: Cerulean Tower 11F
Admin City: Shibuya-ku
Admin State/Province: Tokyo
Admin Postal Code: 150-8512
Admin Country: JP
Admin Phone: +81.354562560
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: email
Registry Tech ID: Not Available From Registry
Tech Name: Whois Privacy Protection Service by onamae.com
Tech Organization: Whois Privacy Protection Service by onamae.com
Tech Street: 26-1 Sakuragaoka-cho
Tech Street: Cerulean Tower 11F
Tech City: Shibuya-ku
Tech State/Province: Tokyo
Tech Postal Code: 150-8512
Tech Country: JP
Tech Phone: +81.354562560
Tech Phone Ext:
Tech Fax:
Tech Fax Ext:
Tech Email: email
Name Server: 01.dnsv.jp
Name Server: 02.dnsv.jp
Name Server: 03.dnsv.jp
Name Server: 04.dnsv.jp
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2024-11-30T01:02:31Z