Skip to content
https://mubi.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
81
GRADE
B
FIX
2
REVIEW
2
PASS
5
INFO
0
Probed from Amsterdam, Netherlands
302 Found
Checks
9
5 PASS 2 REVIEW 2 FIX
F
Redirect Chain
Action
3 redirect(s), 1250 ms total
FIX
3 redirect(s), 1250 ms total
Warning::
3 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://mubi.com
Warning::
Redirect overhead: 1250 ms total
Got: 1250 ms

https://mubi.com

305 ms · HTTP/1.1

302

https://mubi.com/en/

289 ms · HTTP/1.1

308

https://mubi.com/en

302 ms · HTTP/1.1

302

https://mubi.com/en/nl

354 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://mubi.com302305 msHTTP/1.1
2https://mubi.com/en/308289 msHTTP/1.1
3https://mubi.com/en302302 msHTTP/1.1
4https://mubi.com/en/nl200354 msHTTP/1.1

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

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

Certificate validity

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

Recommended actions

  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • 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
3 A records, 122 ms lookup
PASS
3 A records, 122 ms lookup
Info::
Resolves to 3 IPv4 address(es)
Got: 34.194.20.107, 44.215.86.236, 100.50.172.226
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1496.awsdns-59.org, ns-1560.awsdns-03.co.uk, ns-226.awsdns-28.com, ns-784.awsdns-34.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: 122 ms
Got: 122 ms
A34.194.20.107, 44.215.86.236, 100.50.172.226
AAAA—
CNAME—
NSns-1496.awsdns-59.org, ns-1560.awsdns-03.co.uk, ns-226.awsdns-28.com, ns-784.awsdns-34.net
MX
1 aspmx.l.google.com
5 alt2.aspmx.l.google.com
5 alt1.aspmx.l.google.com
10 aspmx2.googlemail.com
10 aspmx3.googlemail.com
TXT
MS=ms97368111
THIS IS MANAGED BY TERRAFORM. MANUAL CHANGES WILL BE DISCARDED
_k670ajswdqbk3iicbu0yo74ud1dkla1
_wwsvo2t9oo1c4ztoti4nzq8n69l68m4
brevo-code:f3c96237cf908eaabb22e4221b7aedb3
facebook-domain-verification=2olb7r30vjw80adllzwfvlvh6owjtv
facebook-domain-verification=mg5alrgbguj2a2ylp1zv2q2dixe7je
google-site-verification=c-hsNjXZFadvLgN6RawQBiDbjsKbJJO1WEheFvMlljo
google-site-verification=qz_0epUOSpj2-LFc3pG2rTI6cXOoA8ZyHdwCEFkfkH8
google-site-verification=xaZONTQIPNB3mFYGN3JBTpVkrgeDO_707MmK5JGZ3A4
pinterest-site-verification=dcf4b6a23512a0383d5162f849f5fa6a
spf2.0/pra include:amazonses.com ?all
stripe-verification=1c0947943c8957717e6f2282b8687acf210075b1d46cd92460f4fcf0e016...
stripe-verification=de7015d7fd87b4862bdd375c4d49702a6f5c95a980268baabbd2b8b12437...
tiktok-developers-site-verification=1vUvv9RkZfMGpH2Qtkbcj10lkegmb0rV
SPF v=spf1 include:sendgrid.net include:_spf.google.com include:spf.mandrillapp.com ...
CAALookup not available with standard resolver
Resolved in 122 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 18 URLs
PASS
robots.txt present, sitemap with 18 URLs
Info::
robots.txt is present
Got: 884 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 18 entries
Info::
Sitemap index with 18 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 884 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
# See https://www.robotstxt.org/robotstxt.html for documentation on how to use the robots.txt file

User-Agent: *
Disallow: /login
Disallow: /search
Disallow: /users/
Disallow: */films/*/awards
Disallow: */awards-and-festivals/
Allow: /*awards-and-festivals/venice
Allow: /*awards-and-festivals/cannes
Allow: /*awards-and-festivals/oscars
Allow: /*awards-and-festivals/outfest
Allow: /*awards-and-festivals/berlinale
Allow: /*awards-and-festivals/asian-fas
Allow: /*awards-and-festivals/rotterdam
Allow: /*awards-and-festivals/istanbul
Allow: /*awards-and-festivals/london
Allow: /*awards-and-festivals/sundance
Allow: /*awards-and-festivals/sarajevo
Allow: /*awards-and-festivals/san-sebastian
Allow: /*awards-and-festivals/toronto

Disallow: /ro/
Disallow: /da/
Disallow: /nb/
Disallow: /pl/
Disallow: /sv/
Disallow: /ms/

Sitemap: https://feeds.mubi.com/sitemap.xml
crawl-delay: 5
sitemap.xml 200 OK
Type Sitemap Index URLs 18 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

301https://www.mubi.com/
200https://mubi.com/

Preferred variant: non-www

HTTP → HTTPS

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

Consistent

A+
Domain Intelligence
mubi.com — via Gandi SAS, 24 years old, hosted on AWS
PASS
mubi.com — via Gandi SAS, 24 years old, hosted on AWS
Info::
Domain registered until Aug 6, 2026 (3 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: Gandi SAS
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: AS14618
Domain expiry

25 days

August 6, 2026

SSL certificate

99 days

Issued by Amazon

Domain age

24 years

Registered August 6, 2002

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS14618

34.194.20.107

Registrar

Gandi SAS

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Gandi SAS
Created August 6, 2002 (24 years ago)
Expires August 6, 2026 (3 months)
Last Updated July 2, 2025
Name Servers ns-1496.awsdns-59.org, ns-1560.awsdns-03.co.uk, ns-226.awsdns-28.com, ns-784.awsdns-34.net
DNSSEC Not enabled
Hosting
IP Address 34.194.20.107
ASN AS14618 (AMAZON-AES - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.4s)

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

Connection waterfall

DNS Lookup 4 ms TCP Connect 94 ms TLS Handshake 96 ms Server Processing 108 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