findinglove.life Findinglove.life

   

Domain Summary

What is the traffic rank for Findinglove.life?

• Findinglove.life ranks #1,170,918 globally on HypeStat.

What percent of global Internet users visit Findinglove.life?

• 0.00024% of global Internet users visit Findinglove.life

How many people visit Findinglove.life each day?

• Findinglove.life receives approximately 11.8K visitors and 27,681 page impressions per day.

Which countries does Findinglove.life receive most of its visitors from?

• Findinglove.life is mostly visited by people located in Italy,Spain,Colombia.

How much Findinglove.life can earn?

• Findinglove.life should earn about $50.18/day from advertising revenue.

What is Findinglove.life estimated value?

• Estimated value of Findinglove.life is $42,582.68.

What IP addresses does Findinglove.life resolve to?

• Findinglove.life resolves to the IP addresses 185.155.186.18.

Where are Findinglove.life servers located in?

• Findinglove.life has servers located in Switzerland.

findinglove.life Profile

Title:
Category:Community and Society / Dating and Relationships
Edit Site Info

What technologies does findinglove.life use?

These are the technologies used at findinglove.life. findinglove.life has a total of 2 technologies installed in 3 different categories.
Web Frameworks
Microsoft ASP.NET Microsoft ASP.NET
Web Servers
Nginx Nginx
Reverse proxies
Nginx Nginx

findinglove.life Traffic Analysis

Findinglove.life is ranked #1,170,918 in the world. This website is viewed by an estimated 11.8K visitors daily, generating a total of 27.7K pageviews. This equates to about 358.5K monthly visitors. Findinglove.life traffic has decreased by 51.74% compared to last month.
Daily Visitors11.8K
56.81%
Monthly Visits358.5K
51.74%
Pages per Visit2.34
60.83%
Visit duration00:54
73.44%
Bounce Rate64.09%
28.88%
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
11,833
Monthly Visits:
358,540
Pages per Visit:
2.34
Daily Pageviews:
27,681
Avg. visit duration:
00:54
Bounce rate:
64.09%
Global Reach:
0.00024%
Monthly Visits (SEMrush):
141,975
Monthly Unique Visitors (SEMrush):
117,389
Monthly Visits (SimilarWeb):
351,476
HypeRank:
1,170,918
SimilarWeb Rank:
165,679
*All traffic values are estimates only.

Traffic sources

Direct:
72.19%
Referral:
6.21%
Search:
21.60%
Social:
0%
Paid:
0%

Desktop vs Mobile

Desktop:
24.88%
Mobile:
75.12%

Total Visits Last 3 Months

483.2K
AUG
742.9K
SEP
358.5K
OCT

Visitors by country

Country
Users%
 
Italy 26.38%
 
Spain 11.92%
 
Colombia 9.96%
 
France 9.09%
 
Brazil 6.14%

Which sites are competitors to findinglove.life?

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

*HypeStat.com is not promoting or affiliated with findinglove.life 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.
Bing Index:
2

  ▼

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:
  findinglove.life
Rank:
(Rank based on keywords, cost and organic traffic)
  n/a
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  0
Organic Traffic:
(Number of visitors coming from top 20 search results)
  0
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 $50.2 per day if the source of income were advertisements, which equates to an estimated monthly revenue of $1.5K and annual gross revenue of approximately $18.3K. Based on these figures, the site's net worth is estimated at around $42.6K.

How much would findinglove.life make?

Daily Revenue:
$50.18
Monthly Revenue:
$1,505.40
Yearly Revenue:
$18,315.70
*All earnings values are estimates only.

Daily earning by country

 
CountryPageviewsEarning
 
Brazil 1,700$2.26
 
Colombia 2,758$1.90
 
Italy 7,303$1.75
 
Spain 3,300$1.58
 
France 2,517$1.46

Loss of money due to Adblock?

Daily Revenue Loss:
$1.05
Monthly Revenue Loss:
$31.42
Yearly Revenue Loss:
$382.29
Daily Pageviews Blocked:
2,468
Monthly Pageviews Blocked:
74,039
Yearly Pageviews Blocked:
900,805

Daily revenue loss by country

 
CountryBlockedLost Money
 
Spain 627$0.30
 
Italy 1,241$0.30
 
France 277$0.16
 
Colombia 221$0.15
 
Brazil 102$0.14

How much is findinglove.life worth?

Website Value:
$42.6K

Ad Experience Report ▼

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

Mobile summary

Root domain:
findinglove.life
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:
findinglove.life
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:
findinglove.life
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 findinglove.life hosted? ▼

Findinglove.life may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.

How fast does findinglove.life load? ▼

The average loading time of findinglove.life is 481 ms. The Desktop speed index is 72 and mobile speed index is 35.
Average Load Time:
481 ms

Page Speed (Google PageSpeed Insights) - Desktop

72
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 96% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 96% 2% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 2% 0% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)973ms 70% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 70% 19% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 19% 10% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 10%
First Contentful Paint (FCP)2.2s 68% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 68% 17% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 17% 14% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 14%
First Input Delay (FID)2ms 99% of loads for this page have a fast (<100ms) First Input Delay (FID) 99% 0% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>300ms) First Input Delay (FID) 0%
Interaction To Next Paint (INP)159ms 81% of loads for this page have a fast (<200ms) Interaction To Next Paint (INP) 81% 13% of loads for this page have an average (200ms ~ 500ms) Interaction To Next Paint (INP) 13% 5% of loads for this page have a slow (>500ms) Interaction To Next Paint (INP) 5%
Largest Contentful Paint (LCP)4.2s 53% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 53% 22% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 22% 24% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 24%

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)4ms 96% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 96% 2% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 2% 0% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)762ms 78% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 78% 15% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 15% 6% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 6%
First Contentful Paint (FCP)1.6s 81% 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% 7% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 7%
First Input Delay (FID)2ms 99% of loads for this page have a fast (<100ms) First Input Delay (FID) 99% 0% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>300ms) First Input Delay (FID) 0%
Interaction To Next Paint (INP)167ms 80% of loads for this page have a fast (<200ms) Interaction To Next Paint (INP) 80% 14% of loads for this page have an average (200ms ~ 500ms) Interaction To Next Paint (INP) 14% 5% of loads for this page have a slow (>500ms) Interaction To Next Paint (INP) 5%
Largest Contentful Paint (LCP)3.9s 54% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 54% 23% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 23% 21% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 21%

Lab Data

Speed Index 2.4 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Timing budget  
Set a timing budget to help you keep an eye on the performance of your site. Performant sites load fast and respond to user input events quickly. Learn more about performance budgets
Performance budget  
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more about performance budgets
Has a `<meta name="viewport">` tag with `width` or `initial-scale`  
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents . a 300 millisecond delay to user input Learn more about using the viewport meta tag
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
Largest Contentful Paint 2.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
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
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
Total Blocking Time 140 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 130 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 1.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
Time to Interactive 2.6 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric
First Meaningful Paint 1.7 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
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

35
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)13ms 96% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 64% 27% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 27% 7% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 7%
Time To First Byte (TTFB)1.3s 70% of loads for this page have a fast (<800s) Time To First Byte (TTFB) 53% 30% of loads for this page have an average (800s ~ 1800s) Time To First Byte (TTFB) 30% 15% of loads for this page have a slow (>1800s) Time To First Byte (TTFB) 15%
First Contentful Paint (FCP)3.1s 68% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 40% 33% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 33% 26% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 26%
First Input Delay (FID)43ms 87% of loads for this page have a fast (<100ms) First Input Delay (FID) 87% 8% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 8% 4% of loads for this page have a slow (>300ms) First Input Delay (FID) 4%
Interactive To Next Paint (INP)488ms 81% of loads for this page have a fast (<200s) Interactive To Next Paint (INP) 31% 44% of loads for this page have an average (200s ~ 500s) Interactive To Next Paint (INP) 44% 23% of loads for this page have a slow (>500s) Interactive To Next Paint (INP) 23%
Largest Contentful Paint (LCP)7.1s 53% of loads for this page have a fast (<2500s) Largest Contentful Paint (LCP) 27% 19% of loads for this page have an average (2500s ~ 4000s) Largest Contentful Paint (LCP) 19% 53% of loads for this page have a slow (>4000s) Largest Contentful Paint (LCP) 53%

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)13ms 56% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 56% 36% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 36% 7% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 7%
Time To First Byte (TTFB)1.2s 60% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 60% 27% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 27% 12% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 12%
First Contentful Paint (FCP)2.5s 55% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 55% 27% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 27% 17% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 17%
First Input Delay (FID)33ms 99% of loads for this page have a fast (<100ms) First Input Delay (FID) 89% 7% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 7% 3% of loads for this page have a slow (>300ms) First Input Delay (FID) 3%
Interactive To Next Paint (INP)448ms 34% of loads for this page have a fast (<0.2s) Interactive To Next Paint (INP) 34% 45% of loads for this page have an average (0.2s ~ 0.5s) Interactive To Next Paint (INP) 45% 20% of loads for this page have a slow (>0.5s) Interactive To Next Paint (INP) 20%
Largest Contentful Paint (LCP)6.2s 25% of loads for this page have a fast (<2.5s)Largest Contentful Paint (LCP) 25% 24% of loads for this page have an average (2.5s ~ 4s)Largest Contentful Paint (LCP) 24% 50% of loads for this page have a slow (>4s)Largest Contentful Paint (LCP) 50%

Lab Data

Lazy load third-party resources with facades  
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade
First Meaningful Paint 5.3 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
Max Potential First Input Delay 550 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
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 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
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
Total Blocking Time 1,700 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
Has a `<meta name="viewport">` tag with `width` or `initial-scale`  
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents . a 300 millisecond delay to user input Learn more about using the viewport meta tag
Largest Contentful Paint 10.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
Timing budget  
Set a timing budget to help you keep an eye on the performance of your site. Performant sites load fast and respond to user input events quickly. Learn more about performance budgets
First Contentful Paint 3.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
Time to Interactive 13.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
Performance budget  
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more about performance budgets
Speed Index 6.7 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric

Does findinglove.life 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 findinglove.life are reduced by %.
findinglove.life does not use compression.
Original size: 676 B
Compressed size: n/a
File reduced by: (%)

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:
  UNKNOWN

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. findinglove.life supports HTTPS.
 findinglove.life supports HTTPS
     
Verifying SSL Support. Please wait...
Common Name: findinglove.life
Organization:
Location:
Issuer: R3
Valid from: Oct 11 05:36:01 2023 GMT
Valid until: Jan 9 05:36:00 2024 GMT
Authority: CA:FALSE
Keysize: 2048 Bits
Common Name: R3
Organization: Let's Encrypt
Location: US
Issuer: ISRG Root X1
Valid from: Sep 4 00:00:00 2020 GMT
Valid until: Sep 15 16:00:00 2025 GMT
Authority: CA:TRUE
Keysize: 2048 Bits
Common Name: ISRG Root X1
Organization: Internet Security Research Group
Location: US
Issuer: DST Root CA X3
Valid from: Jan 20 19:14:03 2021 GMT
Valid until: Sep 30 18:14:03 2024 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.
 findinglove.life does not support 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: nginx
Date: Wed, 08 Nov 2023 13:30:57 GMT
Content-Type: text/html; charset=utf-8
Connection: close
cache-control: private
set-cookie: sid=t1~4uzawb051qcdcg04bbtgsj52; path=/
Cache-Control: no-transform

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
HINFO 3600
A 185.155.186.18 169
NS blakely.ns.cloudflare.com 3469
NS patryk.ns.cloudflare.com 3469

Whois Lookup ▼

Domain WHOIS is a public database that provides information about domain names, including registered owners, contact information, domain registrars, registration and expiration dates, name servers, and other relevant information. Domain registration for this website began on July 11, 2023 and will expire on July 11, 2024 if not renewed. This website is now assigned through the registrar NAMECHEAP INC. The WHOIS data for this website's domain was last updated on January 1, 0001.
Domain Created:
2023-07-11
Domain Expires:
2024-07-11
Domain Updated:
0001-01-01
Domain Age:
1 years 5 months
Domain Registrar:
NAMECHEAP INC
Domain Owner:
Privacy service provided by Withheld for Privacy e
WhoIs:
 

Domain name: findinglove.life
Registry Domain ID: da3740a43d424827b8efcf46f6d938c4-DONUTS
Registrar WHOIS Server: whois.namecheap.com
Registrar URL: http://www.namecheap.com
Updated Date: 0001-01-01T00:00:00.00Z
Creation Date: 2023-07-11T03:17:37.34Z
Registrar Registration Expiration Date: 2024-07-11T03:17:37.34Z
Registrar: NAMECHEAP INC
Registrar IANA ID: 1068
Registrar Abuse Contact Email: email
Registrar Abuse Contact Phone: +1.9854014545
Reseller: NAMECHEAP INC
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID: 
Registrant Name: Redacted for Privacy
Registrant Organization: Privacy service provided by Withheld for Privacy ehf
Registrant Street: Kalkofnsvegur 2 
Registrant City: Reykjavik
Registrant State/Province: Capital Region
Registrant Postal Code: 101
Registrant Country: IS
Registrant Phone: +354.4212434
Registrant Phone Ext: 
Registrant Fax: 
Registrant Fax Ext: 
Registrant Email: email
Registry Admin ID: 
Admin Name: Redacted for Privacy
Admin Organization: Privacy service provided by Withheld for Privacy ehf
Admin Street: Kalkofnsvegur 2 
Admin City: Reykjavik
Admin State/Province: Capital Region
Admin Postal Code: 101
Admin Country: IS
Admin Phone: +354.4212434
Admin Phone Ext: 
Admin Fax: 
Admin Fax Ext: 
Admin Email: email
Registry Tech ID: 
Tech Name: Redacted for Privacy
Tech Organization: Privacy service provided by Withheld for Privacy ehf
Tech Street: Kalkofnsvegur 2 
Tech City: Reykjavik
Tech State/Province: Capital Region
Tech Postal Code: 101
Tech Country: IS
Tech Phone: +354.4212434
Tech Phone Ext: 
Tech Fax: 
Tech Fax Ext: 
Tech Email: email
Name Server: blakely.ns.cloudflare.com
Name Server: patryk.ns.cloudflare.com
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2023-11-07T18:32:56.30Z