mika.care Mika.care

   
Mikata Health

Domain Summary

What is the traffic rank for Mika.care?

• Mika.care ranks #221,828 globally on HypeStat.

What percent of global Internet users visit Mika.care?

• 0.0002034% of global Internet users visit Mika.care

How many people visit Mika.care each day?

• Mika.care receives approximately 10K visitors and 12,274 page impressions per day.

How much Mika.care can earn?

• Mika.care should earn about $50.08/day from advertising revenue.

What is Mika.care estimated value?

• Estimated value of Mika.care is $45,642.55.

What IP addresses does Mika.care resolve to?

• Mika.care resolves to the IP addresses 198.185.159.145.

Where are Mika.care servers located in?

• Mika.care has servers located in United States.

mika.care Profile

Title:Mikata Health
Description:Your clinic uses Mikata Health to enhance your care.
Edit Site Info

What technologies does mika.care use?

These are the technologies used at mika.care. mika.care has a total of 6 technologies installed in 4 different categories.
Miscellaneous
Amazon S3 Amazon S3
Open Graph Open Graph
PWA PWA
Security
HSTS HSTS
PaaS
Netlify Netlify
Amazon Web Services Amazon Web Services
CDN
Netlify Netlify

mika.care Traffic Analysis

Mika.care is ranked #221,828 in the world. This website is viewed by an estimated 10K visitors daily, generating a total of 12.3K pageviews. This equates to about 303.9K monthly visitors. Mika.care traffic has increased by 19.61% compared to last month.
Daily Visitors10K
4.64%
Monthly Visits303.9K
19.61%
Pages per Visit1.22
9.31%
Visit duration00:34
50.49%
Bounce Rate82.45%
0.11%
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
10,029
Monthly Visits:
303,879
Pages per Visit:
1.22
Daily Pageviews:
12,274
Avg. visit duration:
00:34
Bounce rate:
82.45%
Global Reach:
0.0002034%
Monthly Visits (SEMrush):
397,728
Monthly Unique Visitors (SEMrush):
166,937
Monthly Visits (SimilarWeb):
297,879
HypeRank:
221,828
SimilarWeb Rank:
221,828
*All traffic values are estimates only.

Traffic sources

Direct:
97.23%
Referral:
2.77%
Search:
0%
Social:
0%
Paid:
0%

Desktop vs Mobile

Desktop:
0.17%
Mobile:
99.83%

Total Visits Last 3 Months

274.6K
NOV
254.1K
DEC
303.9K
JAN
Last update was 9 hours ago
     
This can take up to 60 seconds. Please wait...

Update will be available in 15 hours
*HypeStat.com is not promoting or affiliated with mika.care 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

  ▼

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:
  mika.care
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.1 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 $45.6K.

How much would mika.care make?

Daily Revenue:
$50.08
Monthly Revenue:
$1,502.40
Yearly Revenue:
$18,279.20
*All earnings values are estimates only.

How much is mika.care worth?

Website Value:
$45.6K

Ad Experience Report ▼

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

Mobile summary

Root domain:
mika.care
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:
mika.care
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:
mika.care
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 mika.care hosted? ▼

Mika.care may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.
Server IP:
198.185.159.145
ASN:
AS53831 
ISP:
Squarespace, Inc. 
Server Location:

United States, US
 

Other sites hosted on 198.185.159.145

How fast does mika.care load? ▼

The average loading time of mika.care is 303 ms. The Desktop speed index is 98 and mobile speed index is 75.
Average Load Time:
303 ms

Page Speed (Google PageSpeed Insights) - Desktop

98
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)19ms 50% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 50% 44% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 44% 5% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 5%
Time To First Byte (TTFB)1.1s 61% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 61% 31% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 31% 7% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 7%
First Contentful Paint (FCP)2.5s 52% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 52% 31% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 31% 15% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 15%
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)49ms 98% of loads for this page have a fast (<200ms) Interaction To Next Paint (INP) 98% 0% of loads for this page have an average (200ms ~ 500ms) Interaction To Next Paint (INP) 0% 0% of loads for this page have a slow (>500ms) Interaction To Next Paint (INP) 0%
Largest Contentful Paint (LCP)2.7s 68% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 68% 21% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 21% 9% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 9%

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)19ms 50% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 50% 44% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 44% 5% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 5%
Time To First Byte (TTFB)1.1s 61% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 61% 31% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 31% 7% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 7%
First Contentful Paint (FCP)2.5s 52% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 52% 31% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 31% 15% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 15%
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)49ms 98% of loads for this page have a fast (<200ms) Interaction To Next Paint (INP) 98% 0% of loads for this page have an average (200ms ~ 500ms) Interaction To Next Paint (INP) 0% 0% of loads for this page have a slow (>500ms) Interaction To Next Paint (INP) 0%
Largest Contentful Paint (LCP)2.7s 68% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 68% 21% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 21% 9% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 9%

Lab Data

Improve image delivery  
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
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
INP by phase  
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
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
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
LCP request discovery  
Optimize LCP by making the LCP image from the HTML immediately, and discoverable avoiding lazy-loading
Speed Index 0.9 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
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
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 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric
Long critical network tree  
by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Avoid chaining critical requests
Largest Contentful Paint 0.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 0.9 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
Max Potential First Input Delay 40 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
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 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
First Meaningful Paint  
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric

Page Speed (Google PageSpeed Insights) - Mobile

75
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)100ms 50% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 56% 16% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 16% 27% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 27%
Time To First Byte (TTFB)975ms 61% of loads for this page have a fast (<800s) Time To First Byte (TTFB) 62% 32% of loads for this page have an average (800s ~ 1800s) Time To First Byte (TTFB) 32% 5% of loads for this page have a slow (>1800s) Time To First Byte (TTFB) 5%
First Contentful Paint (FCP)2.7s 52% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 34% 47% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 47% 18% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 18%
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)88ms 98% of loads for this page have a fast (<200s) Interactive To Next Paint (INP) 96% 2% of loads for this page have an average (200s ~ 500s) Interactive To Next Paint (INP) 2% 0% of loads for this page have a slow (>500s) Interactive To Next Paint (INP) 0%
Largest Contentful Paint (LCP)3.0s 68% of loads for this page have a fast (<2500s) Largest Contentful Paint (LCP) 60% 30% of loads for this page have an average (2500s ~ 4000s) Largest Contentful Paint (LCP) 30% 9% of loads for this page have a slow (>4000s) Largest Contentful Paint (LCP) 9%

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)100ms 56% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 56% 16% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 16% 27% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 27%
Time To First Byte (TTFB)975ms 62% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 62% 32% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 32% 5% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 5%
First Contentful Paint (FCP)2.7s 34% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 34% 47% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 47% 18% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 18%
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)88ms 96% of loads for this page have a fast (<0.2s) Interactive To Next Paint (INP) 96% 2% of loads for this page have an average (0.2s ~ 0.5s) Interactive To Next Paint (INP) 2% 0% of loads for this page have a slow (>0.5s) Interactive To Next Paint (INP) 0%
Largest Contentful Paint (LCP)3.0s 60% of loads for this page have a fast (<2.5s)Largest Contentful Paint (LCP) 60% 30% of loads for this page have an average (2.5s ~ 4s)Largest Contentful Paint (LCP) 30% 9% of loads for this page have a slow (>4s)Largest Contentful Paint (LCP) 9%

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
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
Speed Index 5.1 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
LCP request discovery  
Optimize LCP by making the LCP image from the HTML immediately, and discoverable avoiding lazy-loading
INP by phase  
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
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 4.1 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
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
Improve image delivery  
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Max Potential First Input Delay 20 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
Font display  
Consider setting to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with . font-display font metric overrides
First Contentful Paint 4.1 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 4.1 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
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric
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 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

Does mika.care 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 mika.care are reduced by %.
mika.care does not use compression.
Original size: 1007 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. mika.care has 80 Safety Reputations.
Status:
  SAFE
Safety Reputations:
  80
Safety Confidence:
  51

SSL Checker - SSL Certificate Verify ▼

An SSL (Secure Sockets Layer) certificate is a digital certificate that establishes a secure encrypted connection between a web server and a user's web browser. It provides authentication and encryption, ensuring that data transmitted between the server and the browser remains private and protected. mika.care supports HTTPS.
 mika.care supports HTTPS
     
Verifying SSL Support. Please wait...
Common Name: chat.mikatahealth.com
Organization:
Location:
Issuer: E5
Valid from: Jan 18 15:13:38 2025 GMT
Valid until: Apr 18 15:13:37 2025 GMT
Authority: CA:FALSE
Keysize:
Common Name: E5
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:

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.
 mika.care 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: 14043
date: Wed, 05 Mar 2025 16:26:49 GMT
location: https://chat.mikatahealth.com
server: Squarespace
set-cookie: crumb=Bd2d+c6372TuYzdkODY2NDI1ZWU5Zjg1MjBlNDdjNDcxNjJjNzY4;Secure;Path=/
x-contextid: ebjJhLey/4jS2NDMz
content-length: 0

HTTP/2 200 
accept-ranges: bytes
age: 10981
cache-control: max-age=0,no-cache,no-store,must-revalidate
cache-status: "Netlify Edge"; hit
content-security-policy-report-only: default-src 'self' *.mikatahealth.com; font-src 'self' https://netdna.bootstrapcdn.com/font-awesome/4.6.3/fonts/fontawesome-webfont.woff; img-src 'self' https://mikata-production-ca-central-1-org-logo-uploads.s3.ca-central-1.amazonaws.com/; script-src 'self'; style-src 'self'; frame-ancestors 'self'; report-uri https://0hetp96g.uriports.com/reports/report; report-to default
content-type: text/html; charset=UTF-8
date: Wed, 05 Mar 2025 21:11:23 GMT
etag: "a932611541969dbed86ec01a2e31d7fb-ssl"
nel: {"report_to":"default","max_age":2592000,"include_subdomains":true,"failure_fraction":1.0}
reporting-endpoints: default="https://0hetp96g/urireports.com/reports"
server: Netlify
strict-transport-security: max-age=31536000; includeSubDomains
x-content-type-options: nosniff
x-nf-request-id: 01JNM2C7PPAB00FWCJYSAJESDW
content-length: 1007

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 21600
Mname ns-cloud-c1.googledomains.com
Rname cloud-dns-hostmaster.google.com
Serial Number 9
Refresh 21600
Retry 3600
Expire 259200
Minimum TTL 300
A 198.185.159.145 14360
NS ns-cloud-c1.googledomains.com 3560
NS ns-cloud-c4.googledomains.com 3560
NS ns-cloud-c3.googledomains.com 3560
NS ns-cloud-c2.googledomains.com 3560

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 January 25, 2022 and will expire on January 25, 2026 if not renewed. This website is now assigned through the registrar Squarespace Domains II LLC. The WHOIS data for this website's domain was last updated on January 15, 2025.
Domain Created:
2022-01-25
Domain Expires:
2026-01-25
Domain Updated:
2025-01-15
Domain Age:
3 years 1 months 12 days
Domain Registrar:
Squarespace Domains II LLC
Domain Owner:
REDACTED FOR PRIVACY
WhoIs:
 

Domain Name: mika.care
Registry Domain ID: 347cd3e5481249e9bc0513efe85208a3-DONUTS
Registrar WHOIS Server: whois.donuts.co
Registrar URL: 
Updated Date: 2025-01-15T22:42:00Z
Creation Date: 2022-01-25T18:58:07Z
Registry Expiry Date: 2026-01-25T18:58:07Z
Registrar: Squarespace Domains II LLC
Registrar IANA ID: 895
Registrar Abuse Contact Email: email
Registrar Abuse Contact Phone: +1.6466935324
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID: REDACTED FOR PRIVACY
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: 
Registrant Street: REDACTED FOR PRIVACY
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province: AB
Registrant Postal Code: REDACTED FOR PRIVACY
Registrant Country: CA
Registrant Phone: REDACTED FOR PRIVACY
Registrant Phone Ext: REDACTED FOR PRIVACY
Registrant Fax: REDACTED FOR PRIVACY
Registrant Fax Ext: REDACTED FOR PRIVACY
Registrant Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Admin ID: REDACTED FOR PRIVACY
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State/Province: REDACTED FOR PRIVACY
Admin Postal Code: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Phone Ext: REDACTED FOR PRIVACY
Admin Fax: REDACTED FOR PRIVACY
Admin Fax Ext: REDACTED FOR PRIVACY
Admin Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Tech ID: REDACTED FOR PRIVACY
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State/Province: REDACTED FOR PRIVACY
Tech Postal Code: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Phone Ext: REDACTED FOR PRIVACY
Tech Fax: REDACTED FOR PRIVACY
Tech Fax Ext: REDACTED FOR PRIVACY
Tech Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Name Server: ns-cloud-c1.googledomains.com
Name Server: ns-cloud-c2.googledomains.com
Name Server: ns-cloud-c3.googledomains.com
Name Server: ns-cloud-c4.googledomains.com
DNSSEC: signedDelegation
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2025-03-05T21:12:02Z