Skip to content
https://www.storyblok.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
91
GRADE
A
FIX
0
REVIEW
2
PASS
7
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
7 PASS 2 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
TLS Certificate Expiry & Recommendations
245 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • 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, 46 ms lookup
PASS
4 A records, 46 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 143.204.55.109, 143.204.55.14, 143.204.55.115, 143.204.55.25
Info::
No IPv6 (AAAA) records
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: 46 ms
Got: 46 ms
A143.204.55.109, 143.204.55.14, 143.204.55.115, 143.204.55.25
AAAA
CNAME
NS
MX
TXT
CAALookup not available with standard resolver
Resolved in 46 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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://www.storyblok.com

https://www.storyblok.com

197 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.storyblok.com200197 msHTTP/1.1Netlify
A+
Crawlability
robots.txt present, sitemap with 2437 URLs
PASS
robots.txt present, sitemap with 2437 URLs
Info::
robots.txt is present
Got: 81 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 2437 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 81 B Sitemaps referenced 1 User-agents * Disallow: Blocking No — crawling allowed

  User-Agent: * Disallow:

  Sitemap: https://www.storyblok.com/sitemap-0.xml
  
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: www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

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

Preferred variant: www

HTTP → HTTPS

301http://www.storyblok.com/ https://www.storyblok.com/

Consistent

A+
Domain Intelligence
storyblok.com — via Amazon Registrar, Inc., 10 years, 9 months old, hosted on AWS
PASS
storyblok.com — via Amazon Registrar, Inc., 10 years, 9 months old, hosted on AWS
Info::
Domain registered until Aug 15, 2026 (4 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: Amazon Registrar, Inc.
Info::
Hosting: AWS
Got: AS16509
Domain expiry

63 days

August 15, 2026

SSL certificate

245 days

Issued by Amazon

Domain age

10 years, 9 months

Registered August 15, 2015

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

35.156.140.201

Registrar

Amazon Registrar, Inc.

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
  • Enable DNSSEC to protect visitors from DNS spoofing
Registrar Amazon Registrar, Inc.
Created August 15, 2015 (10 years, 9 months ago)
Expires August 15, 2026 (4 months)
Last Updated July 11, 2025
Name Servers ns-1499.awsdns-59.org, ns-1778.awsdns-30.co.uk, ns-450.awsdns-56.com, ns-924.awsdns-51.net
DNSSEC Not enabled
Hosting
IP Address 35.156.140.201
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.2s)

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

Connection waterfall

DNS Lookup 36 ms TCP Connect 31 ms TLS Handshake 35 ms Server Processing 328 ms Content Transfer 186 ms
A
CDN & Delivery
AWS CloudFront (Miss from cloudfront)
PASS
AWS CloudFront (Miss from cloudfront)
Info::
Site is served via AWS CloudFront CDN (edge: ZRH52-P1)
Got: x-amz-cf-id: pl1mqz7FW0x6Xm0Lxrytq_oS51DCxpYXHWftvwHrQvp3DNqe35Rt2A==
Info::
CDN cache status: Miss from cloudfront
CDN Detected: AWS CloudFront
Provider AWS CloudFront Cache Status Miss from cloudfront Evidence x-amz-cf-id: pl1mqz7FW0x6Xm0Lxrytq_oS51DCxpYXHWftvwHrQvp3DNqe35Rt2A==
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback