myzuka.club
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
20
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
20
myzuka.club was registered on 12 Nov 2017 via TLD Registrar Solutions Ltd. and the registry expiry is 12 Nov 2026. WHOIS data came from RDAP at https://rdap.nic.club/domain/myzuka.club.
No safety warning was recorded for myzuka.club in the checks that ran.
myzuka.club was registered on 12 Nov 2017 via TLD Registrar Solutions Ltd.. The registry returned 1 status value and 2 nameservers from https://rdap.nic.club/domain/myzuka.club.
| Registered | since 12 Nov 2017 |
|---|---|
| Created | 12 November 2017 |
| Updated | 26 November 2025 |
| Expires | 12 November 2026 |
| Registrar | TLD Registrar Solutions Ltd. |
| Status | client transfer prohibited |
| Nameservers | harlan.ns.cloudflare.com, veronica.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.nic.club/domain/myzuka.club |
myzuka.club carries the status "client transfer prohibited". The registrar has asked the registry to refuse a transfer to another registrar. The status is a lock on the domain object. It is not evidence about the content of the site.
Nameserver harlan.ns.cloudflare.com is published for myzuka.club in the registration record from https://rdap.nic.club/domain/myzuka.club.
Nameserver veronica.ns.cloudflare.com is published for myzuka.club in the registration record from https://rdap.nic.club/domain/myzuka.club.
myzuka.club has 0 address records, 0 mail exchangers and 0 nameservers, measured at 1.1.1.1:53.
| A | — |
|---|---|
| AAAA | — |
| NS | — |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
Geolocation for myzuka.club is not available. No local city or ASN database is installed, so this report does not guess a country.
| Geolocation | not available |
|---|---|
| Source | maxmind |
No TLS certificate was read for myzuka.club on port 443.
| Available | no |
|---|---|
| Source | tls:443 |
dial tcp: lookup myzuka.club on 46.38.225.230:53: server misbehaving
Tech detection did not run.
| Checked | no |
|---|---|
| Source | wappalyzergo |
The homepage fetch did not return a status code.
| Status | none |
|---|
Get "https://myzuka.club/": dial tcp: lookup myzuka.club on 46.38.225.230:53: server misbehaving
Family DNS for myzuka.club is clear, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | clear |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | no |
| CSP | no |
Google Web Risk did not run. No API key is configured, and this report does not invent a clean result from that service.
Availability 0 of 25. DNS answer plus a homepage status in the 2xx or 3xx range.
TLS 0 of 20. A valid certificate, with extra points when it has at least 14 days left.
DNS hygiene 0 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 0 of 15. HSTS, CSP, and X-Frame-Options or CSP frame-ancestors.
Safety lists 15 of 15. Points only when the checks ran and came back clean. Unknown is not clean.
Domain age 5 of 5. Five points at one year, two points at 30 days.
The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.
The host network is not available without a local geolocation database.
myzuka.club expires on 12 November 2026 according to https://rdap.nic.club/domain/myzuka.club.
The registry did not return a person or a company for myzuka.club. RDAP often redacts the registrant. The registrar on file is TLD Registrar Solutions Ltd..
No other indexable reports share this TLD, host, or registrar yet.
Ask for a correction or for the report to be removed from search. Public DNS facts stay on the page. An optional badge is not inserted for you.
The sentences under each heading are filled from the latest snapshot. If a collector had nothing to say, that sentence is left out. The target site's own title and meta description, when shown, are quoted as measurements. They are not this page's title. Change history only lists a difference between two snapshots, so the first check starts the clock and later edits are the history. A malware blocklist is the only reason the homepage body is skipped. That fact stays on the report. It does not by itself drop the page from the sitemap or from related-report links.