uukanshu.com

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

OfflineSafe14 years oldTranco #939965

One re-check per domain each UTC day.

30

uukanshu.com was registered on 19 Oct 2012 via GoDaddy.com, LLC and the registry expiry is 19 Oct 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/uukanshu.com.

uukanshu.com has 1 IPv4 address (127.0.0.1) and 1 IPv6 address (::1).

No safety warning was recorded for uukanshu.com in the checks that ran.

Domain · RDAP/WHOIS

uukanshu.com was registered on 19 Oct 2012 via GoDaddy.com, LLC. The registry returned 4 status values and 4 nameservers from https://rdap.verisign.com/com/v1/domain/uukanshu.com.

Registeredsince 19 Oct 2012
Created19 October 2012
Updated30 March 2024
Expires19 October 2027
RegistrarGoDaddy.com, LLC
Statusclient delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited
Nameserverspns101.cloudns.net, pns102.cloudns.net, pns103.cloudns.net, pns104.cloudns.net
DNSSECno
Sourcehttps://rdap.verisign.com/com/v1/domain/uukanshu.com

uukanshu.com 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.

uukanshu.com 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.

uukanshu.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.

uukanshu.com 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 pns101.cloudns.net is published for uukanshu.com in the registration record from https://rdap.verisign.com/com/v1/domain/uukanshu.com.

Nameserver pns102.cloudns.net is published for uukanshu.com in the registration record from https://rdap.verisign.com/com/v1/domain/uukanshu.com.

Nameserver pns103.cloudns.net is published for uukanshu.com in the registration record from https://rdap.verisign.com/com/v1/domain/uukanshu.com.

Nameserver pns104.cloudns.net is published for uukanshu.com in the registration record from https://rdap.verisign.com/com/v1/domain/uukanshu.com.

DNS

uukanshu.com has 2 address records, 1 mail exchanger and 0 nameservers, measured at 1.1.1.1:53.

A127.0.0.1
AAAA::1
NS—
MXlocalhost (0)
SPFabsent
DMARCabsent
CAA—
Wildcardon
DNSSECnot signed
Resolver1.1.1.1:53

IPv4 address 127.0.0.1 answers for uukanshu.com at resolver 1.1.1.1:53.

IPv6 address ::1 answers for uukanshu.com at resolver 1.1.1.1:53.

Mail exchanger localhost has preference 0.

A random label under uukanshu.com also resolved, which means wildcard DNS is on.

Hosting and geo

Geolocation for uukanshu.com is not available. No local city or ASN database is installed, so this report does not guess a country.

Geolocationnot available
Sourcemaxmind

SSL/TLS

No TLS certificate was read for uukanshu.com on port 443.

Availableno
Sourcetls:443

dial tcp [::1]:443: connect: connection refused

Tech stack

Tech detection did not run.

Checkedno
Sourcewappalyzergo

On-page checks

The homepage fetch did not return a status code.

Statusnone

Get "https://uukanshu.com/": dial tcp [::1]:443: connect: connection refused

Security

Family DNS for uukanshu.com is clear, and URLhaus is clear. Source: family DNS and local lists.

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

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

First checked on 30 October 2026; changes will appear here.

Questions

Is uukanshu.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 uukanshu.com?

The host network is not available without a local geolocation database.

When does uukanshu.com expire?

uukanshu.com expires on 19 October 2027 according to https://rdap.verisign.com/com/v1/domain/uukanshu.com.

Who owns uukanshu.com?

The registry did not return a person or a company for uukanshu.com. RDAP often redacts the registrant. The registrar on file is GoDaddy.com, LLC.

Sources

  • RDAP source https://rdap.verisign.com/com/v1/domain/uukanshu.com at 2026-10-30T14:18:33Z
  • DNS source 1.1.1.1:53 at 2026-10-30T14:18:33Z
  • TLS source tls:443 at 2026-10-30T14:18:33Z
  • HTTP source https://uukanshu.com/ at 2026-10-30T14:18:33Z
  • Tech source not available at 2026-10-30T14:18:33Z
  • Geo source db-ip at 2026-10-30T14:18:33Z
  • Safety source family DNS and local lists at 2026-10-30T14:18:33Z

Methodology

Related reports

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

.com GoDaddy.com, LLC

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.