Skip to content
https://icbc.com.cn

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
3
REVIEW
2
PASS
4
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
4 PASS 2 REVIEW 3 FIX
D
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
FIX
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
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 200 Expected: 301 redirect to HTTPS

www / non-www

200https://www.icbc.com.cn/
200https://icbc.com.cn/

Inconsistent — duplicate content risk

HTTP → HTTPS

200http://icbc.com.cn/

HTTP version does not redirect to HTTPS

F
HTTP Probe Timing
Action
Total 7443 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
FIX
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
358 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
215 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
650 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
1.44 s
Total Time Total request time from DNS lookup through full response.
7.44 s

Connection waterfall

DNS Lookup 358 ms TCP Connect 215 ms TLS Handshake 650 ms Server Processing 218 ms Content Transfer 6.00 s
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
Crawlability
no robots.txt, no sitemap
REVIEW
no robots.txt, no sitemap
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
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.

B
TLS Certificate Expiry & Recommendations
284 days until leaf cert expires — 5 issues to address
REVIEW

Certificate validity

284
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
  • Add includeSubDomains to the HSTS directive
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • 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, 415 ms lookup
PASS
1 A records, 415 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 58.33.222.36
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 1 IPv6 (AAAA) record(s)
Got: 2409:871e:8200:2::18b
Info::
6 nameserver(s) configured
Got: shuni.icbc.com.cn, cns2.icbc.com.cn, bjtns2.icbc.com.cn, tns1.icbc.com.cn, shtns.icbc.com.cn, ns114.icbc.com.cn
Info::
2 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 (415 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 415 ms
A58.33.222.36
AAAA2409:871e:8200:2::18b
CNAME—
NSshuni.icbc.com.cn, cns2.icbc.com.cn, bjtns2.icbc.com.cn, tns1.icbc.com.cn, shtns.icbc.com.cn, ns114.icbc.com.cn
MX
10 mx1.icbc.com.cn
50 mx2.icbc.com.cn
TXT
VISA=15F6CD154DCAB785AE838EC20216F869
VISA=BC7F45BC1984466755FB14F9866E85FE
VISA=E26A19ABE0FB395CA85F5D281BBAE13A
google-site-verification=x-q2H2Ym5gS1_IK9QeM7QXRVerEXADbNJQy6DXu13YE
SPF v=spf1 include:spf.icbc.com.cn -all
mBIpyNzz0UBhvSJFtxJV0orBOLB8cPOw9f+tJyFDGyg=
VISA=75E5C925346A58A64508BCDDFFAFC766
d958cjzqdb271t220g37ygdnj69y2wkx
90yc9cth2h0xz51pkmh35y7cblynyq6l
lv7zm833snt467vrj11nzmf3gyy0r84q
VISA=4619E80F312F5D2471F5304D3C54D6E4
20251014402777197344ed959913336bd20509b47fbd7eb91bfb110220b169f0e11f3a2a89dbfd04
CAALookup not available with standard resolver
Resolved in 415 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.

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

https://icbc.com.cn

1483 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://icbc.com.cn2001483 msHTTP/1.1
A+
IPv6 Readiness
IPv6 reachable (213 ms)
PASS
IPv6 reachable (213 ms)
Info::
IPv6 is configured and reachable at 2409:871e:8200:2::18b
Got: 213 ms connect
IPv6 Ready
AAAA Records 2409:871e:8200:2::18b Connection Reachable (213 ms)
A+
Domain Intelligence
icbc.com.cn — via 北京国科云计算技术有限公司（原北京中科三方网络技术有限公司）, 24 years, 10 months old
PASS
icbc.com.cn — via 北京国科云计算技术有限公司（原北京中科三方网络技术有限公司）, 24 years, 10 months old
Info::
Domain registered until Oct 17, 2029 (3 years, 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.
Domain expiry

1219 days

October 17, 2029

SSL certificate

284 days

Issued by China Financial Certification Authority

Domain age

24 years, 10 months

Registered October 17, 2001

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Unknown

2409:871e:8200:2::18b

Registrar

北京国科云计算技术有限公司（原北京中科三方网络技术有限公司）

Locked 6 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Registrar 北京国科云计算技术有限公司（原北京中科三方网络技术有限公司）
Created October 17, 2001 (24 years, 10 months ago)
Expires October 17, 2029 (3 years, 6 months)
Name Servers cns2.icbc.com.cn, tns1.icbc.com.cn, shtns.icbc.com.cn, bjtns2.icbc.com.cn, shuni.icbc.com.cn, ns114.icbc.com.cn
Hosting
IP Address 2409:871e:8200:2::18b
Data source: whois (1.0s)

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