Skip to content
https://acronis.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Madrid, Spain
302 Found
Checks
9
5 PASS 3 REVIEW 1 FIX
D
Redirect Chain
Action
3 redirect(s), 533 ms total
FIX
3 redirect(s), 533 ms total
Warning::
3 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://acronis.com
Info::
Redirect overhead: 533 ms total
Got: 533 ms

https://acronis.com

141 ms · HTTP/1.1

302

https://www.acronis.com/

174 ms · HTTP/1.1

302

https://www.acronis.com/en-us/

107 ms · HTTP/1.1

301

https://www.acronis.com/en/

112 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://acronis.com302141 msHTTP/1.1nginx
2https://www.acronis.com/302174 msHTTP/1.1nginx
3https://www.acronis.com/en-us/301107 msHTTP/1.1nginx
4https://www.acronis.com/en/200112 msHTTP/1.1nginx

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
223 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • 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
Google Cloud CDN
REVIEW
Google Cloud CDN
Info::
Site is served via Google Cloud CDN CDN
Got: via: 1.1 google
CDN Detected: Google Cloud CDN
Provider Google Cloud CDN Evidence via: 1.1 google
A+
DNS Records
1 A records, 28 ms lookup
PASS
1 A records, 28 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 34.120.97.237
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-809.awsdns-37.net, ns-445.awsdns-55.com, ns-1700.awsdns-20.co.uk, ns-1134.awsdns-13.org
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::
SPF record present in TXT
Info::
DNS resolution time: 28 ms
Got: 28 ms
A34.120.97.237
AAAA—
CNAME—
NSns-809.awsdns-37.net, ns-445.awsdns-55.com, ns-1700.awsdns-20.co.uk, ns-1134.awsdns-13.org
MX
0 acronis-com.mail.protection.outlook.com
TXT
google-site-verification=W9gEtUq0zBrZwjuoEifQAvkqfjGcym_CdeZTtwyKLG0
SPF v=spf1 mx include:_spf1.acronis.com include:mktomail.com include:_spf.salesforce...
teamviewer-sso-verification=739bbee559854bdb80e9939d00510470
m_verify=b666ba0552
atlassian-domain-verification=RMd0J9VHZO4cswqtUWk00SirIuFGQanssPhyUWmwUnOonpAAsW...
h1-domain-verification=BVSjuCCBwRSMxvEmaxxthzHU9gRVBrapRXqKz18Dg9pYpL37
anthropic-domain-verification-6rracp=5jvVkUwtUQlp8iqyUklFztKiM
_9t7gr1ggy2p4suuzp9ipew47ia6goxn
parallels-domain-verification=92a90b23e8b04c64a74c6c0b035845b11e849c620f7745eb9e...
windsurf-verification=z8Ao0xMQBmU2rlCWg9S5c_N2RY_6CkEx2S6Is5iEyGk=
1password-site-verification=WR2Z23X7NZAHLKCLZWS63KTOT4
MS=ms64092276
mgverify=6d3b5ecfd2b2bc9d4a80c50b916703c98b3877fee984ebc3a77bda48827a737c
bw=F8wLudwV2wv5ptEe1Z1A+Cnm21WClQ+1XyXjztcD/FjN
openai-domain-verification=dv-ydnukeiExZTGdsG6bsWqn4iz
CAALookup not available with standard resolver
Resolved in 28 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.

A+
Crawlability
robots.txt present, sitemap with 19 URLs
PASS
robots.txt present, sitemap with 19 URLs
Info::
robots.txt is present
Got: 1479 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 references sitemap
robots.txt 200 OK
Size 1479 B Sitemaps referenced 3 User-agents Twitterbot, dotbot, * Blocking No — crawling allowed
#
# robots.txt
#
# This file is to prevent the crawling and indexing of certain parts
# of your site by web crawlers and spiders run by sites like Yahoo!
# and Google. By telling these "robots" where not to go on your site,
# you save bandwidth and server resources.
#
# This file will be ignored unless it is at the root of your host:
# Used:    http://example.com/robots.txt
# Ignored: http://example.com/site/robots.txt
#
# For more information about the robots.txt standard, see:
# http://www.robotstxt.org/robotstxt.html
#
# For syntax checking, see:
# http://www.frobee.com/robots-txt-check

User-agent: Twitterbot
Disallow:

User-agent: dotbot
Disallow: /


User-agent: *
# Directories
Disallow: /misc/
Disallow: /modules/
Disallow: /includes/
Disallow: /*/?q=admin/
Disallow: /inapp/
Disallow: /in-app-browser/
Disallow: /?sort=

# RKG recommendations
Disallow: /*/my/
Disallow: /*/search/
Disallow: /*/admin/
# SEO
Disallow: *?oem=
Disallow: *?language=
Disallow: *?s=
Disallow: *?rr=
Disallow: */promo/bcmebook/
Disallow: */mag/ita/

# Disallow resources facets
Disallow: /*/resource-center/*/language/
Disallow: /*/resource-center/*.jsp/

# Disallow merged locales
Disallow: /en-au/
Disallow: /en-ca/
Disallow: /en-in/
Disallow: /de-ch/
Disallow: /fr-ca/


Sitemap:https://websiteapi.acronis.com/api/core/sitemaps/
Sitemap:https://websiteapi.acronis.com/api/blog/sitemaps/
Sitemap:https://websiteapi.acronis.com/api/resources/sitemaps/

Host: https://www.acronis.com/
sitemap.xml 200 OK
Type Sitemap Index URLs 19 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.acronis.com/
200https://acronis.com/

Preferred variant: non-www

HTTP → HTTPS

301http://acronis.com/ → https://acronis.com:443/

Consistent

A+
Domain Intelligence
acronis.com — via GoDaddy.com, LLC, 25 years, 7 months old, hosted on Google Cloud
PASS
acronis.com — via GoDaddy.com, LLC, 25 years, 7 months old, hosted on Google Cloud
Info::
Domain registered until Jan 9, 2034 (7 years, 9 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: GoDaddy.com, LLC
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: Google Cloud
Got: AS396982
Domain expiry

2732 days

January 9, 2034

SSL certificate

223 days

Issued by DigiCert Inc

Domain age

25 years, 7 months

Registered January 9, 2001

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Google Cloud

ASN AS396982

34.120.97.237

Registrar

GoDaddy.com, LLC

Unlocked 4 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 GoDaddy.com, LLC
Created January 9, 2001 (25 years, 7 months ago)
Expires January 9, 2034 (7 years, 9 months)
Last Updated November 3, 2025
Name Servers ns-1134.awsdns-13.org, ns-1700.awsdns-20.co.uk, ns-445.awsdns-55.com, ns-809.awsdns-37.net
DNSSEC Not enabled
Hosting
IP Address 34.120.97.237
ASN AS396982 (GOOGLE-CLOUD-PLATFORM - Google LLC, US)
Provider Google 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 178 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
38 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
17 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
24 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
178 ms
Total Time Total request time from DNS lookup through full response.
178 ms

Connection waterfall

DNS Lookup 38 ms TCP Connect 17 ms TLS Handshake 24 ms Server Processing 100 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