Skip to content
https://ai.zhailaoban.com/showcase

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
83
GRADE
B
FIX
1
REVIEW
10
PASS
6
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
6 PASS 10 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN (document or assets)
FIX
No CDN (document or assets)
Warning::
No CDN (document or assets)
Neither the HTML document nor the page's subresources are served through an edge network. A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN (document or assets)

Consider using a CDN to improve global delivery speed and reduce origin load.

B
DNS Records
1 A records, 324 ms lookup
REVIEW
1 A records, 324 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 49.232.165.136
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
No NS records found
Info::
No MX records — email not configured via DNS
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 (324 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 324 ms
A49.232.165.136
AAAA—
CNAME—
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 324 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

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

B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
DNSSEC is not deployed
The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).
B
CAA Records
No CAA records (any CA may issue certificates)
REVIEW
No CAA records (any CA may issue certificates)
Info::
No CAA records published
Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.
C
Reverse DNS
Action
0/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR lookup failed for 49.232.165.136: lookup 49.232.165.136: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
C
Multi-Resolver DNS Speed
Action
Mean 353ms across 3 resolvers (spread 182ms)
REVIEW
Mean 353ms across 3 resolvers (spread 182ms)
Info::
Google: 233ms
Got: 233ms via 8.8.8.8:53
Info::
Quad9: 412ms
Got: 412ms via 9.9.9.9:53
Info::
Cloudflare: 415ms
Got: 415ms via 1.1.1.1:53
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 843 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
282 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
183 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
190 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
843 ms
Total Time Total request time from DNS lookup through full response.
844 ms

Connection waterfall

DNS Lookup 282 ms TCP Connect 183 ms TLS Handshake 190 ms Server Processing 187 ms Content Transfer 1 ms
B
TLS Certificate Expiry & Recommendations
68 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

68
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
B
CDN Cache Observability
No CDN cache-status headers in the response
REVIEW
No CDN cache-status headers in the response
Info::
No CDN cache-status headers in the response
Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.
B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://ai.zhailaoban.com/showcase

https://ai.zhailaoban.com/showcase

561 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://ai.zhailaoban.com/showcase200561 msHTTP/1.1nginx/1.24.0 (Ubuntu)
A+
Crawlability
robots.txt present, sitemap with 16 URLs
PASS
robots.txt present, sitemap with 16 URLs
Info::
robots.txt is present
Got: 79 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 16 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 79 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Allow: /articles/
Sitemap: https://ai.zhailaoban.com/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 16 entries Valid XML Yes
Sample URLs:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

https://www.ai.zhailaoban.com/showcase
200https://ai.zhailaoban.com/showcase

Trailing Slash

307https://ai.zhailaoban.com/showcase/
200https://ai.zhailaoban.com/showcase

HTTP → HTTPS

301http://ai.zhailaoban.com/showcase → https://ai.zhailaoban.com/showcase

Consistent

A+
Domain Intelligence
zhailaoban.com — via Alibaba Cloud Computing Ltd. d/b/a HiChina (www.net.cn), 11 years, 2 months old, hosted on Alibaba Cloud
PASS
zhailaoban.com — via Alibaba Cloud Computing Ltd. d/b/a HiChina (www.net.cn), 11 years, 2 months old, hosted on Alibaba Cloud
Info::
Domain registered until Oct 1, 2029 (3 years 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: Alibaba Cloud Computing Ltd. d/b/a HiChina (www.net.cn)
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

1092 days

October 1, 2029

SSL certificate

68 days

Issued by Let's Encrypt

Domain age

11 years, 2 months

Registered October 1, 2015

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Alibaba Cloud

ASN AS37963

60.205.194.12

Registrar

Alibaba Cloud Computing Ltd. d/b/a HiChina (www.net.cn)

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 Alibaba Cloud Computing Ltd. d/b/a HiChina (www.net.cn)
Created October 1, 2015 (11 years, 2 months ago)
Expires October 1, 2029 (3 years)
Last Updated September 12, 2026
Name Servers ns1.alidns.com, ns2.alidns.com
DNSSEC Not enabled
Hosting
IP Address 60.205.194.12
ASN AS37963 (ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd., CN)
Provider Alibaba Cloud
Data source: rdap (0.7s)

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

A+
Health Check Endpoint
Health endpoint at https://ai.zhailaoban.com/health (HTTP 200)
PASS
Health endpoint at https://ai.zhailaoban.com/health (HTTP 200)
Info::
Public health endpoint at https://ai.zhailaoban.com/health
Got: https://ai.zhailaoban.com/health
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback