go4kora.info
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
HTTP 405SafeSSL: 66 days left1 year old
50
go4kora.info was registered on 21 May 2025 via Name.com, Inc. and the registry expiry is 21 May 2027. WHOIS data came from RDAP at https://rdap.identitydigital.services/rdap/domain/go4kora.info.
go4kora.info publishes 4 nameservers. DNSSEC is not signed.
go4kora.info has 1 IPv4 address (91.195.240.94). The geolocation database places 91.195.240.94 in Cologne (Innenstadt, Cologne), Germany.
The TLS certificate from Encryption Everywhere DV TLS CA - G2 is valid and has 66 days left (TLS 1.3).
No safety warning was recorded for go4kora.info in the checks that ran.
Domain · RDAP/WHOIS
go4kora.info was registered on 21 May 2025 via Name.com, Inc.. The registry returned 1 status value and 4 nameservers from https://rdap.identitydigital.services/rdap/domain/go4kora.info.
| Registered | since 21 May 2025 |
|---|---|
| Created | 21 May 2025 |
| Updated | 11 August 2026 |
| Expires | 21 May 2027 |
| Registrar | Name.com, Inc. |
| Status | client transfer prohibited |
| Nameservers | ns4lrt.name.com, ns3bgq.name.com, ns2qvz.name.com, ns1mtw.name.com |
| DNSSEC | no |
| Source | https://rdap.identitydigital.services/rdap/domain/go4kora.info |
go4kora.info 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 ns4lrt.name.com is published for go4kora.info in the registration record from https://rdap.identitydigital.services/rdap/domain/go4kora.info.
Nameserver ns3bgq.name.com is published for go4kora.info in the registration record from https://rdap.identitydigital.services/rdap/domain/go4kora.info.
Nameserver ns2qvz.name.com is published for go4kora.info in the registration record from https://rdap.identitydigital.services/rdap/domain/go4kora.info.
Nameserver ns1mtw.name.com is published for go4kora.info in the registration record from https://rdap.identitydigital.services/rdap/domain/go4kora.info.
DNS
go4kora.info has 1 address record, 0 mail exchangers and 4 nameservers, measured at 1.1.1.1:53.
| A | 91.195.240.94 |
|---|---|
| AAAA | — |
| NS | ns1mtw.name.com, ns2qvz.name.com, ns3bgq.name.com, ns4lrt.name.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 91.195.240.94 answers for go4kora.info at resolver 1.1.1.1:53.
A random label under go4kora.info also resolved, which means wildcard DNS is on.
Hosting and geo
go4kora.info is placed in Cologne (Innenstadt, Cologne), Germany by the local geolocation database (db-ip).
| Address | 91.195.240.94 |
|---|---|
| Country | Germany |
| City | Cologne (Innenstadt, Cologne) |
| Source | db-ip |
SSL/TLS
The certificate for go4kora.info is valid, with 66 days left and 1 subject alternative name. Source: tls:443.
| Issuer | Encryption Everywhere DV TLS CA - G2 |
|---|---|
| Subject | go4kora.info |
| Valid from | 8 October 2026 |
| Valid until | 5 January 2027 |
| Days left | 66 |
| SAN count | 1 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: go4kora.info.
Tech stack
Tech detection checked the fetched homepage and named 0 products. Source: wappalyzergo.
The fingerprint set matched no product. That is a result, not a skipped check.
On-page checks
The homepage returned HTTP 405 in 0 ms. The target title is 0 characters and the page has 0 H1 headings.
| Status | 405 |
|---|---|
| TTFB | 0 ms |
| Title length | 0 no |
| Quoted title | none |
| Meta description | none no |
| H1 count | 0 |
| HSTS | no no |
| 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 go4kora.info 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.
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 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 Cologne (Innenstadt, Cologne).
- October 2026: geo country changed from empty to Germany.
Questions
Is go4kora.info 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 go4kora.info?
go4kora.info is placed in Cologne (Innenstadt, Cologne), Germany.
When does go4kora.info expire?
go4kora.info expires on 21 May 2027 according to https://rdap.identitydigital.services/rdap/domain/go4kora.info.
Who owns go4kora.info?
The registry did not return a person or a company for go4kora.info. RDAP often redacts the registrant. The registrar on file is Name.com, Inc..
Sources
- RDAP source https://rdap.identitydigital.services/rdap/domain/go4kora.info at 2026-10-30T14:32:54Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:32:54Z
- TLS source tls:443 at 2026-10-30T14:32:54Z
- HTTP source https://go4kora.info/ at 2026-10-30T14:32:54Z
- Tech source wappalyzergo at 2026-10-30T14:32:54Z
- Geo source db-ip at 2026-10-30T14:32:54Z
- Safety source family DNS and local lists at 2026-10-30T14:32:54Z
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.