Skip to content
https://bluestacks.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
3
PASS
6
INFO
0
Probed from Sao Paulo, Brazil
301 Moved Permanently
Checks
9
6 PASS 3 REVIEW
B
Redirect Chain
2 redirect(s), 361 ms total
REVIEW
2 redirect(s), 361 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.bluestacks.com/

https://bluestacks.com

176 ms · HTTP/1.1

301

https://www.bluestacks.com/

140 ms · HTTP/1.1

302

https://www.bluestacks.com/pt-br/index.h...

45 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://bluestacks.com301176 msHTTP/1.1AmazonS3
2https://www.bluestacks.com/302140 msHTTP/1.1CloudFront
3https://www.bluestacks.com/pt-br/index.h...20045 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
268 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

268
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
4 A records, 42 ms lookup
PASS
4 A records, 42 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 108.139.113.102, 108.139.113.64, 108.139.113.77, 108.139.113.62
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1251.awsdns-28.org, ns-1987.awsdns-56.co.uk, ns-34.awsdns-04.com, ns-829.awsdns-39.net
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: 42 ms
Got: 42 ms
A108.139.113.102, 108.139.113.64, 108.139.113.77, 108.139.113.62
AAAA—
CNAME—
NSns-1251.awsdns-28.org, ns-1987.awsdns-56.co.uk, ns-34.awsdns-04.com, ns-829.awsdns-39.net
MX
10 aspmx.l.google.com
20 alt1.aspmx.l.google.com
30 alt2.aspmx.l.google.com
40 aspmx2.googlemail.com
50 aspmx3.googlemail.com
TXT
MS=4B0BCD2FF4B2A0B7D74A62DE1E265B88E3F04E83
MS=ms35639149
MS=ms40774375
_1rnmn174gmf5likcp39atlojzq2jgtp
google-site-verification=-VLyuSvfhncNZZ1yWzNGd1QMQF8ScIriUploxGOmuDE
google-site-verification=E9GBCt1VGWm1vI_NAKCOglIxlK3c1FoQQJolqlKKoFc
google-site-verification=JjDEOFzguXkOdTsB0WJlsuqEL3KnmCeMY4sqcTJOFUk
google-site-verification=pyvUW3E-6GDmYp9vShgGWU_COOgjVIpDkAwrscCLzlA
SPF v=spf1 include:sendgrid.net include:mail.zendesk.com include:servers.mcsv.net in...
CAALookup not available with standard resolver
Resolved in 42 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 258 URLs
PASS
robots.txt present, sitemap with 258 URLs
Info::
robots.txt is present
Got: 1208 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 258 entries
Info::
Sitemap index with 258 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1208 B Sitemaps referenced 1 User-agents Yandex, Baiduspider, facebookexternalhit, Yeti, * Blocking No — crawling allowed
User-agent: Yandex
Allow: /ru/
Allow: /download.html
Allow: /ru/blog/
Allow: /tr/
Disallow: /
Clean-param: p&z&u */index.html

User-agent: Baiduspider
Disallow: /

User-agent: facebookexternalhit
Allow: /ly/

User-agent: Yeti
Allow: /
Allow: /sitemap-naver.xml
Disallow: /tw/
Disallow: /vi/
Disallow: /tr/
Disallow: /th/
Disallow: /ru/
Disallow: /pt-br/
Disallow: /pl/
Disallow: /ms/
Disallow: /ja/
Disallow: /it/
Disallow: /id/
Disallow: /fr/
Disallow: /es/
Disallow: /de/
Disallow: /ar/

User-agent: *

Disallow: /wp-content/plugins/
Disallow: /wp-admin/
Disallow: /feed/
Disallow: /trackback/
Disallow: /xmlrpc.php
Disallow: /readme.html
Disallow: /json/
Disallow: /banner_app/
Disallow: /tw/banner_app/
Disallow: /ja/banner_app/
Disallow: /ko/banner_app/
Disallow: /th/banner_app/
Disallow: /ru/banner_app/
Disallow: /es/banner_app/
Disallow: /fr/banner_app/
Disallow: /pt-br/banner_app/
Disallow: /it/banner_app/
Disallow: /de/banner_app/
Disallow: /vi/banner_app/
Disallow: /id/banner_app/
Disallow: /ms/banner_app/
Disallow: /nl/banner_app/
Disallow: /pl/banner_app/
Disallow: /ar/banner_app/
Disallow: /search/
# Disallow: /campaign/

Allow: /

sitemap: https://www.bluestacks.com/sitemap_index.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 258 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.bluestacks.com/
200https://bluestacks.com/

Preferred variant: non-www

HTTP → HTTPS

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

Consistent

A+
Domain Intelligence
bluestacks.com — via GoDaddy.com, LLC, 15 years, 8 months old, hosted on AWS
PASS
bluestacks.com — via GoDaddy.com, LLC, 15 years, 8 months old, hosted on AWS
Info::
Domain registered until Oct 27, 2032 (6 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: 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: AWS
Got: AS16509
Domain expiry

2328 days

October 27, 2032

SSL certificate

268 days

Issued by Amazon

Domain age

15 years, 8 months

Registered October 27, 2010

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

13.225.107.59

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 October 27, 2010 (15 years, 8 months ago)
Expires October 27, 2032 (6 years, 7 months)
Last Updated October 22, 2023
Name Servers ns-1251.awsdns-28.org, ns-1987.awsdns-56.co.uk, ns-34.awsdns-04.com, ns-829.awsdns-39.net
DNSSEC Not enabled
Hosting
IP Address 13.225.107.59
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.7s)

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

Connection waterfall

DNS Lookup 11 ms TCP Connect 1 ms TLS Handshake 6 ms Server Processing 7 ms Content Transfer 0 ms
A+
CDN & Delivery
AWS CloudFront (Hit from cloudfront)
PASS
AWS CloudFront (Hit from cloudfront)
Info::
Site is served via AWS CloudFront CDN (edge: GRU3-P13)
Got: x-amz-cf-id: hEg6nwqxe4V-WXrb60dBGvnIIZFZ5dxWiqYmdn7MCkbtkjhhliiUbw==
Info::
CDN cache status: Hit from cloudfront
CDN Detected: AWS CloudFront
Provider AWS CloudFront Cache Status Hit from cloudfront Evidence x-amz-cf-id: hEg6nwqxe4V-WXrb60dBGvnIIZFZ5dxWiqYmdn7MCkbtkjhhliiUbw==
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback