ting56.cc

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

Online · 200Family DNS blockedSSL: 62 days left9 years old

One re-check per domain each UTC day.

55

ting56.cc was registered on 16 Dec 2016 via Gname.com Pte. Ltd. and the registry expiry is 16 Dec 2026. WHOIS data came from RDAP at https://tld-rdap.verisign.com/cc/v1/domain/ting56.cc.

ting56.cc publishes 2 nameservers. DNSSEC is not signed.

ting56.cc has 1 IPv4 address (168.76.120.210). The geolocation database places 168.76.120.210 in Bloemfontein, South Africa.

The TLS certificate from YR1 is valid and has 62 days left (TLS 1.3). The homepage answered HTTP 200.

Tech detection named Cloudflare, HSTS, HTTP/3 and jQuery. The fingerprints ran on the homepage that was already downloaded.

Domain · RDAP/WHOIS

ting56.cc was registered on 16 Dec 2016 via Gname.com Pte. Ltd.. The registry returned 1 status value and 2 nameservers from https://tld-rdap.verisign.com/cc/v1/domain/ting56.cc.

Registeredsince 16 Dec 2016
Created16 December 2016
Updated17 November 2025
Expires16 December 2026
RegistrarGname.com Pte. Ltd.
Statusclient transfer prohibited
Nameserversns1.dnsip.com, ns2.dnsip.com
DNSSECno
Sourcehttps://tld-rdap.verisign.com/cc/v1/domain/ting56.cc

ting56.cc 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 ns1.dnsip.com is published for ting56.cc in the registration record from https://tld-rdap.verisign.com/cc/v1/domain/ting56.cc.

Nameserver ns2.dnsip.com is published for ting56.cc in the registration record from https://tld-rdap.verisign.com/cc/v1/domain/ting56.cc.

DNS

ting56.cc has 1 address record, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.

A168.76.120.210
AAAA—
NSns1.dnsip.com, ns2.dnsip.com
MX—
SPFabsent
DMARCabsent
CAA—
Wildcardoff
DNSSECnot signed
Resolver1.1.1.1:53

IPv4 address 168.76.120.210 answers for ting56.cc at resolver 1.1.1.1:53.

Hosting and geo

ting56.cc is placed in Bloemfontein, South Africa by the local geolocation database (db-ip).

Address168.76.120.210
CountrySouth Africa
CityBloemfontein
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

The certificate for ting56.cc is valid, with 62 days left and 3 subject alternative names. Source: tls:443.

IssuerYR1
Subjectm.ting56.cc
Valid from4 October 2026
Valid until2 January 2027
Days left62
SAN count3
ProtocolTLS 1.3
Sourcetls:443

Subject alternative names: m.ting56.cc, ting56.cc, www.ting56.cc.

Tech stack

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

  • Cloudflare · CDN
  • HSTS · Security
  • HTTP/3 · Miscellaneous
  • jQuery · JavaScript libraries

Cloudflare is filed under CDN.

HSTS is filed under Security.

HTTP/3 is filed under Miscellaneous.

jQuery is filed under JavaScript libraries.

On-page checks

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

Status200
TTFB227 ms
Title length4 yes
Quoted title"韩修影院"
Meta description"韩修影院为您提供最新『热映电影、热门电视剧、热播综艺、动漫视频』在线观看,每天第一时间更新,给您更好的视频观看体验,手机看片首选韩修影院。" yes
H1 count0
HSTSyes yes
CSPno
X-Frame-Options—
Robots metanoarchive
Canonical—
Language—
Links18
Images15
Faviconno

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 ting56.cc is blocked, and URLhaus is clear. Source: family DNS and local lists.

Family DNSblocked
URLhausclear
UT1—
Web Risknot run
Sourcefamily DNS and local lists
HSTSyes
CSPno

Cloudflare family DNS returned a block for ting56.cc. That resolver covers adult and malware names.

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 5 of 15. HSTS, CSP, and X-Frame-Options or CSP frame-ancestors.

Safety lists 0 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 Bloemfontein.
  • October 2026: geo country changed from empty to South Africa.

Questions

Is ting56.cc safe?

Cloudflare family DNS returned a block for ting56.cc. That resolver covers adult and malware names.

Who hosts ting56.cc?

ting56.cc is placed in Bloemfontein, South Africa.

When does ting56.cc expire?

ting56.cc expires on 16 December 2026 according to https://tld-rdap.verisign.com/cc/v1/domain/ting56.cc.

Who owns ting56.cc?

The registry did not return a person or a company for ting56.cc. RDAP often redacts the registrant. The registrar on file is Gname.com Pte. Ltd..

Sources

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

Methodology

Related reports

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

.cc Gname.com Pte. 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.