Skip to content
https://turbo.build

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
89
GRADE
B
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from Sao Paulo, Brazil
301 Moved Permanently
Checks
9
6 PASS 3 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
87 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

87
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
Vercel
REVIEW
Vercel
Info::
Site is served via Vercel CDN
Got: x-vercel-id: gru1::lkxkk-1775328173514-10c5a66a56b6
CDN Detected: Vercel
Provider Vercel Evidence x-vercel-id: gru1::lkxkk-1775328173514-10c5a66a56b6
A+
DNS Records
2 A records, 130 ms lookup
PASS
2 A records, 130 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 64.239.123.193, 64.239.123.65
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: ns2.vercel-dns.com, ns1.vercel-dns.com
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: 130 ms
Got: 130 ms
A64.239.123.193, 64.239.123.65
AAAA
CNAME
NSns2.vercel-dns.com, ns1.vercel-dns.com
MX
TXT
google-site-verification=8l6xfIvxDy7ZI32TFfrv8S3haLxbpVPY4qmc9sIvAIY
google-site-verification=v_ZX7rc5Yh75SRolZBMB8GbsAeZLXDtOH4laVhVbyHY
google-site-verification=OSqDDkqpfyXM7i1SMHO_kfF6Yqc7JC-2oBYxAAJOgbk
google-site-verification=8SKAcO7YVybXwhZHNeoWhcfLTJhNNchNQbBzy-uVKmM
CAALookup not available with standard resolver
Resolved in 130 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), 488 ms total
PASS
1 redirect(s), 488 ms total
Info::
Single redirect
Got: https://turbo.build → https://turborepo.dev/ (301)
Info::
Cross-domain redirect detected

https://turbo.build

74 ms · HTTP/1.1

301

https://turborepo.dev/

414 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://turbo.build30174 msHTTP/1.1Vercel
2https://turborepo.dev/200414 msHTTP/1.1Vercel

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 138 URLs
PASS
robots.txt present, sitemap with 138 URLs
Info::
robots.txt is present
Got: 67 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 138 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 67 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-Agent: *
Allow: /

Sitemap: https://turborepo.dev/sitemap.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: non-www)
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

301https://www.turbo.build/
200https://turbo.build/

Preferred variant: non-www

HTTP → HTTPS

308http://turbo.build/ https://turbo.build/

Use 301 (permanent) instead of 302 (temporary)

A+
Domain Intelligence
turbo.build — via Tucows.com Co., 3 years, 7 months old, hosted on AWS
PASS
turbo.build — via Tucows.com Co., 3 years, 7 months old, hosted on AWS
Info::
Domain registered until Sep 9, 2026 (5 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: Tucows.com Co.
Info::
Hosting: AWS
Got: AS16509
Domain expiry

60 days

September 9, 2026

SSL certificate

87 days

Issued by Let's Encrypt

Domain age

3 years, 7 months

Registered September 9, 2022

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

64.239.123.65

Registrar

Tucows.com Co.

Lock status unknown 2 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 Tucows.com Co.
Created September 9, 2022 (3 years, 7 months ago)
Expires September 9, 2026 (5 months)
Last Updated October 8, 2025
Name Servers ns1.vercel-dns.com, ns2.vercel-dns.com
DNSSEC Not enabled
Hosting
IP Address 64.239.123.65
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (1.7s)

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

Connection waterfall

DNS Lookup 55 ms TCP Connect 1 ms TLS Handshake 6 ms Server Processing 17 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