zimuku.org

Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .

HTTP 404Family DNS blockedSSL: 95 days left8 years oldTranco #441711

One re-check per domain each UTC day.

35

zimuku.org was registered on 17 Oct 2018 via NameCheap, Inc. and the registry expiry is 17 Oct 2027. WHOIS data came from RDAP at https://rdap.publicinterestregistry.org/rdap/domain/zimuku.org.

zimuku.org publishes 2 nameservers. DNSSEC is not signed.

zimuku.org has 1 IPv4 address (144.168.61.193). The geolocation database places 144.168.61.193 in Los Angeles (Downtown Los Angeles), United States.

The TLS certificate from Sectigo Public Server Authentication CA DV R36 is valid and has 95 days left (TLS 1.2).

Tech detection named Nginx. The fingerprints ran on the homepage that was already downloaded.

Domain · RDAP/WHOIS

zimuku.org was registered on 17 Oct 2018 via NameCheap, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.publicinterestregistry.org/rdap/domain/zimuku.org.

Registeredsince 17 Oct 2018
Created17 October 2018
Updated22 September 2026
Expires17 October 2027
RegistrarNameCheap, Inc.
Statusclient transfer prohibited
Nameserversben.ns.cloudflare.com, pat.ns.cloudflare.com
DNSSECno
Sourcehttps://rdap.publicinterestregistry.org/rdap/domain/zimuku.org

zimuku.org 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 ben.ns.cloudflare.com is published for zimuku.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/zimuku.org.

Nameserver pat.ns.cloudflare.com is published for zimuku.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/zimuku.org.

DNS

zimuku.org has 1 address record, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.

A144.168.61.193
AAAA—
NSben.ns.cloudflare.com, pat.ns.cloudflare.com
MX—
SPFabsent
DMARCabsent
CAA—
Wildcardoff
DNSSECnot signed
Resolver1.1.1.1:53

IPv4 address 144.168.61.193 answers for zimuku.org at resolver 1.1.1.1:53.

Hosting and geo

zimuku.org is placed in Los Angeles (Downtown Los Angeles), United States by the local geolocation database (db-ip).

Address144.168.61.193
CountryUnited States
CityLos Angeles (Downtown Los Angeles)
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

The certificate for zimuku.org is valid, with 95 days left and 2 subject alternative names. Source: tls:443.

IssuerSectigo Public Server Authentication CA DV R36
Subjectzimuku.org
Valid from20 July 2026
Valid until3 February 2027
Days left95
SAN count2
ProtocolTLS 1.2
Sourcetls:443

Subject alternative names: www.zimuku.org, zimuku.org.

Tech stack

Tech detection checked the fetched homepage and named 1 product. Source: wappalyzergo.

  • Nginx · Web servers, Reverse proxies

Nginx is filed under Web servers, Reverse proxies.

On-page checks

The homepage returned HTTP 404 in 0 ms. The target title is 0 characters and the page has 0 H1 headings.

Status404
TTFB0 ms
Title length0 no
Quoted titlenone
Meta descriptionnone no
H1 count0
HSTSno no
CSPno
X-Frame-Options—
Robots meta—
Canonical—
Language—
Links0
Images0
Faviconno

The quoted title and meta description are measurements of the other site. They are not this page's title or description.

Security

Family DNS for zimuku.org is blocked, and URLhaus is clear. Source: family DNS and local lists.

Family DNSblocked
URLhausclear
UT1—
Web Risknot run
Sourcefamily DNS and local lists
HSTSno
CSPno

Cloudflare family DNS returned a block for zimuku.org. That resolver covers adult and malware names.

Google Web Risk did not run. No API key is configured, and this report does not invent a clean result from that service.

Score breakdown

Availability 10 of 25. DNS answer plus a homepage status in the 2xx or 3xx range.

TLS 20 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 0 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.

Change history

  • October 2026: geo city changed from empty to Los Angeles (Downtown Los Angeles).
  • October 2026: geo country changed from empty to United States.

Questions

Is zimuku.org safe?

Cloudflare family DNS returned a block for zimuku.org. That resolver covers adult and malware names.

Who hosts zimuku.org?

zimuku.org is placed in Los Angeles (Downtown Los Angeles), United States.

When does zimuku.org expire?

zimuku.org expires on 17 October 2027 according to https://rdap.publicinterestregistry.org/rdap/domain/zimuku.org.

Who owns zimuku.org?

The registry did not return a person or a company for zimuku.org. RDAP often redacts the registrant. The registrar on file is NameCheap, Inc..

Sources

  • RDAP source https://rdap.publicinterestregistry.org/rdap/domain/zimuku.org at 2026-10-30T15:26:02Z
  • DNS source 1.1.1.1:53 at 2026-10-30T15:26:02Z
  • TLS source tls:443 at 2026-10-30T15:26:02Z
  • HTTP source https://zimuku.org/ at 2026-10-30T15:26:02Z
  • Tech source wappalyzergo at 2026-10-30T15:26:02Z
  • Geo source db-ip at 2026-10-30T15:26:02Z
  • Safety source family DNS and local lists at 2026-10-30T15:26:02Z

Methodology

Related reports

No other indexable reports share this TLD, host, or registrar yet.

.org NameCheap, Inc.

Owner of this site?

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.

Removal policy

How to read this report

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.