Overview
Findings
Actions
Details
Related
B-
82 / 100

tilt.com

Security report · Scanned February 18, 2026

Checks
8
Passed
5
Warnings
2
Critical
1
AI-Generated Summary
What this means

tilt.com scored 82/100, demonstrating a strong security posture. Minor improvements are noted below.

Critical gaps in: Security Headers. Positive signals: Known Breaches, TLS Configuration, CVE Exposure all passed.

3 action items identified, including 0 critical. The issues are configuration gaps, not architectural problems. A focused remediation effort of 2–5 days could address all findings.

How tilt.com compares

Grade distribution across 2378 companies we've scanned. tilt.com scores better than 72% of them.

72th percentile
0 Percentile rank 100
71
A+
22
A
180
A-
181
B+
69
B
333
B-
111
C+
111
C
295
C-
110
D+
92
D
216
D-
587
F
tilt.com — Grade B- (82/100) 2378 companies scanned
Security checks

Each check inspects a different part of tilt.com's public security setup. Green means healthy, yellow needs attention, red is a problem.

Security Headers
Only 2/5 security headers present. Missing: CSP, X-Frame-Options, Permissions-Policy. This exposes the application to clickjacking, MIME-sniffing, and other client-side attacks.
Problem
DNS Configuration
Strengths: 4 nameservers configured (ns1-04.azure-dns.com., ns2-04.azure-dns.net., ns3-04.azure-dns.org., ns4-04.azure-dns.info.); 1 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
Needs work
HSTS Header
HSTS present but max-age is low (10886400s). Recommended minimum: 15768000 (6 months).
Needs work
Known Breaches
No known breaches found in public disclosure databases.
Healthy
TLS Configuration
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
Healthy
CVE Exposure
No server software versions detected in HTTP response headers. This is good practice (version hiding) but means CVE exposure cannot be assessed from external signals alone.
Healthy
DMARC / Email Security
Strengths: DMARC policy set to quarantine; SPF record present with soft-fail (~all); DKIM configured (selectors: google, s1, s2, zendesk1, zendesk2).
Healthy
Certificate Hygiene
Strengths: Certificate valid, 139 days remaining; Issued by DigiCert Inc.
Healthy
Recommended actions
3 items

Steps to improve tilt.com's security grade, ranked by impact.

1
Add missing security headers (CSP, X-Frame-Options, Permissions-Policy)
Impact: 1–2 Hours
HIGH
3 of 5 recommended security headers are missing on tilt.com: CSP, X-Frame-Options, Permissions-Policy. These headers protect against clickjacking, MIME-sniffing, and unauthorized browser feature access. Adding them is a server configuration change with no application code changes required.
Compliance impact
PCI-DSS 4.0Req 6.4.1
Security headers are required application controls
OWASPSecure Headers
Recommended baseline for web applications
How to fix this
1
Add Content-Security-Policy header (start with report-only to avoid breakage)
2
Add: X-Frame-Options: DENY (or SAMEORIGIN if you use iframes)
3
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
4
Verify with: curl -sI https://tilt.com | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
2
Enable DNSSEC on your domain
Impact: 1–3 Days (Depends On Registrar)
MEDIUM
Without DNSSEC, DNS responses for tilt.com can be spoofed, potentially redirecting users to malicious sites. This requires coordination with your domain registrar to publish DS records.
Compliance impact
NIST 800-53SC-20
Secure name/address resolution service
How to fix this
1
Check if your DNS provider supports DNSSEC (Cloudflare, Route53, etc.)
2
Enable DNSSEC signing in your DNS provider dashboard
3
Add the DS record to your registrar for .com TLD
4
Verify: dig +dnssec tilt.com
3
Increase HSTS max-age duration
Impact: < 30 Minutes
MEDIUM
HSTS is enabled but the max-age (0s) is below the recommended minimum of 15768000s (6 months). A short max-age means browsers forget the HTTPS-only policy quickly, reducing protection between visits.
Compliance impact
PCI-DSS 4.0Req 6.4.1
Application security header configuration
How to fix this
1
Update header: Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
2
Verify: curl -sI https://tilt.com | grep -i strict
At a glance

Key data points from the scan.

TLS Version
TLSv1.3
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
DMARC Policy
p=quarantine
Strengths: DMARC policy set to quarantine; SPF record present with soft-fail (~all); DKIM configured (selectors: google, s1, s2, zendesk1, zendesk2).
SPF Record
Present
v=spf1 a include:_spf.google.com include:_spf.mailgun.org include:mail.zendesk.com ~all
Security Headers
2/5 present
Missing: CSP, X-Frame-Options, Permissions-Policy
HSTS
Not enabled
HSTS present but max-age is low (10886400s). Recommended minimum: 15768000 (6 months).
SSL Certificate
Valid
Strengths: Certificate valid, 139 days remaining; Issued by DigiCert Inc.
DNSSEC
Not enabled
Strengths: 4 nameservers configured (ns1-04.azure-dns.com., ns2-04.azure-dns.net., ns3-04.azure-dns.org., ns4-04.azure-dns.info.); 1 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.