Skip to content
https://cloudways.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
88
GRADE
B
FIX
0
REVIEW
4
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
5 PASS 4 REVIEW
B
Redirect Chain
2 redirect(s), 256 ms total
REVIEW
2 redirect(s), 256 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://www.cloudways.com/

https://cloudways.com

58 ms · HTTP/1.1

301

https://www.cloudways.com/

151 ms · HTTP/1.1

302

https://www.cloudways.com/es

47 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://cloudways.com30158 msHTTP/1.1cloudflare
2https://www.cloudways.com/302151 msHTTP/1.1cloudflare
3https://www.cloudways.com/es20047 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

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

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
TLS Certificate Expiry & Recommendations
293 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

293
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
B
CDN & Delivery
Cloudflare
REVIEW
Cloudflare
Info::
Site is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: 9f085507fadb0220-CDG
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9f085507fadb0220-CDG
A+
DNS Records
2 A records, 45 ms lookup
PASS
2 A records, 45 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.17.242.235, 104.17.241.235
Info::
No IPv6 (AAAA) records
Info::
5 nameserver(s) configured
Got: ns3.dnsmadeeasy.com, ns2.dnsmadeeasy.com, ns0.dnsmadeeasy.com, ns4.dnsmadeeasy.com, ns1.dnsmadeeasy.com
Info::
5 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
Info::
DNS resolution time: 45 ms
Got: 45 ms
A104.17.242.235, 104.17.241.235
AAAA—
CNAME—
NSns3.dnsmadeeasy.com, ns2.dnsmadeeasy.com, ns0.dnsmadeeasy.com, ns4.dnsmadeeasy.com, ns1.dnsmadeeasy.com
MX
1 aspmx.l.google.com
5 alt2.aspmx.l.google.com
5 alt1.aspmx.l.google.com
10 alt4.aspmx.l.google.com
10 alt3.aspmx.l.google.com
TXT
spycloud-domain-verification=a6ff367e-bb1b-450a-a415-d133125dfe71
google-site-verification=nV29whdht5OqLEZXy82IhZTvU-QYKQDv-oElqulBkE4
SPF v=spf1 include:mail.zendesk.com include:spf.mandrillapp.com include:stspg-custom...
google-site-verification=l-HbQ55ugAjJUvVTa1BNQxSCYH4VVt_J4qOO3ZMntp8
atlassian-domain-verification=WeMWPeYJlghQK1wf8WhNT4VYCAXexf7gz2Xf5A4beapGYxSR9F...
status-page-domain-verification=kt3s956crw03
unbounce=580444
ZOOM_verify_TOVnrGxV276nH0rbcNfwaK
mixpanel-domain-verify=85b26146-e35e-47d0-a5e7-a00871b95db3
unbounce543168
google-site-verification=t_Rd4KhMt3iTeeDCN6lXlOgTDBV2vhKDxJ-JxOXg-V0
MS=F42845CA376B7984345CE3F419DC0756FB5D67E9
CAALookup not available with standard resolver
Resolved in 45 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+
Crawlability
robots.txt present, sitemap with 2 URLs
PASS
robots.txt present, sitemap with 2 URLs
Info::
robots.txt is present
Got: 1462 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 2 entries
Info::
Sitemap index with 2 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1462 B Sitemaps referenced 8 User-agents *, GPTBot, Google-Extended, ChatGPT-User, ClaudeBot, Googlebot, PerplexityBot, SiteAuditBot, Pinterestbot, Gemini Blocking No — crawling allowed
User-agent: *
Disallow: /admin/
Disallow: /admin/*?*
Disallow: /admin/*?
Disallow: /ajax_content/
Disallow: /ajax_content/*?*
Disallow: /ajax_content/*?
Disallow: /blog/*?*
Disallow: /blog/*?
Disallow: /en/?*
Disallow: /en/?
Disallow: /en?
Disallow: /zdev/
Disallow: /zdev/*?*
Disallow: /zdev/*?
Disallow: /site/
Disallow: /site/*
Disallow: /site/*?*
Disallow: /site/*?
Disallow: /en/*?*
Disallow: /upload/cms/docs/*?*
Disallow: /blog/featured/
Disallow: /*?id=
Disallow: /blog/wp-content/plugins/sitepress-multilingual-cms/
Disallow: /cdn-cgi/


Sitemap: https://www.cloudways.com/en/sitemap.xml
Sitemap: https://www.cloudways.com/es/sitemap.xml
Sitemap: https://www.cloudways.com/br/sitemap.xml
Sitemap: https://www.cloudways.com/de/sitemap.xml
Sitemap: https://www.cloudways.com/pt/sitemap.xml
Sitemap: https://www.cloudways.com/blog/wp-sitemap.xml
Sitemap: https://www.cloudways.com/es/blog/wp-sitemap.xml
Sitemap: https://www.cloudways.com/pt/blog/wp-sitemap.xml



# ===========================
# Additional Allowed Bots
# ===========================

User-agent: GPTBot
Allow: /
Crawl-delay: 1

User-agent: ClaudeBot
Allow: /
Crawl-delay: 1

User-agent: Google-Extended
Allow: /

User-agent: Googlebot
Allow: /

User-agent: PerplexityBot
Allow: /
Crawl-delay: 1

User-agent: SiteAuditBot
Allow: /
Crawl-delay: 1

User-agent: Pinterestbot
Allow: /
Crawl-delay: 1

User-agent: Gemini
Allow: /
Crawl-delay: 1

User-agent: ChatGPT-User
Allow: /
Crawl-delay: 1
sitemap.xml 200 OK
Type Sitemap Index URLs 2 entries Valid XML Yes
Child Sitemaps:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

302https://www.cloudways.com/
200https://cloudways.com/

Preferred variant: non-www

HTTP → HTTPS

301http://cloudways.com/ → https://www.cloudways.com/

Consistent

A+
Domain Intelligence
cloudways.com — via NameCheap, Inc., 17 years, 8 months old, hosted on Cloudflare
PASS
cloudways.com — via NameCheap, Inc., 17 years, 8 months old, hosted on Cloudflare
Info::
Domain registered until Nov 3, 2031 (5 years, 7 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: NameCheap, Inc.
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: Cloudflare
Got: AS13335
Domain expiry

1939 days

November 3, 2031

SSL certificate

293 days

Issued by Sectigo Limited

Domain age

17 years, 8 months

Registered November 3, 2008

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS13335

104.17.242.235

Registrar

NameCheap, Inc.

Unlocked 5 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 NameCheap, Inc.
Created November 3, 2008 (17 years, 8 months ago)
Expires November 3, 2031 (5 years, 7 months)
Last Updated June 22, 2022
Name Servers ns0.dnsmadeeasy.com, ns1.dnsmadeeasy.com, ns2.dnsmadeeasy.com, ns3.dnsmadeeasy.com, ns4.dnsmadeeasy.com
DNSSEC Not enabled
Hosting
IP Address 104.17.242.235
ASN AS13335 (CLOUDFLARENET - Cloudflare, Inc., US)
Provider Cloudflare
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 110 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
51 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
16 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
23 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
110 ms
Total Time Total request time from DNS lookup through full response.
110 ms

Connection waterfall

DNS Lookup 51 ms TCP Connect 16 ms TLS Handshake 23 ms Server Processing 19 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