Skip to content
https://ustc.edu.cn

Infrastructure

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

www / non-www

https://www.ustc.edu.cn/
200https://ustc.edu.cn/

HTTP → HTTPS

http://ustc.edu.cn/

HTTP version does not redirect to HTTPS

B
HTTP Probe Timing
Total 1427 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
342 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
361 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
358 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
1.43 s
Total Time Total request time from DNS lookup through full response.
1.43 s

Connection waterfall

DNS Lookup 342 ms TCP Connect 361 ms TLS Handshake 358 ms Server Processing 365 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
37 days until leaf cert expires — 5 issues to address
REVIEW

Certificate validity

37
days left
0d 30d 60d 90d+

Recommended actions

  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • 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, 581 ms lookup
PASS
1 A records, 581 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 202.38.64.246
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: 2001:da8:d800:642::248
Info::
2 nameserver(s) configured
Got: ns.ustc.edu.cn, mx.ustc.edu.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 (581 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 581 ms
A202.38.64.246
AAAA2001:da8:d800:642::248
CNAME
NSns.ustc.edu.cn, mx.ustc.edu.cn
MX
5 smtp.ustc.edu.cn
5 smtp2.ustc.edu.cn
TXT
google-site-verification=n_uAijUqmjntOJL0L8N4SIIdw_3cAngmXFBIYgIDNkg
SPF v=spf1 ip4:202.38.64.8 ip4:202.38.64.16 ip4:202.38.64.46 ip4:210.45.120.152 ip4:...
MS=ms26813611
CAALookup not available with standard resolver
Resolved in 581 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://ustc.edu.cn

https://ustc.edu.cn

1074 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://ustc.edu.cn2001074 msHTTP/1.1nginx
A+
IPv6 Readiness
IPv6 reachable (301 ms)
PASS
IPv6 reachable (301 ms)
Info::
IPv6 is configured and reachable at 2001:da8:d800:642::248
Got: 301 ms connect
IPv6 Ready
AAAA Records 2001:da8:d800:642::248 Connection Reachable (301 ms)
Domain Intelligence
Domain intelligence data not available
INFO
Domain intelligence data not available

RDAP and WHOIS lookup both failed

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback