Infrastructure - https://58.com BeaverCheck Audit

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

Redirect Chain

1 redirect(s), 2489 ms total

REVIEW

1 redirect(s), 2489 ms total

Single redirect

Got: https://58.com → https://bj.58.com/ (302)

Uses 302 (temporary) redirect

If permanent, use 301 instead.

Got: https://58.com

Redirect overhead: 2489 ms total

Got: 2489 ms

Cross-domain redirect detected

https://58.com

1132 ms · HTTP/1.1

302

https://bj.58.com/

1357 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://58.com	302	1132 ms	HTTP/1.1	Tengine
2	https://bj.58.com/	200	1357 ms	HTTP/1.1	Tengine

See the visual redirect chain in the HTTP Probe tab →

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

B

HTTP Probe Timing

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

REVIEW

DNS Lookup

128 ms

TCP Connect

340 ms

TLS Handshake

341 ms

Time to First Byte

1.15 s

Total Time

1.16 s

Connection waterfall

DNS Lookup 128 ms TCP Connect 340 ms TLS Handshake 341 ms Server Processing 346 ms Content Transfer 1 ms

B

TLS Certificate Expiry & Recommendations

352 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

352

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, 127 ms lookup

PASS

2 A records, 127 ms lookup

Resolves to 2 IPv4 address(es)

Got: 43.144.202.142, 42.187.161.231

Has 1 IPv6 (AAAA) record(s)

Got: 2402:4e00:1208:2100:0:9d0b:4476:cb8a

2 nameserver(s) configured

Got: ns4.dnsv5.com, ns3.dnsv5.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 time: 127 ms

Got: 127 ms

A	43.144.202.142, 42.187.161.231
AAAA	2402:4e00:1208:2100:0:9d0b:4476:cb8a
CNAME	—
NS	ns4.dnsv5.com, ns3.dnsv5.com
MX	5 mxbiz1.qq.com 10 mxbiz2.qq.com
TXT	TmHAkMZ37fnwOJCDgKGUa/na+/qDhCPq3Hbv/hm0Vdo= SPF v=spf1 include:spf.mail.qq.com include:easeye-edm.com -all cursor-domain-verification-bd24dd=DoVliXeIHxtLMdD8xncGsVSnS _globalsign-domain-verification=kMbXdicQq3Xiao4eLI3jg4vYLRqTCpVqQspbO3g0V- _globalsign-domain-verification=uY2UynA9h1JClxUEyFlCp2AWqlnWWkMJ3M3VBqjo1V
CAA	Lookup not available with standard resolver

Resolved in 127 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.

A+

IPv6 Readiness

IPv6 reachable (338 ms)

PASS

IPv6 reachable (338 ms)

IPv6 is configured and reachable at 2402:4e00:1208:2100:0:9d0b:4476:cb8a

Got: 338 ms connect

IPv6 Ready

AAAA Records 2402:4e00:1208:2100:0:9d0b:4476:cb8a Connection Reachable (338 ms)

A+

Crawlability

robots.txt present, sitemap with 390 URLs

PASS

robots.txt present, sitemap with 390 URLs

robots.txt is present

Got: 388 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 390 entries

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 388 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed

User-agent: *

Allow: /shoujidaquan/*

Disallow: /*?*

Disallow: /sou/*Q*

Disallow: link.58.com

Disallow: link.58.com/*

Disallow: /wenda/*/all/

Disallow: /wenda/*/list-*/

Disallow: /wenda/*/tg-*/

Disallow: /wenda/mr*.shtml

Disallow: /wenda/xq*.shtml

Disallow: /wenda/dr*.shtml

Disallow: /a/ershouche/*

Disallow: /a/dedecms/*

Disallow: cheapi.58.com*

Disallow: cheapi.58.com/*

sitemap.xml 200 OK

Type URL Set URLs 390 entries Valid XML Yes

Sample URLs:

A

URL Variants

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

PASS

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

www/non-www redirect configured correctly (preferred: non-www)

HTTP→HTTPS redirect uses 302 instead of 301

Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

302https://www.58.com/

200https://58.com/

Preferred variant: non-www

HTTP → HTTPS

302http://58.com/ → https://58.com/

Use 301 (permanent) instead of 302 (temporary)

A+

Domain Intelligence

58.com — via eName Technology Co., Ltd., 28 years, 2 months old

PASS

58.com — via eName Technology Co., Ltd., 28 years, 2 months old

Domain registered until Jul 9, 2030 (4 years, 3 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: eName Technology Co., Ltd.

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.

Domain expiry

1484 days

July 9, 2030

SSL certificate

352 days

Issued by GlobalSign nv-sa

Domain age

28 years, 2 months

Registered July 10, 1998

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2402:4e00:1208:2100:0:9d0b:4476:cb8a

Registrar

eName Technology Co., Ltd.

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 eName Technology Co., Ltd.

Created July 10, 1998 (28 years, 2 months ago)

Expires July 9, 2030 (4 years, 3 months)

Last Updated July 26, 2022

Name Servers ns3.dnsv5.com, ns4.dnsv5.com

DNSSEC Not enabled

Hosting

IP Address 2402:4e00:1208:2100:0:9d0b:4476:cb8a

Data source: rdap (0.5s)

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