Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
truebill.com scored 90/100, demonstrating a strong security posture. Minor improvements are noted below.
Positive signals: DNS Configuration, Known Breaches, TLS Configuration all passed.
2 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 truebill.com compares
Grade distribution across 2378 companies we've scanned. truebill.com scores better than 89% of them.
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
truebill.com — Grade A- (90/100)
2378 companies scanned
Security checks
Each check inspects a different part of truebill.com's public security setup. Green means healthy, yellow needs attention, red is a problem.
Security Headers
3/5 security headers present. Missing: CSP, Permissions-Policy.
Certificate Hygiene
Strengths: Certificate valid, 65 days remaining; Issued by Amazon. Issues: Wildcard certificate in use — broader attack surface if compromised.
DMARC / Email Security
Strengths: DMARC policy set to reject (strongest); SPF record present with hard-fail (-all); DKIM configured (selectors: google, k1, mandrill).
TLS Configuration
TLSv1.3 negotiated with TLS_AES_128_GCM_SHA256 (128-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
Known Breaches
No known breaches found in public disclosure databases.
DNS Configuration
Strengths: 4 nameservers configured (ns-1295.awsdns-33.org., ns-1711.awsdns-21.co.uk., ns-875.awsdns-45.net., ns-128.awsdns-16.com.); 2 MX records present; DNSSEC enabled; Zone transfers properly restricted.
HSTS Header
HSTS enabled: max-age=31536000 with includeSubDomains and preload. Meets best-practice configuration.
CVE Exposure
Detected technologies: nginx, Proxy/CDN, Framer/c0aead9. (Proxy/CDN detected but excluded from CVE matching — upstream infrastructure). No high or critical CVEs found for detected versions.
Recommended actions
2 items
Steps to improve truebill.com's security grade, ranked by impact.
1
Add optional security headers (CSP, Permissions-Policy)
truebill.com has most security headers configured. Missing: CSP, Permissions-Policy. These are best-practice additions that reduce the attack surface for client-side vulnerabilities.
How to fix this
1
Add Content-Security-Policy header (start with report-only to avoid breakage)
2
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
3
Verify with: curl -sI https://truebill.com | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
See all recommendations
Enter your work email to unlock the full action plan.
No spam. We only send security-related updates.
Report unlocked.
2
Review certificate configuration
Certificate issues found for truebill.com: wildcard certificate in use. Wildcard certificates have a broader blast radius if compromised. These are operational hygiene items, not immediate security risks.
How to fix this
1
Consider replacing wildcard cert with individual certs for critical subdomains
2
Consolidate certificate issuance to 1–2 trusted CAs
At a glance
Key data points from the scan.
TLS Version
TLSv1.3
TLSv1.3 negotiated with TLS_AES_128_GCM_SHA256 (128-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
DMARC Policy
p=reject
Strengths: DMARC policy set to reject (strongest); SPF record present with hard-fail (-all); DKIM configured (selectors: google, k1, mandrill).
SPF Record
Present
v=spf1 ip4:69.221.85.124 ip4:63.151.90.124 include:spf.protection.outlook.com exists:%{i}.spf.hc2314
Security Headers
3/5 present
Missing: CSP, Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=31536000 with includeSubDomains and preload. Meets best-practice configuration.
SSL Certificate
Issues
Strengths: Certificate valid, 65 days remaining; Issued by Amazon. Issues: Wildcard certificate in use — broader attack surface if compromised.
DNSSEC
Enabled
Strengths: 4 nameservers configured (ns-1295.awsdns-33.org., ns-1711.awsdns-21.co.uk., ns-875.awsdns-45.net., ns-128.awsdns-16.com.); 2 MX records present; DNSSEC enabled; Zone transfers properly restricted.