Skip to content
https://www.cal.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 Amsterdam, Netherlands
308 Permanent Redirect
Checks
9
7 PASS 2 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.cal.com/
200https://cal.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

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

Certificate validity

46
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
A
DNS Records
2 A records, 18 ms lookup
PASS
2 A records, 18 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.18.0.62, 104.18.1.62
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700::6812:3e, 2606:4700::6812:13e
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: 18 ms
Got: 18 ms
A104.18.0.62, 104.18.1.62
AAAA2606:4700::6812:3e, 2606:4700::6812:13e
CNAME
NS
MX
TXT
CAALookup not available with standard resolver
Resolved in 18 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), 130 ms total
PASS
1 redirect(s), 130 ms total
Info::
Single redirect
Got: https://www.cal.com → https://cal.com/ (308)
Info::
WWW normalization redirect

https://www.cal.com

69 ms · HTTP/1.1

308

https://cal.com/

61 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.cal.com30869 msHTTP/1.1cloudflare
2https://cal.com/20061 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (1 ms)
PASS
IPv6 reachable (1 ms)
Info::
IPv6 is configured and reachable at 2606:4700::6812:3e, 2606:4700::6812:13e
Got: 1 ms connect
IPv6 Ready
AAAA Records 2606:4700::6812:3e, 2606:4700::6812:13e Connection Reachable (1 ms)
A+
Crawlability
robots.txt present, sitemap with 7 URLs
PASS
robots.txt present, sitemap with 7 URLs
Info::
robots.txt is present
Got: 329 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 7 entries
Info::
Sitemap index with 7 child sitemaps
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 329 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /sandbox
Disallow: /api
Disallow: /settings
Disallow: /settings/my-account

# Specifically allow access to OG Image api, otherwise eg Twitter won't render these images.
Allow: /api/social/og/image
# Specifically allow access to api/app-store to allow search engines to fetch assets
Allow: /api/app-store/

A+
Domain Intelligence
cal.com — via GoDaddy.com, LLC, 29 years, 3 months old
PASS
cal.com — via GoDaddy.com, LLC, 29 years, 3 months old
Info::
Domain registered until May 17, 2034 (8 years, 2 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: GoDaddy.com, LLC
Domain expiry

2865 days

May 17, 2034

SSL certificate

46 days

Issued by Google Trust Services

Domain age

29 years, 3 months

Registered May 16, 1997

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700::6812:13e

Registrar

GoDaddy.com, LLC

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 GoDaddy.com, LLC
Created May 16, 1997 (29 years, 3 months ago)
Expires May 17, 2034 (8 years, 2 months)
Last Updated May 25, 2024
Name Servers carter.ns.cloudflare.com, linda.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2606:4700::6812:13e
Data source: rdap (0.0s)

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

Connection waterfall

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

Send Feedback