Skip to content
https://people.cn

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
77
GRADE
C
FIX
2
REVIEW
4
PASS
3
INFO
0
Probed from Singapore, Singapore
301 Moved Permanently
Checks
9
3 PASS 4 REVIEW 2 FIX
D
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
FIX
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 301 Expected: 301 redirect to HTTPS

www / non-www

200https://www.people.cn/
200https://people.cn/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://people.cn/ → http://www.people.com.cn/

HTTP version does not redirect to HTTPS

D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

B
Redirect Chain
1 redirect(s), 1523 ms total
REVIEW
1 redirect(s), 1523 ms total
Info::
Single redirect
Got: https://people.cn → https://www.people.cn/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1523 ms total
Got: 1523 ms

https://people.cn

811 ms · HTTP/1.1

301

https://www.people.cn/

712 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://people.cn301811 msHTTP/1.1RMW-WEB/260415
2https://www.people.cn/200712 msHTTP/1.1wswaf

See the visual redirect chain in the HTTP Probe tab →

C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B
HTTP Probe Timing
Total 843 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
90 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
250 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
253 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
843 ms
Total Time Total request time from DNS lookup through full response.
843 ms

Connection waterfall

DNS Lookup 90 ms TCP Connect 250 ms TLS Handshake 253 ms Server Processing 250 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
228 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

228
days left
0d 30d 60d 90d+

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • Enable DNSSEC on your domain for DNS spoofing protection
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+
DNS Records
1 A records, 168 ms lookup
PASS
1 A records, 168 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 49.7.133.88
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
5 nameserver(s) configured
Got: ns3.people.cn, ns5.people.cn, ns4.people.cn, ns2.people.cn, ns1.people.cn
Info::
2 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 168 ms
Got: 168 ms
A49.7.133.88
AAAA—
CNAME—
NSns3.people.cn, ns5.people.cn, ns4.people.cn, ns2.people.cn, ns1.people.cn
MX
5 hzmx01.mxmail.netease.com
10 hzmx02.mxmail.netease.com
TXT
SPF v=spf1 include:spf.163.com -all
CAALookup not available with standard resolver
Resolved in 168 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more ▾

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A
Crawlability
robots.txt present, sitemap with 0 URLs
PASS
robots.txt present, sitemap with 0 URLs
Info::
robots.txt is present
Got: 90 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Warning::
sitemap.xml is empty — no URLs found
An empty sitemap provides no value. Add <url> entries for your pages.
Info::
robots.txt references sitemap

An empty sitemap provides no value. Add <url> entries for your pages.

Why this matters

An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.

Learn more ▾

Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.

Source: Google Search Central / sitemaps.org

robots.txt 200 OK
Size 90 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: 
Crawl-delay: 120
Sitemap: http://www.people.cn/sitemap_index.xml
sitemap.xml 200 OK
Type URL Set URLs 0 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
people.cn — via 北京国科云计算技术有限公司（原北京中科三方网络技术有限公司）, 23 years, 5 months old, hosted on CHINANET-IDC-BJ-AP IDC, China Telecommunications Corporation, CN
PASS
people.cn — via 北京国科云计算技术有限公司（原北京中科三方网络技术有限公司）, 23 years, 5 months old, hosted on CHINANET-IDC-BJ-AP IDC, China Telecommunications Corporation, CN
Info::
Domain registered until Apr 23, 2027 (1 years remaining)
Info::
Registrar: 北京国科云计算技术有限公司（原北京中科三方网络技术有限公司）
Warning::
Registrar lock is NOT enabled
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Info::
Hosting: CHINANET-IDC-BJ-AP IDC, China Telecommunications Corporation, CN
Got: AS23724
Domain expiry

279 days

April 23, 2027

SSL certificate

228 days

Issued by WoTrus CA Limited

Domain age

23 years, 5 months

Registered March 10, 2003

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

CHINANET-IDC-BJ-AP IDC, China Telecommunications Corporation, CN

ASN AS23724

49.7.133.88

Registrar

北京国科云计算技术有限公司（原北京中科三方网络技术有限公司）

Unlocked 5 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar 北京国科云计算技术有限公司（原北京中科三方网络技术有限公司）
Created March 10, 2003 (23 years, 5 months ago)
Expires April 23, 2027 (1 years)
Name Servers ns4.people.cn, ns5.people.cn, ns1.people.cn, ns2.people.cn, ns3.people.cn
Hosting
IP Address 49.7.133.88
ASN AS23724 (CHINANET-IDC-BJ-AP IDC, China Telecommunications Corporation, CN)
Provider CHINANET-IDC-BJ-AP IDC, China Telecommunications Corporation, CN
Data source: whois (1.1s)

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Why this matters

Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.

Learn more ▾

Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback