Skip to content
https://eyoucms.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
80
GRADE
B
FIX
1
REVIEW
5
PASS
3
INFO
0
Probed from Santa Clara, United States
301 Moved Permanently
Checks
9
3 PASS 5 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
1 A records, 346 ms lookup
REVIEW
1 A records, 346 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 8.133.207.83
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: dns7.hichina.com, dns8.hichina.com
Info::
No MX records — email not configured via DNS
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 (346 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 346 ms
A8.133.207.83
AAAA—
CNAME—
NSdns7.hichina.com, dns8.hichina.com
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 346 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.

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

https://eyoucms.com

725 ms · HTTP/1.1

301

https://www.eyoucms.com/

1654 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://eyoucms.com301725 msHTTP/1.1Apache
2https://www.eyoucms.com/2001654 msHTTP/1.1Apache

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
URL Variants
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
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.eyoucms.com/
200https://eyoucms.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://eyoucms.com/ → https://eyoucms.com/

Consistent

C
TLS Certificate Expiry & Recommendations
Action
28 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

28
days left
0d 30d 60d 90d+
Renew soon — under 30 days remaining

Recommended actions

  • Renew certificate — 28 days remaining
  • 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 19 URLs
PASS
robots.txt present, sitemap with 19 URLs
Info::
robots.txt is present
Got: 266 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 19 entries
Info::
Sitemap index with 19 child sitemaps
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your 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 266 B Sitemaps referenced 0 User-agents *, 360Spider Blocking No — crawling allowed
User-agent: *
Disallow: /index.php?m=api&*
Disallow: /index.php?m=plugins&*
Disallow: /index.php?*c=Search*
Disallow: /&wd=*&eqid=*
Disallow: /plus/*
Disallow: /skin/*
Disallow: /static/*
Disallow: /public/*
Disallow: /template/*

User-agent:360Spider
Crawl-delay: 1
sitemap.xml 200 OK
Type Sitemap Index URLs 19 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
eyoucms.com — via Alibaba Cloud Computing (Beijing) Co., Ltd., 8 years, 1 months old, hosted on Alibaba Cloud
PASS
eyoucms.com — via Alibaba Cloud Computing (Beijing) Co., Ltd., 8 years, 1 months old, hosted on Alibaba Cloud
Info::
Domain registered until Apr 6, 2028 (1 years, 11 months remaining)
Info::
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.
Info::
Registrar: Alibaba Cloud Computing (Beijing) Co., Ltd.
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

660 days

April 6, 2028

SSL certificate

28 days

Issued by Unizeto Technologies S.A.

Domain age

8 years, 1 months

Registered April 6, 2018

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Alibaba Cloud

ASN AS37963

8.133.207.83

Registrar

Alibaba Cloud Computing (Beijing) Co., Ltd.

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the TLS certificate or verify auto-renewal is working
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Alibaba Cloud Computing (Beijing) Co., Ltd.
Created April 6, 2018 (8 years, 1 months ago)
Expires April 6, 2028 (1 years, 11 months)
Last Updated November 5, 2025
Name Servers dns7.hichina.com, dns8.hichina.com
DNSSEC Not enabled
Hosting
IP Address 8.133.207.83
ASN AS37963 (ALIBABA-CN-NET Hangzhou Alibaba Advertising Co.,Ltd., CN)
Provider Alibaba Cloud
Data source: rdap (0.3s)

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

A
HTTP Probe Timing
Total 701 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
282 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
139 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
141 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
701 ms
Total Time Total request time from DNS lookup through full response.
702 ms

Connection waterfall

DNS Lookup 282 ms TCP Connect 139 ms TLS Handshake 141 ms Server Processing 139 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback