Skip to content
https://justwatch.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
81
GRADE
B
FIX
0
REVIEW
5
PASS
4
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
4 PASS 5 REVIEW
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
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 23 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

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 23 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow:
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://justwatch.com/ https://justwatch.com:443/

Consistent

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

Certificate validity

45
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
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, 40 ms lookup
PASS
1 A records, 40 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 34.110.236.186
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-707.awsdns-24.net, ns-449.awsdns-56.com, ns-cloud-a2.googledomains.com, ns-cloud-a1.googledomains.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: 40 ms
Got: 40 ms
A34.110.236.186
AAAA
CNAME
NSns-707.awsdns-24.net, ns-449.awsdns-56.com, ns-cloud-a2.googledomains.com, ns-cloud-a1.googledomains.com
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 alt4.aspmx.l.google.com
10 alt3.aspmx.l.google.com
TXT
anthropic-domain-verification-qjkzd3=boW2woC1RdeWkbcyLDLQf3MK8
google-site-verification=YUnmJhmeyQn41307nSSIkwbF0DdSxQuWxUjioZ4s-5U
have-i-been-pwned-verification=73a4fb06907e95cc9ffd2d2e5bdc9522
SPF v=spf1 mx include:bounces.google.com include:_spf.google.com include:amazonses.c...
google-site-verification=4eBTNBm4L6RaWdF8V51EHZajskAMgXYAg81iRXJqumQ
firebase=justwatch-apps-beta
google-site-verification=8MXBeDtk0hQT8T5F0ZWGVMqzpJaTCLNkfLsJqX99jMY
cdn.webflow.com
MS=815C755123894661FA94B5CF470E8F17DC172B80
google-site-verification=Jfi-kWZGfMThWJUe03ArKJIqnMC2OHKpSJDyFb8H8ds
google-site-verification=xQ_zsxro8Tb3IDeIxPOiMqWLKs6VB8OM62iT1sRbPpU
google-site-verification=d45L0IuQrH_y-czGBBOq0ZsYK6Kji-aU8-XHy5i0kss
google-site-verification=JfGSHSBLAbI0idkFZ5f0ZxSGN1Lwfs2XZ3Psopm1-Wg
pinterest-site-verification=7d3beb7c2d84bbca753c06255f1bb520
enjoy hacking with dns? we search for curious minds! => talent.justwatch.com <=
google-site-verification=CHKqnMcFfsFExR3ztXfx6D-poBJW8bJfOxu_K3RvNl0
CAALookup not available with standard resolver
Resolved in 40 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
Redirect Chain
1 redirect(s), 200 ms total
PASS
1 redirect(s), 200 ms total
Info::
Single redirect
Got: https://justwatch.com → https://www.justwatch.com/ (301)
Info::
WWW normalization redirect

https://justwatch.com

77 ms · HTTP/1.1

301

https://www.justwatch.com/

122 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://justwatch.com30177 msHTTP/1.1Google Frontend
2https://www.justwatch.com/200122 msHTTP/1.1Google Frontend

See the visual redirect chain in the HTTP Probe tab →

A
Domain Intelligence
justwatch.com — via INWX GmbH, 23 years, 2 months old, hosted on Google Cloud
PASS
justwatch.com — via INWX GmbH, 23 years, 2 months old, hosted on Google Cloud
Warning::
Domain expires in 41 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Jun 3, 2026
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: INWX GmbH
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

EXPIRED

June 3, 2026

SSL certificate

45 days

Issued by Google Trust Services

Domain age

23 years, 2 months

Registered June 3, 2003

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Google Cloud

ASN AS396982

34.110.236.186

Registrar

INWX GmbH

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Domain has EXPIRED — renew immediately to avoid total site outage
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar INWX GmbH
Created June 3, 2003 (23 years, 2 months ago)
Expires June 3, 2026 (1 months)
Last Updated June 4, 2025
Name Servers ns-449.awsdns-56.com, ns-707.awsdns-24.net, ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com
DNSSEC Not enabled
Hosting
IP Address 34.110.236.186
ASN AS396982 (GOOGLE-CLOUD-PLATFORM - Google LLC, US)
Provider Google Cloud
Data source: rdap (0.3s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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 116 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
32 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.
33 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
116 ms
Total Time Total request time from DNS lookup through full response.
117 ms

Connection waterfall

DNS Lookup 32 ms TCP Connect 16 ms TLS Handshake 33 ms Server Processing 35 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