Skip to content
https://cirquedusoleil.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from New York, United Stated
301 Moved Permanently
Checks
9
5 PASS 3 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.

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.cirquedusoleil.com/
200https://cirquedusoleil.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

B
TLS Certificate Expiry & Recommendations
260 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

260
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
DNS Records
1 A records, 430 ms lookup
PASS
1 A records, 430 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 40.79.66.214
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: ns1-05.azure-dns.com, ns2-05.azure-dns.net, ns3-05.azure-dns.org, ns4-05.azure-dns.info
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
Warning::
DNS resolution is slow (430 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 430 ms
A40.79.66.214
AAAA—
CNAME—
NSns1-05.azure-dns.com, ns2-05.azure-dns.net, ns3-05.azure-dns.org, ns4-05.azure-dns.info
MX
0 cirquedusoleil-com.mail.protection.outlook.com
TXT
SPF v=spf1 mx include:spf.protection.outlook.com include:spf-cds1.cirquedusoleil.com...
atlassian-domain-verification=QDN9Dij30MEXf71fqh/P7XDESb9MswjbgzcCZM2mSsGMrub+5k...
adobe-idp-site-verification=974ab14ab3358282ad47f7a50f47b1fcbf38ab9a496516f8d00f...
docusign=560cb051-d3f3-4258-ba02-78d59d806b57
amazonses:YofiFQmhWh0F1HxYVJgdUknbokwNDDCVggXJ9MVZ6oU=
2724244f-fec0-4f26-b91e-35cf0d536676
MS=ms55836318
facebook-domain-verification=aivemq95e28qsmxphvbf7f5i8hnd0c
miro-verification=ec0c0c4b59da1ec1418f1451cbd6ca14f44c7729
logmein-verification-code=061f4400-b1bd-4145-b9c8-17168beb6ca6
google-site-verification=TI6xZV1EQZwJ7yImANGcScR5WIDZeQWm1194x942j48
canva-site-verification=dpAZICQNSFM5fSWN9sY1Lw
pardot1047413=11ad10dcbc8ade162767ea1fa8d3604409286f5e44ed94c6bf3841be1d23c306
klaviyo-site-verification=X99h2z
twilio-domain-verification=a1dfe5dcc22c1900713034c9dbc192a7
knowbe4-site-verification=a605e27441871fd8c24489cc581058a4
1password-site-verification=IM4I7SYWHBEG5OHMXGAVEJC6FY
reachdesk-verification=WeRbH4EYWKXLAOoomQn9z0UZVB1Vfpb32Py7EST0CfAGUhv9a2VtqvYwm...
gld1dreccntqt4i266nkus72uq
google-site-verification=Uelbj13GlvYXe-qwjE8Ld4ihsk1Atu3SlBhVTHlqD5c
logmein-verification-code=J3tdBuoDRVDk0eKGpDn5xW447
CAALookup not available with standard resolver
Resolved in 430 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
1 redirect(s), 685 ms total
PASS
1 redirect(s), 685 ms total
Info::
Single redirect
Got: https://cirquedusoleil.com → https://www.cirquedusoleil.com/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 685 ms total
Got: 685 ms

https://cirquedusoleil.com

58 ms · HTTP/1.1

301

https://www.cirquedusoleil.com/

627 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://cirquedusoleil.com30158 msHTTP/1.1Microsoft-IIS/10.0
2https://www.cirquedusoleil.com/200627 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 633 URLs
PASS
robots.txt present, sitemap with 633 URLs
Info::
robots.txt is present
Got: 416 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 633 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 416 B Sitemaps referenced 6 User-agents * Blocking No — crawling allowed
User-agent: *

Disallow: /404

Disallow: /Error500

Disallow: /*sitecore


Sitemap: https://www.cirquedusoleil.com/sitemap.xml

Sitemap: https://blog.cirquedusoleil.com/sitemap.xml

Sitemap: https://www.cirquedusoleil.com/city-sitemap.xml

Sitemap: https://www.cirquedusoleil.com/shows-sitemap.xml

Sitemap: https://www.cirquedusoleil.com/press/sitemap.xml

Sitemap: https://www.cirquedusoleil.com/deals-sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 633 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
cirquedusoleil.com — via GoDaddy.com, LLC, 30 years, 7 months old, hosted on Microsoft Azure
PASS
cirquedusoleil.com — via GoDaddy.com, LLC, 30 years, 7 months old, hosted on Microsoft Azure
Info::
Domain registered until Feb 3, 2027 (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: Microsoft Azure
Got: AS8075
Domain expiry

232 days

February 3, 2027

SSL certificate

260 days

Issued by GoDaddy.com, Inc.

Domain age

30 years, 7 months

Registered February 2, 1996

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Microsoft Azure

ASN AS8075

40.79.66.214

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 February 2, 1996 (30 years, 7 months ago)
Expires February 3, 2027 (9 months)
Last Updated September 11, 2022
Name Servers ns1-05.azure-dns.com, ns2-05.azure-dns.net, ns3-05.azure-dns.org, ns4-05.azure-dns.info
DNSSEC Not enabled
Hosting
IP Address 40.79.66.214
ASN AS8075 (MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US)
Provider Microsoft Azure
Data source: rdap (0.1s)

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 188 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
128 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
12 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
34 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
188 ms
Total Time Total request time from DNS lookup through full response.
189 ms

Connection waterfall

DNS Lookup 128 ms TCP Connect 12 ms TLS Handshake 34 ms Server Processing 16 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