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

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
96
GRADE
A
FIX
0
REVIEW
1
PASS
8
INFO
0
Probed from Madrid, Spain
308 Permanent Redirect
Checks
9
8 PASS 1 REVIEW
B
TLS Certificate Expiry & Recommendations
62 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

62
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
A
DNS Records
2 A records, 42 ms lookup
PASS
2 A records, 42 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.21.86.169, 172.67.222.101
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:3037::6815:56a9, 2606:4700:3030::ac43:de65
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: 42 ms
Got: 42 ms
A104.21.86.169, 172.67.222.101
AAAA2606:4700:3037::6815:56a9, 2606:4700:3030::ac43:de65
CNAME
NS
MX
TXT
CAALookup not available with standard resolver
Resolved in 42 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), 232 ms total
PASS
1 redirect(s), 232 ms total
Info::
Single redirect
Got: https://www.timescale.com → https://www.tigerdata.com/ (308)
Info::
Cross-domain redirect detected

https://www.timescale.com

94 ms · HTTP/1.1

308

https://www.tigerdata.com/

138 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.timescale.com30894 msHTTP/1.1cloudflare
2https://www.tigerdata.com/200138 msHTTP/1.1Vercel

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (16 ms)
PASS
IPv6 reachable (16 ms)
Info::
IPv6 is configured and reachable at 2606:4700:3037::6815:56a9, 2606:4700:3030::ac43:de65
Got: 16 ms connect
IPv6 Ready
AAAA Records 2606:4700:3037::6815:56a9, 2606:4700:3030::ac43:de65 Connection Reachable (16 ms)
A+
Crawlability
robots.txt present, sitemap with 345 URLs
PASS
robots.txt present, sitemap with 345 URLs
Info::
robots.txt is present
Got: 176 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 345 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 176 B Sitemaps referenced 3 User-agents * Blocking No — crawling allowed
User-Agent: *
Allow: /
Sitemap: https://www.tigerdata.com/sitemap.xml
Sitemap: https://www.tigerdata.com/blog/sitemap.xml
Sitemap: https://www.tigerdata.com/docs/sitemap-0.xml

A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.timescale.com/
307https://timescale.com/

HTTP → HTTPS

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

Consistent

A+
Domain Intelligence
timescale.com — via NameCheap, Inc., 27 years, 7 months old, hosted on AWS
PASS
timescale.com — via NameCheap, Inc., 27 years, 7 months old, hosted on AWS
Info::
Domain registered until Jan 27, 2027 (9 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: NameCheap, Inc.
Info::
Hosting: AWS
Got: AS16509
Domain expiry

198 days

January 27, 2027

SSL certificate

62 days

Issued by Google Trust Services

Domain age

27 years, 7 months

Registered January 27, 1999

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

76.76.21.21

Registrar

NameCheap, 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 NameCheap, Inc.
Created January 27, 1999 (27 years, 7 months ago)
Expires January 27, 2027 (9 months)
Last Updated December 28, 2025
Name Servers edna.ns.cloudflare.com, josh.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 76.76.21.21
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.1s)

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

Connection waterfall

DNS Lookup 43 ms TCP Connect 16 ms TLS Handshake 23 ms Server Processing 65 ms Content Transfer 0 ms
A
CDN & Delivery
Cloudflare (DYNAMIC)
PASS
Cloudflare (DYNAMIC)
Info::
Site is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: 9e8bcf070be42161-CDG
Info::
CDN cache status: DYNAMIC
CDN Detected: Cloudflare
Provider Cloudflare Cache Status DYNAMIC Evidence cf-ray: 9e8bcf070be42161-CDG
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback