tinder.com Tinder.com

   
Tinder | Dating, Make Friends & Meet New People

Domain Summary

What is the traffic rank for Tinder.com?

• Tinder.com ranks #537 globally on HypeStat.

What percent of global Internet users visit Tinder.com?

• 0.0320945% of global Internet users visit Tinder.com

How many people visit Tinder.com each day?

• Tinder.com receives approximately 1.6M visitors and 12,931,607 page impressions per day.

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

• Tinder.com is mostly visited by people located in Brazil,United States,Spain.

How much Tinder.com can earn?

• Tinder.com should earn about $42,037.04/day from advertising revenue.

What is Tinder.com estimated value?

• Estimated value of Tinder.com is $50,902,779.86.

What IP addresses does Tinder.com resolve to?

• Tinder.com resolves to the IP addresses 52.84.150.60.

Where are Tinder.com servers located in?

• Tinder.com has servers located in Seattle, Washington, 98109, United States.

tinder.com Profile

Title:Tinder | Dating, Make Friends & Meet New People
Description:With 55 billion matches to date, Tinder® is the world’s most popular dating app, making it the place to meet new people.
Tags:
best
beta
subscribe
tinder
sign
read
start
cancel
discover
reading
news
Category:Community and Society / Dating and Relationships
About: Tinder is how people meet. It's like real life, but better. Get it for free on iPhone and Android Edit Site Info

What technologies does tinder.com use?

These are the technologies used at tinder.com. tinder.com has a total of 11 technologies installed in 10 different categories.
Load balancers
Amazon ALB Amazon ALB
CDN
Amazon Cloudfront Amazon Cloudfront
Miscellaneous
Amazon S3 Amazon S3
Open Graph Open Graph
PWA PWA
Web Frameworks
Express Express
Web Servers
Express Express
Nginx Nginx
Security
HSTS HSTS
Reverse proxies
Nginx Nginx
JavaScript Frameworks
React React
PaaS
Amazon Web Services Amazon Web Services
Programming Languages
Node.js Node.js

tinder.com Traffic Analysis

ținder.com is ranked #537 in the world. This website is viewed by an estimated 1.6M visitors daily, generating a total of 12.9M pageviews. This equates to about 47.9M monthly visitors. ținder.com traffic has decreased by 9.16% compared to last month.
Daily Visitors1.6M
0.73%
Monthly Visits47.9M
9.16%
Pages per Visit8.17
15.49%
Visit duration08:25
3.82%
Bounce Rate21.51%
8.24%
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
1,582,235
Monthly Visits:
47,941,721
Pages per Visit:
8.17
Daily Pageviews:
12,931,607
Avg. visit duration:
08:25
Bounce rate:
21.51%
Global Reach:
0.0320945%
Monthly Visits (SEMrush):
66,378,644
Monthly Unique Visitors (SEMrush):
13,494,515
Monthly Visits (SimilarWeb):
46,997,093
HypeRank:
537
SEMrush Rank:
1,909
SimilarWeb Rank:
822
*All traffic values are estimates only.

Traffic sources

Direct:
84.51%
Referral:
1.79%
Search:
12.08%
Social:
1.57%
Paid:
0.05%

Desktop vs Mobile

Desktop:
40.28%
Mobile:
59.72%

Total Visits Last 3 Months

54.9M
DEC
52.8M
JAN
47.9M
FEB

Visitors by country

Country
Users%
 
Brazil 15.00%
 
United States 10.35%
 
Spain 5.20%
 
Germany 4.95%
 
Argentina 4.56%

Where do visitors go on tinder.com?

 
Reach%Pageviews%PerUser
tinder.com
94.45%95.28%3.64
help.tinder.com
5.95%3.09%1.9
policies.tinder.com
2.76%0.87%1.1
go.tinder.com
0.67%0.53%2.9
lite.tinder.com
0.53%0.17%1.2

Which sites are competitors to tinder.com?

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

*HypeStat.com is not promoting or affiliated with tinder.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:
1,280,000
Bing Index:
52,000
Baidu Index:
4,580

  ▼

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:
  tinder.com
Rank:
(Rank based on keywords, cost and organic traffic)
  1,909
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  104,668
Organic Traffic:
(Number of visitors coming from top 20 search results)
  1,517,200
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $2,232,372.00
Full SEMrush Report >>

Revenue report ▼

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

How much would tinder.com make?

Daily Revenue:
$42,037.04
Monthly Revenue:
$1,261,111.20
Yearly Revenue:
$15,343,519.60
*All earnings values are estimates only.

Daily earning by country

 
CountryPageviewsEarning
 
United States 1,338,436$6,464.65
 
Brazil 1,939,719$2,579.83
 
Germany 640,241$896.34
 
Spain 672,036$322.58
 
Argentina 589,644$147.41

Loss of money due to Adblock?

Daily Revenue Loss:
$1,660.29
Monthly Revenue Loss:
$49,808.73
Yearly Revenue Loss:
$606,006.16
Daily Pageviews Blocked:
753,209
Monthly Pageviews Blocked:
22,596,258
Yearly Pageviews Blocked:
274,921,137

Daily revenue loss by country

 
CountryBlockedLost Money
 
United States 240,918$1,163.64
 
Germany 185,670$259.94
 
Brazil 116,383$154.79
 
Spain 127,687$61.29
 
Argentina 82,550$20.64

How much is tinder.com worth?

Website Value:
$50.9M

Ad Experience Report ▼

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

Mobile summary

Root domain:
tinder.com
Last Change Time:
(The last time that the site changed status.)
2019-08-09 01:56:51
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:
tinder.com
Last Change Time:
(The last time that the site changed status.)
2019-06-24 06:11:25
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:
tinder.com
Last Change Time:
(The last time that the site changed status.)
2019-08-09 01:56:51
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 tinder.com hosted? ▼

Tinder.com may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.
Server IP:
52.84.150.60
ASN:
AS16509 
ISP:
Amazon.com, Inc. 
Server Location:
Seattle
Washington, WA
98109
United States, US
 

Other sites hosted on 52.84.150.60

There are no other sites hosted on this IP

How fast does tinder.com load? ▼

The average loading time of tinder.com is 105 ms. The Desktop speed index is 64 and mobile speed index is 47.
Average Load Time:
105 ms

Page Speed (Google PageSpeed Insights) - Desktop

64
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)2ms 95% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 95% 2% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 2% 1% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 1%
Time To First Byte (TTFB)594ms 82% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 82% 12% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 12% 5% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 5%
First Contentful Paint (FCP)690ms 93% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 93% 3% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 3% 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)126ms 88% of loads for this page have a fast (<200ms) Interaction To Next Paint (INP) 88% 8% of loads for this page have an average (200ms ~ 500ms) Interaction To Next Paint (INP) 8% 2% of loads for this page have a slow (>500ms) Interaction To Next Paint (INP) 2%
Largest Contentful Paint (LCP)4.6s 39% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 39% 27% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 27% 32% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 32%

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)2ms 94% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 94% 3% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 3% 2% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 2%
Time To First Byte (TTFB)579ms 83% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 83% 11% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 11% 5% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 5%
First Contentful Paint (FCP)754ms 93% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 93% 3% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 3% 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)127ms 87% of loads for this page have a fast (<200ms) Interaction To Next Paint (INP) 87% 9% of loads for this page have an average (200ms ~ 500ms) Interaction To Next Paint (INP) 9% 2% of loads for this page have a slow (>500ms) Interaction To Next Paint (INP) 2%
Largest Contentful Paint (LCP)4.6s 42% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 42% 26% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 26% 31% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 31%

Lab Data

LCP request discovery  
Optimize LCP by making the LCP image from the HTML immediately, and discoverable avoiding lazy-loading
Preload Largest Contentful Paint image  
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements
Largest Contentful Paint 2.0 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 390 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
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
Speed Index 1.9 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
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
Time to Interactive 2.0 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
First Meaningful Paint  
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful 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
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
First Contentful Paint 0.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
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
Total Blocking Time 550 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
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 about optimal lazy loading

Page Speed (Google PageSpeed Insights) - Mobile

47
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)3ms 95% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 82% 11% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 11% 6% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 6%
Time To First Byte (TTFB)932ms 82% of loads for this page have a fast (<800s) Time To First Byte (TTFB) 70% 21% of loads for this page have an average (800s ~ 1800s) Time To First Byte (TTFB) 21% 8% of loads for this page have a slow (>1800s) Time To First Byte (TTFB) 8%
First Contentful Paint (FCP)1.6s 93% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 81% 11% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 11% 6% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 6%
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)270ms 88% of loads for this page have a fast (<200s) Interactive To Next Paint (INP) 62% 27% of loads for this page have an average (200s ~ 500s) Interactive To Next Paint (INP) 27% 10% of loads for this page have a slow (>500s) Interactive To Next Paint (INP) 10%
Largest Contentful Paint (LCP)7.8s 39% of loads for this page have a fast (<2500s) Largest Contentful Paint (LCP) 23% 19% of loads for this page have an average (2500s ~ 4000s) Largest Contentful Paint (LCP) 19% 57% of loads for this page have a slow (>4000s) Largest Contentful Paint (LCP) 57%

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)8ms 76% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 76% 8% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 8% 15% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 15%
Time To First Byte (TTFB)872ms 71% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 71% 20% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 20% 7% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 7%
First Contentful Paint (FCP)1.6s 80% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 80% 12% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 12% 6% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 6%
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)284ms 59% of loads for this page have a fast (<0.2s) Interactive To Next Paint (INP) 59% 30% of loads for this page have an average (0.2s ~ 0.5s) Interactive To Next Paint (INP) 30% 10% of loads for this page have a slow (>0.5s) Interactive To Next Paint (INP) 10%
Largest Contentful Paint (LCP)8.3s 21% of loads for this page have a fast (<2.5s)Largest Contentful Paint (LCP) 21% 17% of loads for this page have an average (2.5s ~ 4s)Largest Contentful Paint (LCP) 17% 60% of loads for this page have a slow (>4s)Largest Contentful Paint (LCP) 60%

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
First Meaningful Paint  
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
Largest Contentful Paint 8.9 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Time to Interactive 9.0 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 5.5 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
First Contentful Paint 5.5 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful 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
Max Potential First Input Delay 390 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
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
Total Blocking Time 390 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
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

Does tinder.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 tinder.com are reduced by 79%.
tinder.com use gzip compression.
Original size: 445.6 KB
Compressed size: 90.59 KB
File reduced by: 355.01 KB (79%)

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. tinder.com has 63 Safety Reputations.
Status:
  SAFE
Safety Reputations:
  63
Safety Confidence:
  8

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. tinder.com supports HTTPS.
 tinder.com supports HTTPS
     
Verifying SSL Support. Please wait...
Common Name: tinder.com
Organization:
Location:
Issuer: Amazon RSA 2048 M02
Valid from: Feb 15 00:00:00 2025 GMT
Valid until: Mar 17 23:59:59 2026 GMT
Authority: CA:FALSE
Keysize: 2048 Bits
Common Name: Amazon RSA 2048 M02
Organization: Amazon
Location: US
Issuer: Amazon Root CA 1
Valid from: Aug 23 22:25:30 2022 GMT
Valid until: Aug 23 22:25:30 2030 GMT
Authority: CA:TRUE
Keysize: 2048 Bits
Common Name: Amazon Root CA 1
Organization: Amazon
Location: US
Issuer: Starfield Services Root Certificate Authority - G2
Valid from: May 25 12:00:00 2015 GMT
Valid until: Dec 31 01:00:00 2037 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.
 tinder.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. 
content-type: text/html; charset=utf-8
date: Sat, 15 Mar 2025 20:22:39 GMT
set-cookie: AWSALB=ZO8MoyA9OZ3o1/rwrIe5S7/RYgqD4Ry1Q5HxA4//0Zrn/ZNTT2qb3aNiLfKsPCciK/T5rZ7/IuGrLbqqnmUoA673sUqyHQSLlFDeyUvFtCtPgOdA9gZHN96QYLEU; Expires=Sat, 22 Mar 2025 20:22:39 GMT; Path=/
set-cookie: AWSALBCORS=ZO8MoyA9OZ3o1/rwrIe5S7/RYgqD4Ry1Q5HxA4//0Zrn/ZNTT2qb3aNiLfKsPCciK/T5rZ7/IuGrLbqqnmUoA673sUqyHQSLlFDeyUvFtCtPgOdA9gZHN96QYLEU; Expires=Sat, 22 Mar 2025 20:22:39 GMT; Path=/; SameSite=None; Secure
server: nginx
x-powered-by: Express
x-dns-prefetch-control: on
referrer-policy: origin-when-cross-origin
content-security-policy-report-only: default-src 'self';base-uri 'self';connect-src 'self' wss://keepalive.gotinder.com wss://keepalive.ue1.d1.tstaging.com https://messagepublish.ue1.d4.tstaging.com https://*.gotinder.com https://*.appsflyer.com https://*.bugsnag.com https://tinder-api.arkoselabs.com https://*.spotify.com https://*.line.me https://*.onelink.me https://*.*.braintree-api.com https://*.*.paypal.com https://*.braintree-api.com https://*.paypal.com https://*.braintreegateway.com https://*.s3.amazonaws.com https://*.google-analytics.com https://*.analytics.google.com https://*.googletagmanager.com https://*.g.doubleclick.net https://*.doubleclick.net https://*.google.com https://maps.googleapis.com https://*.gstatic.com https://fonts.googleapis.com;script-src 'nonce-s+1VnWNyDdemOZaMiQhGyg==' 'strict-dynamic' 'unsafe-eval' 'unsafe-hashes' 'sha256-PLCxbpHSwAa8+W198R1KQQ9UDCexTvYy4z4YmCg21NM=' 'unsafe-inline' https:;style-src 'self' 'unsafe-inline' blob: https://*.google-analytics.com https://*.analytics.google.com https://*.googletagmanager.com https://*.g.doubleclick.net https://*.doubleclick.net https://*.google.com https://maps.googleapis.com https://*.gstatic.com https://fonts.googleapis.com;frame-src 'self' https://tinder-api.arkoselabs.com https://*.*.paypal.com https://*.paypal.com https://*.google-analytics.com https://*.analytics.google.com https://*.googletagmanager.com https://*.g.doubleclick.net https://*.doubleclick.net https://*.google.com https://maps.googleapis.com https://*.gstatic.com https://fonts.googleapis.com;frame-ancestors 'self';form-action 'self' *.tinder.com tinder.com;object-src 'none';img-src 'self' data: blob: https://*.gotinder.com https://*.scdn.co https://*.cdninstagram.com https://*.cloudfront.net https://*.s3.amazonaws.com https://*.*.paypal.com https://*.paypalobjects.com https://*.google-analytics.com https://*.analytics.google.com https://*.googletagmanager.com https://*.g.doubleclick.net https://*.doubleclick.net https://*.google.com https://maps.googleapis.com https://*.gstatic.com https://fonts.googleapis.com;media-src 'self' data: https://*.scdn.co https://*.spotify.com https://media.tenor.com;report-to csp-reports;font-src 'self' data: https:;manifest-src 'self' https:
content-security-policy: default-src *;script-src * 'unsafe-inline' 'unsafe-eval';style-src * 'unsafe-inline' blob:;img-src * data: blob:;media-src * data:;font-src * data: https:
report-to: {"group":"csp-reports","max_age":604800,"endpoints":[{"url":"/api/csp-reports"}]}
x-render-method: ssr
cache-control: must-revalidate, public, max-age=3600
cross-origin-opener-policy: same-origin-allow-popups
etag: W/"6f667-97ZFHLj4Li8hM3suhUlhaWuwsmo"
content-encoding: gzip
vary: Accept-Encoding
x-cache: Miss from cloudfront
via: 1.1 f4931915c262d78fa3e94b48faa4f55a.cloudfront.net (CloudFront)
x-amz-cf-pop: ORD56-P1
x-amz-cf-id: _mJWzqIJwcr4XIY1qHygN2St_2dKBAmn23gIeld3xLEfEtj7PM79Xg==
x-xss-protection: 1; mode=block
x-frame-options: SAMEORIGIN
x-content-type-options: nosniff
strict-transport-security: max-age=31536000

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 facebook-domain-verification=mubcqnl1rf89sxi0nk4gc1hij354ff 300
TXT google-site-verification=8Lg81wA2KUu6Decn-GH3tkOB5VeYAUsCWMpUAGEFwDc 300
TXT google-site-verification=rBpv3L9D4zbAMPOmrNZvyMW5yiWPc4wlUcAAEffiyU0 300
TXT google-site-verification=hl89faooobd53l_n3yaXMKWqxj9HQmJ1uHIF0JA-MDw 300
TXT v=spf1 include:mail.zendesk.com include:_spf.google.com include:_spf1.tinder.com -all 300
TXT google-site-verification=3DRNth5Cc4J6V0isjY7TVFKBv_dzH52aPupt2Axa_fQT4 300
TXT google-site-verification=bfJd9owFtmCvui4O6JrDJLVnSJA_aaxJOJuOEFbInF4 300
TXT facebook-domain-verification=9o6q82t8kc2hyjisuur2ihrb5p030t 300
TXT OSSRH-49342 300
MX alt1.aspmx.l.google.com 300
MX alt2.aspmx.l.google.com 300
MX aspmx2.googlemail.com 300
MX aspmx3.googlemail.com 300
MX aspmx.l.google.com 300
SOA 900
Mname ns-1483.awsdns-57.org
Rname awsdns-hostmaster.amazon.com
Serial Number 1
Refresh 7200
Retry 900
Expire 1209600
Minimum TTL 86400
A 52.84.150.54 60
A 52.84.150.60 60
A 52.84.150.39 60
A 52.84.150.55 60
NS ns-303.awsdns-37.com 172739
NS ns-684.awsdns-21.net 172739
NS ns-1483.awsdns-57.org 172739
NS ns-1571.awsdns-04.co.uk 172739
CAA amazon.com 300
CAA letsencrypt.org 300
CAA godaddy.com 300

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 October 15, 1998 and will expire on October 14, 2025 if not renewed. This website is now assigned through the registrar MarkMonitor Inc.. The WHOIS data for this website's domain was last updated on September 12, 2024.
Domain Created:
1998-10-15
Domain Expires:
2025-10-14
Domain Updated:
2024-09-12
Domain Age:
26 years 5 months 7 days
Domain Registrar:
MarkMonitor Inc.
Domain Owner:
Match Group, LLC
WhoIs:
 

Domain Name: tinder.com
Registry Domain ID: 2193473_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.markmonitor.com
Registrar URL: http://www.markmonitor.com
Updated Date: 2024-09-12T09:32:59+0000
Creation Date: 1998-10-15T04:00:00+0000
Registrar Registration Expiration Date: 2025-10-14T00:00:00+0000
Registrar: MarkMonitor, Inc.
Registrar IANA ID: 292
Registrar Abuse Contact Email: email
Registrar Abuse Contact Phone: +1.2086851750
Domain Status: clientUpdateProhibited (https://www.icann.org/epp#clientUpdateProhibited)
Domain Status: clientTransferProhibited (https://www.icann.org/epp#clientTransferProhibited)
Domain Status: clientDeleteProhibited (https://www.icann.org/epp#clientDeleteProhibited)
Registrant Organization: Match Group, LLC
Registrant State/Province: TX
Registrant Country: US
Registrant Email: Select Request Email Form at https://domains.markmonitor.com/whois/tinder.com
Admin Organization: Match Group, LLC
Admin State/Province: TX
Admin Country: US
Admin Email: Select Request Email Form at https://domains.markmonitor.com/whois/tinder.com
Tech Organization: Match Group, LLC
Tech State/Province: TX
Tech Country: US
Tech Email: Select Request Email Form at https://domains.markmonitor.com/whois/tinder.com
Name Server: ns-1483.awsdns-57.org
Name Server: ns-1571.awsdns-04.co.uk
Name Server: ns-303.awsdns-37.com
Name Server: ns-684.awsdns-21.net
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2025-03-15T20:23:39+0000