Skip to content
https://feishu.cn

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
78
GRADE
C
FIX
2
REVIEW
2
PASS
5
INFO
0
Probed from Madrid, Spain
307 Temporary Redirect
Checks
9
5 PASS 2 REVIEW 2 FIX
F
Redirect Chain
Action
3 redirect(s), 2827 ms total
FIX
3 redirect(s), 2827 ms total
Warning::
3 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://www.feishu.cn/
Warning::
Redirect overhead: 2827 ms total
Got: 2827 ms
Info::
Cross-domain redirect detected

https://feishu.cn

550 ms · HTTP/1.1

307

https://www.feishu.cn/

536 ms · HTTP/1.1

302

https://www.larksuite.com/en_us/?from_si...

954 ms · HTTP/1.1

301

https://www.larksuite.com/en_sg/?from_si...

786 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://feishu.cn307550 msHTTP/1.1TLB
2https://www.feishu.cn/302536 msHTTP/1.1volc-dcdn
3https://www.larksuite.com/en_us/?from_si...301954 msHTTP/1.1TLB
4https://www.larksuite.com/en_sg/?from_si...200786 msHTTP/1.1TLB

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

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

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.

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
TLS Certificate Expiry & Recommendations
270 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

270
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
2 A records, 245 ms lookup
PASS
2 A records, 245 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 122.14.236.76, 101.126.58.133
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: vip4.alidns.com, vip3.alidns.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
Warning::
DNS resolution is slow (245 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 245 ms
A122.14.236.76, 101.126.58.133
AAAA—
CNAME—
NSvip4.alidns.com, vip3.alidns.com
MX
10 mx1.feishu.cn
20 mx2.feishu.cn
30 mx3.feishu.cn
TXT
SPF v=spf1 include:spf.protection.partner.outlook.cn include:_netblocks.m.feishu.cn ...
google-site-verification=MMjIqjmOWnEQwp3mFZ-5OFlx2Uo_v1Segz6yKf01dZ8
verification-code-site-App_feishu=XmuEom61SU6juTVXMYLh
google-site-verification=utwLElChTeTPay5yMn4NqF-_6aqKxO8tS0KJWy5wlBc
google-site-verification=IexCuvHLRvTU_0EQY5m7QxGMhqSowYgkeE7RJB4P-C4
_globalsign-domain-verification=nVoktjzsfYmeWb5MWRqp5LMdvon0KHc4Dzj159AyP9
MS=ms26767525
qqmail-site-verification=10e9cad9b26723d76a3174786e0c402c067d6b57eb5
qqmail-site-verification=db098967c117b469c2cb29f717fb08d766e75b9493b
_f3zsp3jcr9843f36xnpbfib409nlhjt
google-site-verification=EooW_PCO4wl5oB9lqcSh0QH1gvVHEre1RmBtq2K31aw
google-site-verification=1WUgFybb_wW59OZTDR2ZPPtZp5Udod_b_vHAvuci8UQ
google-site-verification=L4LE6Fx-3g5m_mZTU58Ud0Z_2jW-Bh5MrXaYoxuqaOI
google-site-verification=M0UzjB9baO0F9vun2sJ_tf8WCfQtpC5qfRnMao5T02M
google-site-verification=lk-9t8onLvedo6PGfcBYL_MD2t-qYo1wZNUKXvUMRv0
qqmail-site-verification=26288cf2c988f9a18f0f419fe3e5ea49888adb5e5f9
qqmail-site-verification=1f9712b69ebd2b370e5033029f640281389510aeb79
CAALookup not available with standard resolver
Resolved in 245 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.

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

A+
Crawlability
robots.txt present, sitemap with 308 URLs
PASS
robots.txt present, sitemap with 308 URLs
Info::
robots.txt is present
Got: 496 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 308 entries
Info::
Sitemap index with 308 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 496 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Allow:/
Disallow:/*ggamj3vbcr.feishu.cn/
Disallow:/*gupjsw41o4.feishu.cn/
Disallow:/*ggq1ltumus.feishu.cn/
Disallow:/*kaizen.feishu.cn/
Disallow:/*pc26k79sx5.feishu.cn/
Disallow:/*sixeco.feishu.cn/
Disallow:/*gc5whanyf5.feishu.cn/
Disallow:/*wenjuan.feishu.cn/
Disallow:/*bluecity.feishu.cn/
Disallow:/*2fwww.feishu.cn/
Disallow:/*ccbft.feishu.cn/

Sitemap: https://www.feishu.cn/sitemap/sitemap.xml

# robots.txt file from https://www.feishu.cn/
# All robots will spider the domain
sitemap.xml 200 OK
Type Sitemap Index URLs 308 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)
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

302https://www.feishu.cn/
200https://feishu.cn/

Preferred variant: non-www

HTTP → HTTPS

307http://feishu.cn/ → https://www.feishu.cn/

Use 301 (permanent) instead of 302 (temporary)

A+
Domain Intelligence
feishu.cn — via 厦门易名科技股份有限公司, 19 years, 8 months old, hosted on CHINANET-IDC-BJ-AP IDC, China Telecommunications Corporation, CN
PASS
feishu.cn — via 厦门易名科技股份有限公司, 19 years, 8 months old, hosted on CHINANET-IDC-BJ-AP IDC, China Telecommunications Corporation, CN
Info::
Domain registered until Nov 11, 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: CHINANET-IDC-BJ-AP IDC, China Telecommunications Corporation, CN
Got: AS23724
Domain expiry

148 days

November 11, 2026

SSL certificate

270 days

Issued by DigiCert Inc

Domain age

19 years, 8 months

Registered November 11, 2006

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

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

ASN AS23724

122.14.236.76

Registrar

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

Locked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Registrar 厦门易名科技股份有限公司
Created November 11, 2006 (19 years, 8 months ago)
Expires November 11, 2026 (6 months)
Name Servers vip3.alidns.com, vip4.alidns.com
Hosting
IP Address 122.14.236.76
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)

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

A
HTTP Probe Timing
Total 579 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
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.
182 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
184 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
580 ms
Total Time Total request time from DNS lookup through full response.
580 ms

Connection waterfall

DNS Lookup 30 ms TCP Connect 182 ms TLS Handshake 184 ms Server Processing 183 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback