kurakura.xyz
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafe1 year old
35
kurakura.xyz was registered on 27 Apr 2025 via CommuniGal Communication Ltd. and the registry expiry is 27 Apr 2027. WHOIS data came from RDAP at https://rdap.centralnic.com/xyz/domain/kurakura.xyz.
kurakura.xyz publishes 2 nameservers. DNSSEC is not signed.
kurakura.xyz has 1 IPv4 address (103.224.182.213). The geolocation database places 103.224.182.213 in San Diego, United States.
No safety warning was recorded for kurakura.xyz in the checks that ran.
Domain · RDAP/WHOIS
kurakura.xyz was registered on 27 Apr 2025 via CommuniGal Communication Ltd.. The registry returned 1 status value and 2 nameservers from https://rdap.centralnic.com/xyz/domain/kurakura.xyz.
| Registered | since 27 Apr 2025 |
|---|---|
| Created | 27 April 2025 |
| Updated | 5 May 2026 |
| Expires | 27 April 2027 |
| Registrar | CommuniGal Communication Ltd. |
| Status | client transfer prohibited |
| Nameservers | ns15.abovedomains.com, ns16.abovedomains.com |
| DNSSEC | no |
| Source | https://rdap.centralnic.com/xyz/domain/kurakura.xyz |
kurakura.xyz 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 ns15.abovedomains.com is published for kurakura.xyz in the registration record from https://rdap.centralnic.com/xyz/domain/kurakura.xyz.
Nameserver ns16.abovedomains.com is published for kurakura.xyz in the registration record from https://rdap.centralnic.com/xyz/domain/kurakura.xyz.
DNS
kurakura.xyz has 1 address record, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 103.224.182.213 |
|---|---|
| AAAA | — |
| NS | ns15.abovedomains.com, ns16.abovedomains.com |
| MX | park-mx.above.com (10) |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at kurakura.xyz is "v=spf1 ip6:fdcf:abda:4154::/48 -all".
IPv4 address 103.224.182.213 answers for kurakura.xyz at resolver 1.1.1.1:53.
Mail exchanger park-mx.above.com has preference 10.
A random label under kurakura.xyz also resolved, which means wildcard DNS is on.
Hosting and geo
kurakura.xyz is placed in San Diego, United States by the local geolocation database (db-ip).
| Address | 103.224.182.213 |
|---|---|
| Country | United States |
| City | San Diego |
| Source | db-ip |
SSL/TLS
No TLS certificate was read for kurakura.xyz on port 443.
| Available | no |
|---|---|
| Source | tls:443 |
dial tcp 103.224.182.213:443: i/o timeout
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 |
|---|
context deadline exceeded
Security
Family DNS for kurakura.xyz 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 5 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 San Diego.
- October 2026: geo country changed from empty to United States.
Questions
Is kurakura.xyz 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 kurakura.xyz?
kurakura.xyz is placed in San Diego, United States.
When does kurakura.xyz expire?
kurakura.xyz expires on 27 April 2027 according to https://rdap.centralnic.com/xyz/domain/kurakura.xyz.
Who owns kurakura.xyz?
The registry did not return a person or a company for kurakura.xyz. RDAP often redacts the registrant. The registrar on file is CommuniGal Communication Ltd..
Sources
- RDAP source https://rdap.centralnic.com/xyz/domain/kurakura.xyz at 2026-10-30T15:48:07Z
- DNS source 1.1.1.1:53 at 2026-10-30T15:48:07Z
- TLS source tls:443 at 2026-10-30T15:48:07Z
- HTTP source https://kurakura.xyz/ at 2026-10-30T15:48:07Z
- Tech source not available at 2026-10-30T15:48:07Z
- Geo source db-ip at 2026-10-30T15:48:07Z
- Safety source family DNS and local lists at 2026-10-30T15:48:07Z
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.