go4kora.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafeSSL: -35 days left8 years old
30
go4kora.com was registered on 6 Mar 2018 via Name.com, Inc. and the registry expiry is 6 Mar 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/go4kora.com.
go4kora.com publishes 2 nameservers. DNSSEC is not signed.
go4kora.com has 1 IPv4 address (54.235.210.28). The geolocation database places 54.235.210.28 in Ashburn, United States.
The TLS certificate from YE1 is not valid (TLS 1.3).
No safety warning was recorded for go4kora.com in the checks that ran.
Domain · RDAP/WHOIS
go4kora.com was registered on 6 Mar 2018 via Name.com, Inc.. The registry returned 4 status values and 2 nameservers from https://rdap.verisign.com/com/v1/domain/go4kora.com.
| Registered | since 6 Mar 2018 |
|---|---|
| Created | 6 March 2018 |
| Updated | 26 June 2026 |
| Expires | 6 March 2027 |
| Registrar | Name.com, Inc. |
| Status | client transfer prohibited, server delete prohibited, server transfer prohibited, server update prohibited |
| Nameservers | ns1.seizedservers.com, ns2.seizedservers.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/go4kora.com |
go4kora.com 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.
go4kora.com carries the status "server delete prohibited". The registry itself is refusing deletes. This lock is not one the registrar can clear alone.
go4kora.com carries the status "server transfer prohibited". The registry itself is refusing transfers. The name stays at the current registrar while the status remains.
go4kora.com carries the status "server update prohibited". The registry itself is refusing updates to the domain object.
Nameserver ns1.seizedservers.com is published for go4kora.com in the registration record from https://rdap.verisign.com/com/v1/domain/go4kora.com.
Nameserver ns2.seizedservers.com is published for go4kora.com in the registration record from https://rdap.verisign.com/com/v1/domain/go4kora.com.
DNS
go4kora.com has 1 address record, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 54.235.210.28 |
|---|---|
| AAAA | — |
| NS | ns1.seizedservers.com, ns2.seizedservers.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 54.235.210.28 answers for go4kora.com at resolver 1.1.1.1:53.
A random label under go4kora.com also resolved, which means wildcard DNS is on.
Hosting and geo
go4kora.com is placed in Ashburn, United States by the local geolocation database (db-ip).
| Address | 54.235.210.28 |
|---|---|
| Country | United States |
| City | Ashburn |
| Source | db-ip |
SSL/TLS
The certificate for go4kora.com is not valid, with -35 days left and 1 subject alternative name. Source: tls:443.
| Issuer | YE1 |
|---|---|
| Subject | go4kora.com |
| Valid from | 27 June 2026 |
| Valid until | 25 September 2026 |
| Days left | -35 |
| SAN count | 1 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: go4kora.com.
Validation result: certificate did not validate
Tech stack
Tech detection did not run.
| Checked | no |
|---|---|
| Source | wappalyzergo |
On-page checks
The homepage fetch did not return a status code.
| Status | none |
|---|
Get "https://go4kora.com/": tls: failed to verify certificate: x509: certificate has expired or is not yet valid: current time 2026-10-30T13:56:23Z is after 2026-09-25T13:24:08Z
Security
Family DNS for go4kora.com 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 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.
Change history
- October 2026: geo city changed from empty to Ashburn.
- October 2026: geo country changed from empty to United States.
Questions
Is go4kora.com 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.com?
go4kora.com is placed in Ashburn, United States.
When does go4kora.com expire?
go4kora.com expires on 6 March 2027 according to https://rdap.verisign.com/com/v1/domain/go4kora.com.
Who owns go4kora.com?
The registry did not return a person or a company for go4kora.com. RDAP often redacts the registrant. The registrar on file is Name.com, Inc..
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/go4kora.com at 2026-10-30T13:56:23Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:56:23Z
- TLS source tls:443 at 2026-10-30T13:56:23Z
- HTTP source https://go4kora.com/ at 2026-10-30T13:56:23Z
- Tech source not available at 2026-10-30T13:56:23Z
- Geo source db-ip at 2026-10-30T13:56:23Z
- Safety source family DNS and local lists at 2026-10-30T13:56:23Z
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.