0-6.ch is registered with whois.nic.ch and is hosted on AS16509 in United States. Its SSL certificate from "GoDaddy.com expired on 1 Dec 2024, and the site does not support HTTP/3.
What security vendors and the WOT community say about this domain.
What loads and tracks visitors when the homepage opens.
Running a full browser scan of the homepage… This takes about a minute.
Is 0-6.ch’s name taken on other extensions?
Every IP address 0-6.ch resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| 0-6.ch | 15.197.148.33 | 600 |
| 0-6.ch | 3.33.130.190 | 600 |
| Host | Name server | TTL |
|---|---|---|
| 0-6.ch | ns27.domaincontrol.com | 3600 |
| 0-6.ch | ns28.domaincontrol.com | 3600 |
| Host | Start of authority | TTL |
|---|---|---|
| 0-6.ch | ns27.domaincontrol.com dns.jomax.net 2023092000 28800 7200 604800 600 | 3600 |
Other domains served from 15.197.148.33. Normal for shared hosting and CDNs.
No reviews yet. Used 0-6.ch? Be the first to say how it went.
Reviews are from CubDomain users and are separate from the security verdicts above.
Common questions, answered from this report's data.
0-6.ch has no community safety rating yet. Its SSL certificate expired on 1 Dec 2024. See Security →
0-6.ch is registered through whois.nic.ch. See WHOIS →
0-6.ch is served from 2 IP addresses, mainly on AS16509 in United States. See Hosting →
Raw registry data for 0-6.ch. May be redacted by privacy services.
Requests of this client are not permitted. Please use https://www.nic.ch/whois/ for queries.
The first response from http://www.0-6.ch, before any redirect: caching, server and policy headers.
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with 0-6.ch. Data is collected independently from public sources and some figures are estimates, provided for information only.
Spam and malware blocklists for the site's IP and mail servers.
When the site first appeared, and what has changed since.
We record what changes from the next time this report is refreshed.
Found in public certificate transparency logs.
Searching the certificate transparency logs… This can take up to a minute.