Skip to content
https://cnblogs.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
77
GRADE
C
FIX
1
REVIEW
6
PASS
2
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
2 PASS 6 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), 1793 ms total
REVIEW
1 redirect(s), 1793 ms total
Info::
Single redirect
Got: https://cnblogs.com → https://www.cnblogs.com/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1793 ms total
Got: 1793 ms

https://cnblogs.com

814 ms · HTTP/1.1

301

https://www.cnblogs.com/

978 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://cnblogs.com301814 msHTTP/1.1
2https://www.cnblogs.com/200978 msHTTP/1.1

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
Crawlability
robots.txt present, sitemap with 38998 URLs
REVIEW
robots.txt present, sitemap with 38998 URLs
Info::
robots.txt is present
Got: 69 bytes
Info::
sitemap.xml is present
Warning::
sitemap.xml contains invalid XML
Search engines may not be able to parse the sitemap. Fix XML validation errors.
Info::
sitemap.xml contains 38998 entries
Info::
Sitemap index with 38998 child sitemaps
Info::
robots.txt references sitemap

Search engines may not be able to parse the sitemap. Fix XML validation errors.

Why this matters

An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.

Learn more ▾

Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.

Source: sitemaps.org / Google Search Central

robots.txt 200 OK
Size 69 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-Agent: *
Allow: /

Sitemap: https://www.cnblogs.com/sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 38998 entries Valid XML No
Child Sitemaps:
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.cnblogs.com/
200https://cnblogs.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

302http://cnblogs.com/ → https://cnblogs.com/

Use a permanent redirect (301 or 308) instead of a temporary one

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

Connection waterfall

DNS Lookup 30 ms TCP Connect 184 ms TLS Handshake 402 ms Server Processing 188 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
295 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

295
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
  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • 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, 37 ms lookup
PASS
1 A records, 37 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 101.37.97.51
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: vip4.alidns.com, vip3.alidns.com
Info::
7 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::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 37 ms
Got: 37 ms
A101.37.97.51
AAAA—
CNAME—
NSvip4.alidns.com, vip3.alidns.com
MX
10 aspmx3.googlemail.com
10 aspmx4.googlemail.com
10 alt2.aspmx.l.google.com
10 aspmx2.googlemail.com
10 alt1.aspmx.l.google.com
10 aspmx.l.google.com
10 aspmx5.googlemail.com
TXT
aliyun-site-verification=440c2c9c-1adc-4cd2-b695-fa21c7614056
google-site-verification=kdUMdsdtBuGBYKs3uIk-9G9dRQADgkionurDPeUnhC8
CAALookup not available with standard resolver
Resolved in 37 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.

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more ▾

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

A+
Domain Intelligence
cnblogs.com — via Xiamen 35.com Information Co., Ltd., 22 years, 9 months old, hosted on Alibaba Cloud
PASS
cnblogs.com — via Xiamen 35.com Information Co., Ltd., 22 years, 9 months old, hosted on Alibaba Cloud
Info::
Domain registered until Nov 12, 2030 (4 years, 7 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: Xiamen 35.com Information 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: Alibaba Cloud
Got: AS37963
Domain expiry

1531 days

November 12, 2030

SSL certificate

295 days

Issued by DigiCert Inc

Domain age

22 years, 9 months

Registered November 12, 2003

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Alibaba Cloud

ASN AS37963

101.37.97.51

Registrar

Xiamen 35.com Information Co., Ltd.

Unlocked 2 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 Xiamen 35.com Information Co., Ltd.
Created November 12, 2003 (22 years, 9 months ago)
Expires November 12, 2030 (4 years, 7 months)
Last Updated January 14, 2026
Name Servers vip3.alidns.com, vip4.alidns.com
DNSSEC Not enabled
Hosting
IP Address 101.37.97.51
ASN AS37963 (ALIBABA-CN-NET Hangzhou Alibaba Advertising Co.,Ltd., CN)
Provider Alibaba Cloud
Data source: rdap (0.3s)

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