hanindisk.com

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

Online · 200SafeSSL: 136 days left18 years oldTranco #324166

One re-check per domain each UTC day.

65

hanindisk.com was registered on 3 Feb 2008 via Namescout Ltd and the registry expiry is 3 Feb 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/hanindisk.com.

hanindisk.com publishes 4 nameservers. DNSSEC is not signed.

hanindisk.com has 1 IPv4 address (64.71.153.93). The geolocation database places 64.71.153.93 in Kirkland (Moss Bay), United States.

The TLS certificate from Sectigo Public Server Authentication CA DV R36 is valid and has 136 days left (TLS 1.2). The homepage answered HTTP 200.

Tech detection named Apache HTTP Server, CentOS, FancyBox, Google Analytics, Google Sign-in, PHP, bxSlider and jQuery. The fingerprints ran on the homepage that was already downloaded.

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

Domain · RDAP/WHOIS

hanindisk.com was registered on 3 Feb 2008 via Namescout Ltd. The registry returned 2 status values and 4 nameservers from https://rdap.verisign.com/com/v1/domain/hanindisk.com.

Registeredsince 3 Feb 2008
Created3 February 2008
Updated4 February 2026
Expires3 February 2027
RegistrarNamescout Ltd
Statusclient transfer prohibited, client update prohibited
Nameserversns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e4.googledomains.com
DNSSECno
Sourcehttps://rdap.verisign.com/com/v1/domain/hanindisk.com

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

hanindisk.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 ns-cloud-e1.googledomains.com is published for hanindisk.com in the registration record from https://rdap.verisign.com/com/v1/domain/hanindisk.com.

Nameserver ns-cloud-e2.googledomains.com is published for hanindisk.com in the registration record from https://rdap.verisign.com/com/v1/domain/hanindisk.com.

Nameserver ns-cloud-e3.googledomains.com is published for hanindisk.com in the registration record from https://rdap.verisign.com/com/v1/domain/hanindisk.com.

Nameserver ns-cloud-e4.googledomains.com is published for hanindisk.com in the registration record from https://rdap.verisign.com/com/v1/domain/hanindisk.com.

DNS

hanindisk.com has 1 address record, 5 mail exchangers and 4 nameservers, measured at 1.1.1.1:53.

A64.71.153.93
AAAA—
NSns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e4.googledomains.com
MXaspmx.l.google.com (1) Google, alt1.aspmx.l.google.com (5) Google, alt2.aspmx.l.google.com (5) Google, aspmx2.googlemail.com (10) Google, aspmx3.googlemail.com (10) Google
SPFabsent
DMARCabsent
CAA—
Wildcardon
DNSSECnot signed
Resolver1.1.1.1:53

IPv4 address 64.71.153.93 answers for hanindisk.com at resolver 1.1.1.1:53.

Mail exchanger aspmx.l.google.com has preference 1. The host is recognised as Google.

Mail exchanger alt1.aspmx.l.google.com has preference 5. The host is recognised as Google.

Mail exchanger alt2.aspmx.l.google.com has preference 5. The host is recognised as Google.

Mail exchanger aspmx2.googlemail.com has preference 10. The host is recognised as Google.

Mail exchanger aspmx3.googlemail.com has preference 10. The host is recognised as Google.

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

Hosting and geo

hanindisk.com is placed in Kirkland (Moss Bay), United States by the local geolocation database (db-ip).

Address64.71.153.93
CountryUnited States
CityKirkland (Moss Bay)
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

The certificate for hanindisk.com is valid, with 136 days left and 2 subject alternative names. Source: tls:443.

IssuerSectigo Public Server Authentication CA DV R36
Subject*.hanindisk.com
Valid from30 August 2026
Valid until16 March 2027
Days left136
SAN count2
ProtocolTLS 1.2
Sourcetls:443

Subject alternative names: *.hanindisk.com, hanindisk.com.

Tech stack

Tech detection checked the fetched homepage and named 8 products. Source: wappalyzergo.

  • Apache HTTP Server · Web servers
  • CentOS · Operating systems
  • FancyBox · JavaScript libraries
  • Google Analytics · Analytics
  • Google Sign-in · Authentication
  • PHP · Programming languages
  • bxSlider · Photo galleries, JavaScript libraries
  • jQuery · JavaScript libraries

Apache HTTP Server is filed under Web servers.

CentOS is filed under Operating systems.

FancyBox is filed under JavaScript libraries.

Google Analytics is filed under Analytics.

Google Sign-in is filed under Authentication.

PHP is filed under Programming languages.

bxSlider is filed under Photo galleries, JavaScript libraries.

jQuery is filed under JavaScript libraries.

On-page checks

The homepage returned HTTP 200 in 234 ms. The target title is 34 characters and the page has 0 H1 headings.

Status200
TTFB234 ms
Title length34 yes
Quoted title"한인디스크 | 미주 한인 웹하드 · 한국 방송·드라마 다시보기"
Meta description"한인디스크는 미국·캐나다 등 해외 한인을 위한 미주 웹하드 서비스입니다. 한국 방송, 드라마, 예능, 영화 등 다양한 콘텐츠를 편리하게 이용할 수 있습니다." yes
H1 count0
HSTSno no
CSPno
X-Frame-Options—
Robots meta—
Canonical—
Language—
Links134
Images68
Faviconyes

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 hanindisk.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 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 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 Kirkland (Moss Bay).
  • October 2026: geo country changed from empty to United States.

Questions

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

hanindisk.com is placed in Kirkland (Moss Bay), United States.

When does hanindisk.com expire?

hanindisk.com expires on 3 February 2027 according to https://rdap.verisign.com/com/v1/domain/hanindisk.com.

Who owns hanindisk.com?

The registry did not return a person or a company for hanindisk.com. RDAP often redacts the registrant. The registrar on file is Namescout Ltd.

Sources

  • RDAP source https://rdap.verisign.com/com/v1/domain/hanindisk.com at 2026-10-30T13:57:02Z
  • DNS source 1.1.1.1:53 at 2026-10-30T13:57:02Z
  • TLS source tls:443 at 2026-10-30T13:57:02Z
  • HTTP source https://hanindisk.com/ at 2026-10-30T13:57:02Z
  • Tech source wappalyzergo at 2026-10-30T13:57:02Z
  • Geo source db-ip at 2026-10-30T13:57:02Z
  • Safety source family DNS and local lists at 2026-10-30T13:57:02Z

Methodology

Related reports

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

.com Namescout Ltd

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.