Infrastructure - https://zhaopin.com BeaverCheck Audit

D

Redirect Chain

Action

2 redirect(s), 3322 ms total

FIX

2 redirect(s), 3322 ms total

2 redirects before reaching final URL

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

HTTP to HTTPS redirect present

WWW normalization redirect

2-hop chain could be reduced to 1 hop

Redirect directly from https://zhaopin.com to https://www.zhaopin.com/

Redirect overhead: 3322 ms total

Got: 3322 ms

https://zhaopin.com

1792 ms · HTTP/1.1

301

http://www.zhaopin.com/

761 ms · HTTP/1.1

301

https://www.zhaopin.com/

769 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://zhaopin.com	301	1792 ms	HTTP/1.1	Tengine
2	http://www.zhaopin.com/	301	761 ms	HTTP/1.1	Tengine
3	https://www.zhaopin.com/	200	769 ms	HTTP/1.1	Tengine

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

Redirect directly from https://zhaopin.com to https://www.zhaopin.com/

Why this matters

Redirect chain could be flattened to one hop — server config tweak removes intermediate latency.

Source: web.dev

D

URL Variants

Action

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

FIX

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 version does not redirect to HTTPS

Got: HTTP 301 Expected: 301 redirect to HTTPS

www / non-www

200https://www.zhaopin.com/

200https://zhaopin.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://zhaopin.com/ → http://www.zhaopin.com/

HTTP version does not redirect to HTTPS

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

1 A records, 404 ms lookup

REVIEW

1 A records, 404 ms lookup

Resolves to 1 IPv4 address(es)

Got: 43.159.108.49

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

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: gtm.zhaopin.com

2 nameserver(s) configured

Got: vip3.alidns.com, vip4.alidns.com

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 (404 ms)

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

Got: 404 ms

A	43.159.108.49
AAAA	—
CNAME	gtm.zhaopin.com
NS	vip3.alidns.com, vip4.alidns.com
MX	5 hzmx01.mxmail.netease.com 10 hzmx02.mxmail.netease.com
TXT	SPF v=spf1 include:spf.163.com -all qqmail-site-verification=7aff805aa483b6fa863773a4eb00f825de44fd6dadd globalsign-domain-verification=Kxr8wkeXlHs0gmF7D4C1xPKXMH0ECQtEooPXzfvxCQ
CAA	Lookup not available with standard resolver

Resolved in 404 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

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

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

C

HTTP Probe Timing

Action

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

REVIEW

DNS Lookup

488 ms

TCP Connect

1 ms

TLS Handshake

8 ms

Time to First Byte

1.70 s

Total Time

1.70 s

Connection waterfall

DNS Lookup 488 ms TCP Connect 1 ms TLS Handshake 8 ms Server Processing 1.21 s Content Transfer 0 ms

B

TLS Certificate Expiry & Recommendations

206 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

206

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+

Crawlability

robots.txt present, sitemap with 5 URLs

PASS

robots.txt present, sitemap with 5 URLs

robots.txt is present

Got: 114 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 5 entries

Sitemap index with 5 child sitemaps

robots.txt does not reference a sitemap

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK

Size 114 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed

User-agent: *


Disallow: *?*


Disallow: /source/


Disallow: /install/


Disallow: /data/


Allow: *?utm_*

sitemap.xml 200 OK

Type Sitemap Index URLs 5 entries Valid XML Yes

Child Sitemaps:

A+

Domain Intelligence

zhaopin.com — via Xin Net Technology Corporation, 28 years, 9 months old, hosted on ACE-AS-AP ACE, SG

PASS

zhaopin.com — via Xin Net Technology Corporation, 28 years, 9 months old, hosted on ACE-AS-AP ACE, SG

Domain registered until Dec 3, 2033 (7 years, 8 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: Xin Net Technology Corporation

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: ACE-AS-AP ACE, SG

Got: AS139341

Domain expiry

2695 days

December 3, 2033

SSL certificate

206 days

Issued by GlobalSign nv-sa

Domain age

28 years, 9 months

Registered December 17, 1997

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

ACE-AS-AP ACE, SG

ASN AS139341

43.159.108.49

Registrar

Xin Net Technology Corporation

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 Xin Net Technology Corporation

Created December 17, 1997 (28 years, 9 months ago)

Expires December 3, 2033 (7 years, 8 months)

Last Updated January 28, 2026

Name Servers vip3.alidns.com, vip4.alidns.com

DNSSEC Not enabled

Hosting

IP Address 43.159.108.49

ASN AS139341 (ACE-AS-AP ACE, SG)

Provider ACE-AS-AP ACE, SG

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