Skip to content
https://www.mistral.ai

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
91
GRADE
A
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
6 PASS 3 REVIEW
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.mistral.ai/
200https://mistral.ai/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://www.mistral.ai/ https://mistral.ai/

Consistent

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

Certificate validity

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

Recommended actions

  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • 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
Cloudflare
REVIEW
Cloudflare
Info::
Site is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: 9e8bd158bd0bd0ba-CDG
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9e8bd158bd0bd0ba-CDG
A
DNS Records
2 A records, 37 ms lookup
PASS
2 A records, 37 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 172.66.2.203, 162.159.142.207
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:7::2c3, 2a06:98c1:58::2c3
Info::
No NS records found
Info::
No MX records — email not configured via DNS
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 37 ms
Got: 37 ms
A172.66.2.203, 162.159.142.207
AAAA2606:4700:7::2c3, 2a06:98c1:58::2c3
CNAME
NS
MX
TXT
CAALookup not available with standard resolver
Resolved in 37 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.

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

A
Redirect Chain
1 redirect(s), 419 ms total
PASS
1 redirect(s), 419 ms total
Info::
Single redirect
Got: https://www.mistral.ai → https://mistral.ai/ (301)
Info::
WWW normalization redirect

https://www.mistral.ai

59 ms · HTTP/1.1

301

https://mistral.ai/

360 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.mistral.ai30159 msHTTP/1.1cloudflare
2https://mistral.ai/200360 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
IPv6 is configured and reachable at 2606:4700:7::2c3, 2a06:98c1:58::2c3
Got: 17 ms connect
IPv6 Ready
AAAA Records 2606:4700:7::2c3, 2a06:98c1:58::2c3 Connection Reachable (17 ms)
A+
Crawlability
robots.txt present, sitemap with 98 URLs
PASS
robots.txt present, sitemap with 98 URLs
Info::
robots.txt is present
Got: 22 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 98 entries
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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 22 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
Allow: /
A+
Domain Intelligence
mistral.ai — via Cloudflare, Inc, 6 years, 11 months old
PASS
mistral.ai — via Cloudflare, Inc, 6 years, 11 months old
Info::
Domain registered until May 15, 2029 (3 years, 1 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: Cloudflare, Inc
Domain expiry

1038 days

May 15, 2029

SSL certificate

85 days

Issued by Google Trust Services

Domain age

6 years, 11 months

Registered May 15, 2019

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:7::2c3

Registrar

Cloudflare, Inc

Lock status unknown 2 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
Registrar Cloudflare, Inc
Created May 15, 2019 (6 years, 11 months ago)
Expires May 15, 2029 (3 years, 1 months)
Last Updated October 26, 2025
Name Servers ivan.ns.cloudflare.com, ada.ns.cloudflare.com
DNSSEC Not enabled
Registrant DATA REDACTED
Hosting
IP Address 2606:4700:7::2c3
Data source: rdap (0.8s)

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

A+
HTTP Probe Timing
Total 87 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
31 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.
22 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
88 ms
Total Time Total request time from DNS lookup through full response.
88 ms

Connection waterfall

DNS Lookup 31 ms TCP Connect 17 ms TLS Handshake 22 ms Server Processing 18 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