kinobase.org
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 63 days left8 years oldTranco #76706
80
kinobase.org was registered on 3 Oct 2018 via GoDaddy.com, LLC and the registry expiry is 3 Oct 2027. WHOIS data came from RDAP at https://rdap.publicinterestregistry.org/rdap/domain/kinobase.org.
kinobase.org publishes 2 nameservers. DNSSEC is not signed.
kinobase.org has 1 IPv4 address (37.1.205.29). The geolocation database places 37.1.205.29 in Amsterdam, The Netherlands.
The TLS certificate from ZeroSSL RSA DV SSL CA 2 is valid and has 63 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named HSTS and Nginx. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for kinobase.org in the checks that ran.
Domain · RDAP/WHOIS
kinobase.org was registered on 3 Oct 2018 via GoDaddy.com, LLC. The registry returned 4 status values and 2 nameservers from https://rdap.publicinterestregistry.org/rdap/domain/kinobase.org.
| Registered | since 3 Oct 2018 |
|---|---|
| Created | 3 October 2018 |
| Updated | 12 August 2026 |
| Expires | 3 October 2027 |
| Registrar | GoDaddy.com, LLC |
| Status | client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited |
| Nameservers | ns49.domaincontrol.com, ns50.domaincontrol.com |
| DNSSEC | no |
| Source | https://rdap.publicinterestregistry.org/rdap/domain/kinobase.org |
kinobase.org carries the status "client delete prohibited". The registrar has asked the registry to refuse a delete. This is an EPP status on the domain object. It does not say the website is safe, and it does not name the person who registered it.
kinobase.org carries the status "client renew prohibited". The registrar has asked the registry to refuse a renewal. The expiry date still stands until a different status is set.
kinobase.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.
kinobase.org carries the status "client update prohibited". The registrar has asked the registry to refuse updates to the domain object. Contact and nameserver changes wait until the lock is lifted by the registrar of record.
Nameserver ns49.domaincontrol.com is published for kinobase.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/kinobase.org.
Nameserver ns50.domaincontrol.com is published for kinobase.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/kinobase.org.
DNS
kinobase.org has 1 address record, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 37.1.205.29 |
|---|---|
| AAAA | — |
| NS | ns49.domaincontrol.com, ns50.domaincontrol.com |
| MX | mail.kinobase.org (0) |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at kinobase.org is "v=spf1 mx -all".
The DMARC text record at _dmarc.kinobase.org is "v=DMARC1; p=none".
IPv4 address 37.1.205.29 answers for kinobase.org at resolver 1.1.1.1:53.
Mail exchanger mail.kinobase.org has preference 0.
Hosting and geo
kinobase.org is placed in Amsterdam, The Netherlands by the local geolocation database (db-ip).
| Address | 37.1.205.29 |
|---|---|
| Country | The Netherlands |
| City | Amsterdam |
| Source | db-ip |
SSL/TLS
The certificate for kinobase.org is valid, with 63 days left and 2 subject alternative names. Source: tls:443.
| Issuer | ZeroSSL RSA DV SSL CA 2 |
|---|---|
| Subject | kinobase.org |
| Valid from | 4 October 2026 |
| Valid until | 2 January 2027 |
| Days left | 63 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: kinobase.org, www.kinobase.org.
Tech stack
Tech detection checked the fetched homepage and named 2 products. Source: wappalyzergo.
- HSTS · Security
- Nginx · Web servers, Reverse proxies
HSTS is filed under Security.
Nginx is filed under Web servers, Reverse proxies.
On-page checks
The homepage returned HTTP 200 in 0 ms. The target title is 0 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 0 ms |
| Title length | 0 no |
| Quoted title | none |
| Meta description | none no |
| H1 count | 0 |
| HSTS | yes yes |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | — |
| Links | 0 |
| Images | 0 |
| Favicon | no |
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 kinobase.org 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 | yes |
| 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.
Score breakdown
Availability 25 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 10 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 5 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.
Change history
- October 2026: geo city changed from empty to Amsterdam.
- October 2026: geo country changed from empty to The Netherlands.
Questions
Is kinobase.org safe?
The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.
Who hosts kinobase.org?
kinobase.org is placed in Amsterdam, The Netherlands.
When does kinobase.org expire?
kinobase.org expires on 3 October 2027 according to https://rdap.publicinterestregistry.org/rdap/domain/kinobase.org.
Who owns kinobase.org?
The registry did not return a person or a company for kinobase.org. RDAP often redacts the registrant. The registrar on file is GoDaddy.com, LLC.
Sources
- RDAP source https://rdap.publicinterestregistry.org/rdap/domain/kinobase.org at 2026-10-30T15:02:42Z
- DNS source 1.1.1.1:53 at 2026-10-30T15:02:42Z
- TLS source tls:443 at 2026-10-30T15:02:42Z
- HTTP source https://kinobase.org/ at 2026-10-30T15:02:42Z
- Tech source wappalyzergo at 2026-10-30T15:02:42Z
- Geo source db-ip at 2026-10-30T15:02:42Z
- Safety source family DNS and local lists at 2026-10-30T15:02:42Z
Related reports
No other indexable reports share this TLD, host, or registrar yet.
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.
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.