Skip to content
https://www.strapi.io

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
0
REVIEW
5
PASS
4
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
4 PASS 5 REVIEW
B
DNS Records
2 A records, 31 ms lookup
REVIEW
2 A records, 31 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 199.60.103.29, 199.60.103.227
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:2c40::c73c:671d, 2606:2c40::c73c:67e3
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: 6893032.group32.sites.hubspot.net
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: 31 ms
Got: 31 ms
A199.60.103.29, 199.60.103.227
AAAA2606:2c40::c73c:671d, 2606:2c40::c73c:67e3
CNAME6893032.group32.sites.hubspot.net
NS
MX
TXT
CAALookup not available with standard resolver
Resolved in 31 ms

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

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)

B
Redirect Chain
1 redirect(s), 1230 ms total
REVIEW
1 redirect(s), 1230 ms total
Info::
Single redirect
Got: https://www.strapi.io → https://strapi.io/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1230 ms total
Got: 1230 ms

https://www.strapi.io

67 ms · HTTP/1.1

301

https://strapi.io/

1163 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.strapi.io30167 msHTTP/1.1cloudflare
2https://strapi.io/2001163 msHTTP/1.1envoy

See the visual redirect chain in the HTTP Probe tab →

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.strapi.io/
200https://strapi.io/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://www.strapi.io/ https://www.strapi.io/

Consistent

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

Certificate validity

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

Recommended actions

  • Add includeSubDomains to the HSTS directive
  • 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
B
CDN & Delivery
Cloudflare
REVIEW
Cloudflare
Info::
Site is served via Cloudflare CDN (edge: MAD)
Got: cf-ray: 9e8bcd50fd84cc3c-MAD
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9e8bcd50fd84cc3c-MAD
A+
IPv6 Readiness
IPv6 reachable (1 ms)
PASS
IPv6 reachable (1 ms)
Info::
IPv6 is configured and reachable at 2606:2c40::c73c:671d, 2606:2c40::c73c:67e3
Got: 1 ms connect
IPv6 Ready
AAAA Records 2606:2c40::c73c:671d, 2606:2c40::c73c:67e3 Connection Reachable (1 ms)
A
Crawlability
robots.txt present, sitemap with 0 URLs
PASS
robots.txt present, sitemap with 0 URLs
Info::
robots.txt is present
Got: 165 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Warning::
sitemap.xml is empty — no URLs found
An empty sitemap provides no value. Add <url> entries for your pages.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

An empty sitemap provides no value. Add <url> entries for your pages.

Why this matters

An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.

Learn more

Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.

Source: Google Search Central / sitemaps.org

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 165 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /_hcms/preview/
Disallow: /hs/manage-preferences/
Disallow: /hs/preferences-center/
Disallow: /*?*hs_preview=*
Disallow: /*?*hsCacheBuster=*

sitemap.xml 200 OK
Type URL Set URLs 0 entries Valid XML Yes
A+
Domain Intelligence
strapi.io — via Gandi SAS, 10 years, 8 months old, hosted on AWS
PASS
strapi.io — via Gandi SAS, 10 years, 8 months old, hosted on AWS
Info::
Domain registered until Sep 21, 2026 (5 months remaining)
Info::
Registrar: Gandi SAS
Info::
Hosting: AWS
Got: AS16509
Domain expiry

71 days

September 21, 2026

SSL certificate

42 days

Issued by Google Trust Services

Domain age

10 years, 8 months

Registered September 21, 2015

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

3.165.190.33

Registrar

Gandi SAS

Lock status unknown 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
Registrar Gandi SAS
Created September 21, 2015 (10 years, 8 months ago)
Expires September 21, 2026 (5 months)
Last Updated August 22, 2025
Name Servers ns-1294.awsdns-33.org, ns-1706.awsdns-21.co.uk, ns-556.awsdns-05.net, ns-443.awsdns-55.com
Registrant Strapi Solutions
Hosting
IP Address 3.165.190.33
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: whois (1.2s)
A+
HTTP Probe Timing
Total 262 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
52 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.
13 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
263 ms
Total Time Total request time from DNS lookup through full response.
263 ms

Connection waterfall

DNS Lookup 52 ms TCP Connect 1 ms TLS Handshake 13 ms Server Processing 197 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