Skip to content
https://bjx.com.cn

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
75
GRADE
C
FIX
1
REVIEW
7
PASS
1
INFO
0
Probed from Sao Paulo, Brazil
301 Moved Permanently
Checks
9
1 PASS 7 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
DNS Records
2 A records, 649 ms lookup
REVIEW
2 A records, 649 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 8.140.251.145, 47.95.5.226
Info::
No IPv6 (AAAA) records
Warning::
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: alb-tab1f3bio2gwa4giew.cn-beijing.alb.aliyuncsslb.com
Info::
2 nameserver(s) configured
Got: f1g1ns2.dnspod.net, f1g1ns1.dnspod.net
Info::
1 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::
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 (649 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 649 ms
A8.140.251.145, 47.95.5.226
AAAA—
CNAMEalb-tab1f3bio2gwa4giew.cn-beijing.alb.aliyuncsslb.com
NSf1g1ns2.dnspod.net, f1g1ns1.dnspod.net
MX
10 mx.ym.163.com
TXT
qqmail-site-verification=968208bb06dee7c06cd764b6f32db03f542a6f2a25e
CAALookup not available with standard resolver
Resolved in 649 ms

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), 3339 ms total
REVIEW
1 redirect(s), 3339 ms total
Info::
Single redirect
Got: https://bjx.com.cn → https://www.bjx.com.cn/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 3339 ms total
Got: 3339 ms

https://bjx.com.cn

1710 ms · HTTP/1.1

301

https://www.bjx.com.cn/

1629 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://bjx.com.cn3011710 msHTTP/1.1
2https://www.bjx.com.cn/2001629 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

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
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 30 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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

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 30 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: * 
Disallow: /oidc
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

C
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

200https://www.bjx.com.cn/
200https://bjx.com.cn/

Inconsistent — duplicate content risk

HTTP → HTTPS

308http://bjx.com.cn/ → https://bjx.com.cn/

Use 301 (permanent) instead of 302 (temporary)

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

Connection waterfall

DNS Lookup 505 ms TCP Connect 330 ms TLS Handshake 336 ms Server Processing 332 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
292 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

292
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+
Domain Intelligence
bjx.com.cn — via 阿里云计算有限公司（万网）, 24 years, 5 months old, hosted on Alibaba Cloud
PASS
bjx.com.cn — via 阿里云计算有限公司（万网）, 24 years, 5 months old, hosted on Alibaba Cloud
Info::
Domain registered until Mar 27, 2033 (7 years remaining)
Info::
Registrar: 阿里云计算有限公司（万网）
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

2414 days

March 27, 2033

SSL certificate

292 days

Issued by DigiCert Inc

Domain age

24 years, 5 months

Registered March 27, 2002

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Alibaba Cloud

ASN AS37963

47.95.5.226

Registrar

阿里云计算有限公司（万网）

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar 阿里云计算有限公司（万网）
Created March 27, 2002 (24 years, 5 months ago)
Expires March 27, 2033 (7 years)
Name Servers f1g1ns1.dnspod.net, f1g1ns2.dnspod.net
Hosting
IP Address 47.95.5.226
ASN AS37963 (ALIBABA-CN-NET Hangzhou Alibaba Advertising Co.,Ltd., CN)
Provider Alibaba Cloud
Data source: whois (1.9s)

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

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

Send Feedback