wubisheng.cc

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

Online · 200SafeSSL: 86 days left8 years old

One re-check per domain each UTC day.

75

wubisheng.cc was registered on 5 Sep 2018 via Alibaba Cloud Computing (Beijing) Co., Ltd. and the registry expiry is 5 Sep 2029. WHOIS data came from RDAP at https://tld-rdap.verisign.com/cc/v1/domain/wubisheng.cc.

wubisheng.cc publishes 2 nameservers. DNSSEC is signed.

wubisheng.cc has 1 IPv4 address (45.114.125.3). The geolocation database places 45.114.125.3 in Hong Kong, Hong Kong.

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

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

No safety warning was recorded for wubisheng.cc in the checks that ran.

Domain · RDAP/WHOIS

wubisheng.cc was registered on 5 Sep 2018 via Alibaba Cloud Computing (Beijing) Co., Ltd.. The registry returned 1 status value and 2 nameservers from https://tld-rdap.verisign.com/cc/v1/domain/wubisheng.cc.

Registeredsince 5 Sep 2018
Created5 September 2018
Updated7 September 2026
Expires5 September 2029
RegistrarAlibaba Cloud Computing (Beijing) Co., Ltd.
Statusactive
Nameserversannabel.ns.cloudflare.com, remy.ns.cloudflare.com
DNSSECyes
Sourcehttps://tld-rdap.verisign.com/cc/v1/domain/wubisheng.cc

Nameserver annabel.ns.cloudflare.com is published for wubisheng.cc in the registration record from https://tld-rdap.verisign.com/cc/v1/domain/wubisheng.cc.

Nameserver remy.ns.cloudflare.com is published for wubisheng.cc in the registration record from https://tld-rdap.verisign.com/cc/v1/domain/wubisheng.cc.

DNS

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

A45.114.125.3
AAAA—
NSannabel.ns.cloudflare.com, remy.ns.cloudflare.com
MX—
SPFabsent
DMARCabsent
CAA—
Wildcardoff
DNSSECsigned
Resolver1.1.1.1:53

IPv4 address 45.114.125.3 answers for wubisheng.cc at resolver 1.1.1.1:53.

Hosting and geo

wubisheng.cc is placed in Hong Kong, Hong Kong by the local geolocation database (db-ip).

Address45.114.125.3
CountryHong Kong
CityHong Kong
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

The certificate for wubisheng.cc is valid, with 86 days left and 5 subject alternative names. Source: tls:443.

IssuerYR1
Subjectwubisheng.cc
Valid from28 October 2026
Valid until26 January 2027
Days left86
SAN count5
ProtocolTLS 1.3
Sourcetls:443

Subject alternative names: m.wubisheng.cc, wubisheng.cc, wubisheng.net, www.wubisheng.cc, www.wubisheng.net.

Tech stack

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

  • Google AdSense · Advertising
  • HSTS · Security
  • HTTP/3 · Miscellaneous
  • Nginx · Web servers, Reverse proxies

Google AdSense is filed under Advertising.

HSTS is filed under Security.

HTTP/3 is filed under Miscellaneous.

Nginx is filed under Web servers, Reverse proxies.

On-page checks

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

Status200
TTFB963 ms
Title length11 yes
Quoted title"必胜影视园地_必胜园地"
Meta description"必胜影视园地面向母语为汉语的韩语爱好者,提供韩语学习与交流的空间。" yes
H1 count0
HSTSyes yes
CSPno
X-Frame-Options—
Robots meta—
Canonical—
Language—
Links94
Images1
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 wubisheng.cc is clear, and URLhaus is clear. Source: family DNS and local lists.

Family DNSclear
URLhausclear
UT1—
Web Risknot run
Sourcefamily DNS and local lists
HSTSyes
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 5 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 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 Hong Kong.
  • October 2026: geo country changed from empty to Hong Kong.

Questions

Is wubisheng.cc 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 wubisheng.cc?

wubisheng.cc is placed in Hong Kong, Hong Kong.

When does wubisheng.cc expire?

wubisheng.cc expires on 5 September 2029 according to https://tld-rdap.verisign.com/cc/v1/domain/wubisheng.cc.

Who owns wubisheng.cc?

The registry did not return a person or a company for wubisheng.cc. RDAP often redacts the registrant. The registrar on file is Alibaba Cloud Computing (Beijing) Co., Ltd..

Sources

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

Methodology

Related reports

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

.cc Alibaba Cloud Computing (Beijing) Co., 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.