Infrastructure - https://quark.cn 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.

C

DNS Records

Action

1 A records, 262 ms lookup

REVIEW

1 A records, 262 ms lookup

Resolves to 1 IPv4 address(es)

Got: 121.43.225.189

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

Has 1 IPv6 (AAAA) record(s)

Got: 2401:b180:1100::1ae

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: ai.advertisement.alibabacorp.sm.cn

No NS records found

No MX records — email not configured via DNS

CAA records not checked

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

No SPF record found in TXT records

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

DNS resolution is slow (262 ms)

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

Got: 262 ms

A	121.43.225.189
AAAA	2401:b180:1100::1ae
CNAME	ai.advertisement.alibabacorp.sm.cn
NS	—
MX	—
TXT	—
CAA	Lookup not available with standard resolver

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

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

Redirect Chain

1 redirect(s), 2078 ms total

REVIEW

1 redirect(s), 2078 ms total

Single redirect

Got: https://quark.cn → https://www.quark.cn/ (301)

WWW normalization redirect

Redirect overhead: 2078 ms total

Got: 2078 ms

https://quark.cn

837 ms · HTTP/1.1

301

https://www.quark.cn/

1241 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://quark.cn	301	837 ms	HTTP/1.1	Userver
2	https://www.quark.cn/	200	1241 ms	HTTP/1.1	Userver

See the visual redirect chain in the HTTP Probe tab →

B

URL Variants

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

REVIEW

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 correctly 301-redirects to HTTPS

www / non-www

200https://www.quark.cn/

200https://quark.cn/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://quark.cn/ → https://quark.cn/

Consistent

C

HTTP Probe Timing

Action

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

REVIEW

DNS Lookup

1.08 s

TCP Connect

210 ms

TLS Handshake

424 ms

Time to First Byte

1.93 s

Total Time

1.93 s

Connection waterfall

DNS Lookup 1.08 s TCP Connect 210 ms TLS Handshake 424 ms Server Processing 211 ms Content Transfer 0 ms

B

TLS Certificate Expiry & Recommendations

161 days until leaf cert expires — 5 issues to address

REVIEW

Certificate validity

161

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+

IPv6 Readiness

IPv6 reachable (222 ms)

PASS

IPv6 reachable (222 ms)

IPv6 is configured and reachable at 2401:b180:1100::1ae

Got: 222 ms connect

IPv6 Ready

AAAA Records 2401:b180:1100::1ae Connection Reachable (222 ms)

A+

Crawlability

robots.txt present, sitemap with 33 URLs

PASS

robots.txt present, sitemap with 33 URLs

robots.txt is present

Got: 650 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 33 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 650 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed

User-Agent: *
Allow: /
Disallow: /*?*
Disallow: /articles/*
Disallow: /articles$
Disallow: /quarkai/*
Disallow: /quarkai$
Disallow: /quarkapp/*
Disallow: /quarkapp$
Disallow: /quarkpc/*
Disallow: /quarkpc$
Disallow: /pan/*
Disallow: /pan$
Disallow: /saomiaowang/*
Disallow: /saomiaowang$
Disallow: /kuakexuexi/*
Disallow: /kuakexuexi$
Disallow: /kuakepaiti/*
Disallow: /kuakepaiti$
Disallow: /cuotizhengli/*
Disallow: /cuotizhengli$
Disallow: /kuakewendang/*
Disallow: /kuakewendang$
Disallow: /zhengjianzhao/*
Disallow: /zhengjianzhao$
Disallow: /kuakesousuo/*
Disallow: /kuakesousuo$
Disallow: /s/*
Disallow: /s$
Disallow: /ai/s/*
Disallow: /ai/s$

sitemap.xml 200 OK

Type URL Set URLs 33 entries Valid XML Yes

Sample URLs:

A+

Domain Intelligence

quark.cn — via 阿里巴巴云计算（北京）有限公司, 14 years old

PASS

quark.cn — via 阿里巴巴云计算（北京）有限公司, 14 years old

Domain registered until Jun 18, 2027 (1 years, 2 months remaining)

Registrar: 阿里巴巴云计算（北京）有限公司

Registrar lock is enabled

Domain cannot be transferred without explicit unlock from the registrar. This protects against unauthorized transfers.

Domain expiry

337 days

June 18, 2027

SSL certificate

161 days

Issued by GlobalSign nv-sa

Domain age

14 years

Registered June 18, 2012

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Unknown

2401:b180:1100::1ae

Registrar

阿里巴巴云计算（北京）有限公司

Locked 2 NS records

Expiry timeline

Today

+1 year

Domain expiry SSL expiry Danger zone (≤30 days)

Registrar 阿里巴巴云计算（北京）有限公司

Created June 18, 2012 (14 years ago)

Expires June 18, 2027 (1 years, 2 months)

Name Servers ns1.alibabadns.com, ns2.alibabadns.com

Hosting

IP Address 2401:b180:1100::1ae

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