Skip to content
https://qq.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
82
GRADE
B
FIX
1
REVIEW
5
PASS
3
INFO
0
Probed from Singapore, Singapore
302 Found
Checks
9
3 PASS 5 REVIEW 1 FIX
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), 1876 ms total
REVIEW
1 redirect(s), 1876 ms total
Info::
Single redirect
Got: https://qq.com → https://www.qq.com/ (302)
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://qq.com
Warning::
Redirect overhead: 1876 ms total
Got: 1876 ms

https://qq.com

1816 ms · HTTP/1.1

302

https://www.qq.com/

60 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://qq.com3021816 msHTTP/1.1stgw
2https://www.qq.com/20060 msHTTP/1.1tRPC-Gateway

See the visual redirect chain in the HTTP Probe tab →

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more ▾

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

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

C
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
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
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

200https://www.qq.com/
200https://qq.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

302http://qq.com/ → https://www.qq.com/

Use 301 (permanent) instead of 302 (temporary)

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

Connection waterfall

DNS Lookup 2 ms TCP Connect 222 ms TLS Handshake 452 ms Server Processing 223 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
57 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • 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
3 A records, 5 ms lookup
PASS
3 A records, 5 ms lookup
Info::
Resolves to 3 IPv4 address(es)
Got: 203.205.254.157, 113.108.81.189, 123.150.76.218
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns4.qq.com, ns1.qq.com, ns2.qq.com, ns3.qq.com
Info::
3 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: 5 ms
Got: 5 ms
A203.205.254.157, 113.108.81.189, 123.150.76.218
AAAA—
CNAME—
NSns4.qq.com, ns1.qq.com, ns2.qq.com, ns3.qq.com
MX
10 mx3.qq.com
20 mx2.qq.com
30 mx1.qq.com
TXT
SPF v=spf1 include:spf.mail.qq.com -all
CAALookup not available with standard resolver
Resolved in 5 ms

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 1000 URLs
PASS
robots.txt present, sitemap with 1000 URLs
Info::
robots.txt is present
Got: 71 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 1000 entries
Info::
Sitemap index with 1000 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 71 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: 
Sitemap: https://news.qq.com/sitemap/index.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 1000 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
qq.com — via MarkMonitor Information Technology (Shanghai) Co., Ltd., 31 years, 4 months old, hosted on CHINATELECOM-TIANJIN Tianjij,300000, CN
PASS
qq.com — via MarkMonitor Information Technology (Shanghai) Co., Ltd., 31 years, 4 months old, hosted on CHINATELECOM-TIANJIN Tianjij,300000, CN
Info::
Domain registered until Jul 27, 2034 (8 years, 4 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: MarkMonitor Information Technology (Shanghai) Co., Ltd.
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: CHINATELECOM-TIANJIN Tianjij,300000, CN
Got: AS58542
Domain expiry

2901 days

July 27, 2034

SSL certificate

57 days

Issued by DigiCert, Inc.

Domain age

31 years, 4 months

Registered May 4, 1995

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

CHINATELECOM-TIANJIN Tianjij,300000, CN

ASN AS58542

123.150.76.218

Registrar

MarkMonitor Information Technology (Shanghai) Co., Ltd.

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar MarkMonitor Information Technology (Shanghai) Co., Ltd.
Created May 4, 1995 (31 years, 4 months ago)
Expires July 27, 2034 (8 years, 4 months)
Last Updated April 14, 2026
Name Servers ns1.qq.com, ns2.qq.com, ns3.qq.com, ns4.qq.com
DNSSEC Not enabled
Hosting
IP Address 123.150.76.218
ASN AS58542 (CHINATELECOM-TIANJIN Tianjij,300000, CN)
Provider CHINATELECOM-TIANJIN Tianjij,300000, CN
Data source: rdap (0.5s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more ▾

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

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