Skip to content
https://juejin.cn

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
88
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
4 PASS 4 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
DNS Records
10 A records, 351 ms lookup
REVIEW
10 A records, 351 ms lookup
Info::
Resolves to 10 IPv4 address(es)
Got: 47.246.45.183, 155.102.46.10, 47.246.45.235, 47.246.45.180, 47.246.45.186, 47.246.45.181, 47.246.45.185, 47.246.45.182, 155.102.214.148, 47.246.45.179
Info::
No IPv6 (AAAA) records
Warning::
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: juejin.cn.w.cdngslb.com
Info::
No NS records found
Info::
No MX records — email not configured via DNS
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'.
Warning::
DNS resolution is slow (351 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 351 ms
A47.246.45.183, 155.102.46.10, 47.246.45.235, 47.246.45.180, 47.246.45.186, 47.246.45.181, 47.246.45.185, 47.246.45.182, 155.102.214.148, 47.246.45.179
AAAA
CNAMEjuejin.cn.w.cdngslb.com
NS
MX
TXT
CAALookup not available with standard resolver
Resolved in 351 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.

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)

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

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 1044 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
501 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
1 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
4 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
868 ms
Total Time Total request time from DNS lookup through full response.
1.04 s

Connection waterfall

DNS Lookup 501 ms TCP Connect 1 ms TLS Handshake 4 ms Server Processing 362 ms Content Transfer 177 ms
B
TLS Certificate Expiry & Recommendations
271 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

271
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+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://juejin.cn

https://juejin.cn

398 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://juejin.cn200398 msHTTP/1.1Tengine
A+
Crawlability
robots.txt present, sitemap with 53 URLs
PASS
robots.txt present, sitemap with 53 URLs
Info::
robots.txt is present
Got: 844 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 53 entries
Info::
Sitemap index with 53 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 844 B Sitemaps referenced 9 User-agents * Blocking No — crawling allowed
User-agent: *

Disallow: /subscribe/subscribed
Disallow: /user/settings
Disallow: /drafts
Disallow: /news-drafts
Disallow: /editor
Disallow: /oauth-result
Disallow: /search
Disallow: /s/
Disallow: /equation
Disallow: /book/order
Disallow: /books/payment
Disallow: /appview
Disallow: /creator
Disallow: /notification
Disallow: /translate
Disallow: /zhuanlan
Disallow: /spost

Sitemap: https://juejin.cn/sitemap/posts/index.xml
Sitemap: https://juejin.cn/sitemap/user/index.xml
Sitemap: https://juejin.cn/sitemap/news/index.xml
Sitemap: https://juejin.cn/sitemap/columns/index.xml
Sitemap: https://juejin.cn/sitemap/tag/index.xml
Sitemap: https://juejin.cn/sitemap/pin/index.xml
Sitemap: https://juejin.cn/sitemap/collections/index.xml
Sitemap: https://juejin.cn/sitemap/user_posts/index.xml
Sitemap: https://juejin.cn/sitemap/user_pins/index.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 53 entries Valid XML Yes
Child Sitemaps:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.juejin.cn/
200https://juejin.cn/

Preferred variant: non-www

HTTP → HTTPS

301http://juejin.cn/ https://juejin.cn/

Consistent

A+
Domain Intelligence
juejin.cn — via 厦门易名科技股份有限公司, 19 years, 9 months old, hosted on TAOBAO Zhejiang Taobao Network Co.,Ltd, CN
PASS
juejin.cn — via 厦门易名科技股份有限公司, 19 years, 9 months old, hosted on TAOBAO Zhejiang Taobao Network Co.,Ltd, CN
Info::
Domain registered until Oct 28, 2026 (6 months remaining)
Info::
Registrar: 厦门易名科技股份有限公司
Info::
Registrar lock is enabled
Domain cannot be transferred without explicit unlock from the registrar. This protects against unauthorized transfers.
Info::
Hosting: TAOBAO Zhejiang Taobao Network Co.,Ltd, CN
Got: AS24429
Domain expiry

134 days

October 28, 2026

SSL certificate

271 days

Issued by DigiCert Inc

Domain age

19 years, 9 months

Registered October 28, 2006

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

TAOBAO Zhejiang Taobao Network Co.,Ltd, CN

ASN AS24429

155.102.46.10

Registrar

厦门易名科技股份有限公司

Locked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Registrar 厦门易名科技股份有限公司
Created October 28, 2006 (19 years, 9 months ago)
Expires October 28, 2026 (6 months)
Name Servers vip3.alidns.com, vip4.alidns.com
Hosting
IP Address 155.102.46.10
ASN AS24429 (TAOBAO Zhejiang Taobao Network Co.,Ltd, CN)
Provider TAOBAO Zhejiang Taobao Network Co.,Ltd, CN
Data source: whois (1.1s)

Domain cannot be transferred without explicit unlock from the registrar. This protects against unauthorized transfers.

Why this matters

Registrar lock (clientTransferProhibited et al.) prevents unauthorized domain transfers — 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