Nakoma.ch
Welcome to nginx!
Domain Summary
What percent of global Internet users visit Nakoma.ch?
• 8.0E-7% of global Internet users visit Nakoma.ch
How many people visit Nakoma.ch each day?
• Nakoma.ch receives approximately 38 visitors and 503 page impressions per day.
How much Nakoma.ch can earn?
• Nakoma.ch should earn about $2.05/day from advertising revenue.
What is Nakoma.ch estimated value?
• Estimated value of Nakoma.ch is $2,019.27.
What IP addresses does Nakoma.ch resolve to?
• Nakoma.ch resolves to the IP addresses 45.223.65.199.
Where are Nakoma.ch servers located in?
• Nakoma.ch has servers located in United States.
nakoma.ch Profile
Title:Welcome to nginx!
Description:wir führen hosting, backup und dienstleistung zu einem einzigartigen erlebnis. modernes panel, ausgezeichneter supprt, modernste hardware und ein grosszügies team.
What technologies does nakoma.ch use?
These are the technologies used at nakoma.ch. nakoma.ch has a total of 4 technologies installed in 4 different categories.
nakoma.ch Traffic Analysis
This website is viewed by an estimated 38 visitors daily, generating a total of 503 pageviews. This equates to about 1.2K monthly visitors. Nakoma.ch traffic has decreased by 82.63% compared to last month.Daily Visitors38
45.95%
Monthly Visits1.2K
82.63%
Pages per Visit13.29
35.29%
Visit duration02:31
23.77%
Bounce Rate n/a
100%
Is this your site?Verify your site's metrics.
- Daily Unique Visitors:
- 38
- Monthly Visits:
- 1,151
- Pages per Visit:
- 13.29
- Daily Pageviews:
- 503
- Avg. visit duration:
- 02:31
- Bounce rate:
- n/a
- Global Reach:
- 8.0E-7%
- Monthly Visits (SEMrush):
- 1,125
- Monthly Unique Visitors (SEMrush):
- 527
- HypeRank:
- n/a
Traffic sources
- Direct:
- 61.07%
- Referral:
- 0%
- Search:
- 38.93%
- Social:
- 0%
- Paid:
- 0%
Desktop vs Mobile
- Desktop:
- 100.00%
- Mobile:
- 0%
Total Visits Last 3 Months
594
DEC
6.6K
JAN
1.2K
FEB
Backlinks Report ▼
Nakoma.ch has a total of 33 backlinks from 28 referring domains and most of them comes from United States.- Total Backlinks:
- 33
- Follow Links:
- n/a
- Nofollow Links:
- n/a
- Referring Domains:
- 28
- Referring IPs:
- 28
- Authority Domain Score:
- 2
Backlinks by country
- Country
- Domains
- United States 4
- Germany 2
- Russian Federation 1
- Romania 1
- Netherlands 1
Backlinks by TLDs
- TLD Distribution
- Domains
- .com
- 15
- .dev
- 3
- .net
- 2
- .edu
- 0
- .gov
- 0
Last update was 203 days ago
This can take up to 60 seconds. Please wait...
This can take up to 60 seconds. Please wait...
*HypeStat.com is not promoting or affiliated with nakoma.ch 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:
- 10
▼
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.- Domain:
- nakoma.ch
- 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
Revenue report ▼
Google.com would generate approximately $2.1 per day if the source of income were advertisements, which equates to an estimated monthly revenue of $61.5 and annual gross revenue of approximately $748.3. Based on these figures, the site's net worth is estimated at around $2K.How much would nakoma.ch make?
- Daily Revenue:
- $2.05
- Monthly Revenue:
- $61.50
- Yearly Revenue:
- $748.25
How much is nakoma.ch worth?
- Website Value:
- $2K
Ad Experience Report ▼
Summary of the ad experience rating of a website for a specific platform.Mobile summary
- Root domain:
- nakoma.ch
- 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:
- nakoma.ch
- 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:
- nakoma.ch
- 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 nakoma.ch hosted? ▼
Nakoma.ch may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.- Server IP:
- 45.223.65.199
- ASN:
- ISP:
- Server Location:
United States, US
Other sites hosted on 45.223.65.199
There are no other sites hosted on this IPHow fast does nakoma.ch load? ▼
The average loading time of nakoma.ch is 393 ms. The Desktop speed index is 100 and mobile speed index is 100.- Average Load Time:
- 393 ms
Page Speed (Google PageSpeed Insights) - Desktop
Field Data
Over the last 30 days, the field data shows that this page has a 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)0
Time To First Byte (TTFB)0
First Contentful Paint (FCP)0
First Input Delay (FID)0
Interaction To Next Paint (INP)0
Largest Contentful Paint (LCP)0
Origin Data
All pages served from this origin have an 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)0
Time To First Byte (TTFB)0
First Contentful Paint (FCP)0
First Input Delay (FID)0
Interaction To Next Paint (INP)0
Largest Contentful Paint (LCP)0
Lab Data
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
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
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
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
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
Third parties
Third party code can significantly impact load performance. to prioritize your page's content. Reduce and defer loading of third party code
Third party code can significantly impact load performance. to prioritize your page's content. Reduce and defer loading of third party code
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
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
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
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
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
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
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
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
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
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
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
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
LCP request discovery
Optimize LCP by making the LCP image from the HTML immediately, and discoverable avoiding lazy-loading
Optimize LCP by making the LCP image from the HTML immediately, and discoverable avoiding lazy-loading
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
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 0.3 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Minimize third-party usage
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact
Does not have 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
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
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
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 0.2 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint 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
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
Max Potential First Input Delay 50 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
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
Time to Interactive 0.2 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
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
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
First Contentful Paint 0.2 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
Page Speed (Google PageSpeed Insights) - Mobile
Field Data
Over the last 30 days, the field data shows that this page has a 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)0
Time To First Byte (TTFB)0
First Contentful Paint (FCP)0
First Input Delay (FID)0
Interactive To Next Paint (INP)0
Largest Contentful Paint (LCP)0
Origin Data
All pages served from this origin have an 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)0
Time To First Byte (TTFB)0
First Contentful Paint (FCP)0
First Input Delay (FID)0
Interactive To Next Paint (INP)0
Largest Contentful Paint (LCP)0
Lab Data
INP by phase
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
Time to Interactive 0.8 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
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
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
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
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
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
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
Third parties
Third party code can significantly impact load performance. to prioritize your page's content. Reduce and defer loading of third party code
Third party code can significantly impact load performance. to prioritize your page's content. Reduce and defer loading of third party code
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
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
Does not have 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
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
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
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
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
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index 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
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
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
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
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
Largest Contentful Paint 0.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint 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
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
LCP request discovery
Optimize LCP by making the LCP image from the HTML immediately, and discoverable avoiding lazy-loading
Optimize LCP by making the LCP image from the HTML immediately, and discoverable avoiding lazy-loading
Minimize third-party usage
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact
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
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
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
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
Many APIs, typically reading layout geometry, force the rendering engine to pause script execution in order to calculate the style and layout. Learn more about and its mitigations. forced reflow
First Meaningful Paint
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint 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
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
Does nakoma.ch 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 nakoma.ch are reduced by 33%.
nakoma.ch use gzip compression.
Original size: 749 B
Compressed size: 500 B
File reduced by: 249 B (33%)
Compressed size: 500 B
File reduced by: 249 B (33%)
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.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. nakoma.ch supports HTTPS. nakoma.ch supports HTTPS
Verifying SSL Support. Please wait...
Common Name: imperva.com
Organization:
Location:
Issuer: GlobalSign Atlas R3 DV TLS CA 2025 Q1
Valid from: Feb 23 10:06:26 2025 GMT
Valid until: Aug 22 10:05:50 2025 GMT
Authority: CA:FALSE
Keysize: 2048 Bits
Organization:
Location:
Issuer: GlobalSign Atlas R3 DV TLS CA 2025 Q1
Valid from: Feb 23 10:06:26 2025 GMT
Valid until: Aug 22 10:05:50 2025 GMT
Authority: CA:FALSE
Keysize: 2048 Bits
Common Name: GlobalSign Atlas R3 DV TLS CA 2025 Q1
Organization: GlobalSign nv-sa
Location: BE
Issuer: GlobalSign
Valid from: Oct 16 03:08:04 2024 GMT
Valid until: Oct 16 00:00:00 2026 GMT
Authority: CA:TRUE
Keysize: 2048 Bits
Organization: GlobalSign nv-sa
Location: BE
Issuer: GlobalSign
Valid from: Oct 16 03:08:04 2024 GMT
Valid until: Oct 16 00:00:00 2026 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. nakoma.ch 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.server: nginx
date: Mon, 24 Mar 2025 07:22:18 GMT
content-type: text/html; charset=utf-8
vary: Accept-Encoding
last-modified: Wed, 19 Oct 2022 10:48:27 GMT
etag: W/"634fd5fb-267"
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
referrer-policy: no-referrer-when-downgrade
content-security-policy: default-src 'self' http: https: ws: wss: data: blob: 'unsafe-inline'; frame-ancestors 'self';
permissions-policy: interest-cohort=()
strict-transport-security: max-age=31536000; includeSubDomains
content-encoding: gzip
set-cookie: visid_incap_3166296=aS7qFGoYTAS+7L3h1+hhhX8I4WcAAAAAQUIPAAAAAABf4FG5W6dMl0Yl3IjYityT; expires=Mon, 23 Mar 2026 23:28:49 GMT; HttpOnly; path=/; Domain=.nakoma.ch
set-cookie: incap_ses_128_3166296=1MS2Y4sna0/AqpT0jr/GAX8I4WcAAAAAQo2Ntx6zBoBxCAaYpLCKxw==; path=/; Domain=.nakoma.ch
x-cdn: Imperva
x-iinfo: 11-40259921-40259943 nNNN RT(1742801024008 103) q(0 0 1 -1) r(1 1) U12
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 |
| MX | 38400 | ||
| MX | 38400 | ||
| MX | 38400 | ||
| TXT | 38400 | ||
| TXT | 38400 | ||
| TXT | 38400 | ||
| TXT | 38400 | ||
| TXT | 38400 | ||
| TXT | 38400 | ||
| TXT | 38400 | ||
| TXT | 38400 | ||
| TXT | 38400 | ||
| TXT | 38400 | ||
| TXT | 38400 | ||
| SOA | 38400 | ||
| Mname | dns.nakoma.ch | ||
| Rname | helpdesk\.hsn.nakoma.ch | ||
| Serial Number | 2025030600 | ||
| Refresh | 43200 | ||
| Retry | 1200 | ||
| Expire | 1209600 | ||
| Minimum TTL | 38400 | ||
| A | 45.223.65.199 | 38353 | |
| A | 45.223.68.199 | 38353 | |
| NS | 3552 | ||
| NS | 3552 | ||
| NS | 3552 | ||
| NS | 3552 | ||
| CAA | 38400 | ||
| CAA | 38400 | ||
| CAA | 38400 | ||
| CAA | 38400 | ||
| CAA | 38400 |
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.- WhoIs:
Requests of this client are not permitted. Please use https://www.nic.ch/whois/ for queries.