Infrastructure - https://zblogcn.com BeaverCheck Audit

D

CDN & Delivery

Action

No CDN detected

FIX

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

DNS Records

5 A records, 623 ms lookup

REVIEW

5 A records, 623 ms lookup

Resolves to 5 IPv4 address(es)

Got: 175.43.192.174, 116.131.57.65, 101.71.88.61, 60.13.97.57, 211.93.211.158

No IPv6 (AAAA) records

CNAME record at zone apex

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Got: 4ssh22c6.slt.sched.tdnsv8.com

2 nameserver(s) configured

Got: topic.dnspod.net, arthur.dnspod.net

2 mail exchanger(s) configured

CAA records not checked

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

SPF record present in TXT

DNS resolution is slow (623 ms)

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Got: 623 ms

A	175.43.192.174, 116.131.57.65, 101.71.88.61, 60.13.97.57, 211.93.211.158
AAAA	—
CNAME	4ssh22c6.slt.sched.tdnsv8.com
NS	topic.dnspod.net, arthur.dnspod.net
MX	5 mxbiz1.qq.com 10 mxbiz2.qq.com
TXT	SPF v=spf1 include:spf.mail.qq.com ~all 4f7c20fa-2560-466f-83dd-aeef98aaa862-1419496149013 google-site-verification=3ACLjy2dqIleONlsW81iwC0zPIKddYzN6-XzbgDh1Rc
CAA	Lookup not available with standard resolver

Resolved in 623 ms

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more ▾

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

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.

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

B

Redirect Chain

1 redirect(s), 2099 ms total

REVIEW

1 redirect(s), 2099 ms total

Single redirect

Got: https://zblogcn.com → https://www.zblogcn.com/ (302)

WWW normalization redirect

Uses 302 (temporary) redirect

If permanent, use 301 instead.

Got: https://zblogcn.com

Redirect overhead: 2099 ms total

Got: 2099 ms

https://zblogcn.com

1080 ms · HTTP/1.1

302

https://www.zblogcn.com/

1019 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://zblogcn.com	302	1080 ms	HTTP/1.1	openresty
2	https://www.zblogcn.com/	200	1019 ms	HTTP/1.1	openresty/1.25.3.1

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

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

no robots.txt, no sitemap

REVIEW

no robots.txt, no sitemap

No robots.txt found

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

No sitemap.xml found

A sitemap helps search engines discover and index your pages more efficiently.

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more ▾

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more ▾

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

robots.txt No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

C

URL Variants

Action

www/non-www, trailing slash, HTTP→HTTPS

REVIEW

www/non-www, trailing slash, HTTP→HTTPS

Both www and non-www versions serve content

Got: Both variants return 200 Expected: One variant 301-redirects to the other

HTTP→HTTPS redirect uses 302 instead of 301

Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

200https://www.zblogcn.com/

200https://zblogcn.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Use 301 (permanent) instead of 302 (temporary)

B

HTTP Probe Timing

Total 1282 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

REVIEW

DNS Lookup

435 ms

TCP Connect

238 ms

TLS Handshake

251 ms

Time to First Byte

1.28 s

Total Time

1.28 s

Connection waterfall

DNS Lookup 435 ms TCP Connect 238 ms TLS Handshake 251 ms Server Processing 358 ms Content Transfer 0 ms

B

TLS Certificate Expiry & Recommendations

42 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

42

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+

Domain Intelligence

zblogcn.com — via DNSPod, Inc., 12 years, 4 months old, hosted on CHINA169-BACKBONE CHINA UNICOM China169 Backbone, CN

PASS

zblogcn.com — via DNSPod, Inc., 12 years, 4 months old, hosted on CHINA169-BACKBONE CHINA UNICOM China169 Backbone, CN

Domain registered until Feb 21, 2027 (10 months remaining)

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.

Registrar: DNSPod, Inc.

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.

Hosting: CHINA169-BACKBONE CHINA UNICOM China169 Backbone, CN

Got: AS4837

Domain expiry

218 days

February 21, 2027

SSL certificate

42 days

Issued by ZeroSSL

Domain age

12 years, 4 months

Registered February 21, 2014

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

CHINA169-BACKBONE CHINA UNICOM China169 Backbone, CN

ASN AS4837

211.93.211.158

Registrar

DNSPod, Inc.

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 DNSPod, Inc.

Created February 21, 2014 (12 years, 4 months ago)

Expires February 21, 2027 (10 months)

Last Updated July 18, 2025

Name Servers arthur.dnspod.net, topic.dnspod.net

DNSSEC Not enabled

Hosting

IP Address 211.93.211.158

ASN AS4837 (CHINA169-BACKBONE CHINA UNICOM China169 Backbone, CN)

Provider CHINA169-BACKBONE CHINA UNICOM China169 Backbone, CN

Data source: rdap (0.4s)

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