Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
lever.co scored 72/100, meeting baseline requirements but with 3 findings that require attention. The vendor can proceed with a remediation timeline agreement.
Critical gaps in: Security Headers. Positive signals: Known Breaches, HSTS Header, CVE Exposure all passed.
4 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 lever.co compares
Grade distribution across 2378 companies we've scanned. lever.co scores better than 47% 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
lever.co — Grade C- (72/100)
2378 companies scanned
Security checks
Each check inspects a different part of lever.co's public security setup. Green means healthy, yellow needs attention, red is a problem.
Security Headers
Only 0/5 security headers present. Missing: CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy. This exposes the application to clickjacking, MIME-sniffing, and other client-side attacks.
TLS Configuration
TLSv1.2 negotiated. Issues: TLS 1.2 negotiated (1.3 preferred).
DNS Configuration
Strengths: 4 nameservers configured (ns-756.awsdns-30.net., ns-1281.awsdns-32.org., ns-1577.awsdns-05.co.uk., ns-509.awsdns-63.com.); 1 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
Certificate Hygiene
Strengths: Certificate valid, 113 days remaining; Issued by Amazon. Issues: Wildcard certificate in use — broader attack surface if compromised.
Known Breaches
No known breaches found in public disclosure databases.
DMARC / Email Security
Strengths: DMARC policy set to quarantine; SPF record present with soft-fail (~all); DKIM configured (selectors: google, selector1, zendesk1, zendesk2, smtpapi).
HSTS Header
HSTS enabled: max-age=31622400. Missing includeSubDomains. Missing preload directive.
CVE Exposure
Detected technologies: nginx, Proxy/CDN. (Proxy/CDN detected but excluded from CVE matching — upstream infrastructure). No version information exposed — CVE matching not possible (this is good practice).
Recommended actions
4 items
Steps to improve lever.co's security grade, ranked by impact.
1
Add missing security headers (CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy)
5 of 5 recommended security headers are missing on lever.co: CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, 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-Content-Type-Options: nosniff
3
Add: X-Frame-Options: DENY (or SAMEORIGIN if you use iframes)
4
Add: Referrer-Policy: strict-origin-when-cross-origin
5
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
6
Verify with: curl -sI https://lever.co | 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
Enable DNSSEC on your domain
Without DNSSEC, DNS responses for lever.co 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 .co TLD
4
Verify: dig +dnssec lever.co
3
Upgrade to TLS 1.3
lever.co negotiated TLSv1.2. TLS 1.2 is still compliant under all major security frameworks and is not a vulnerability. TLS 1.3 offers faster handshakes and removes legacy cipher negotiation. This is a best-practice improvement, not a compliance gap.
How to fix this
1
Update web server config to prefer TLS 1.3 (nginx: ssl_protocols TLSv1.2 TLSv1.3)
2
Verify: openssl s_client -connect lever.co:443 -tls1_3
4
Review certificate configuration
Certificate issues found for lever.co: 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.2
TLSv1.2 negotiated. Issues: TLS 1.2 negotiated (1.3 preferred).
DMARC Policy
p=quarantine
Strengths: DMARC policy set to quarantine; SPF record present with soft-fail (~all); DKIM configured (selectors: google, selector1, zendesk1, zendesk2, smtpapi).
SPF Record
Present
v=spf1 include:_spf.google.com include:mail.zendesk.com include:mktomail.com include:_spf0.lever.co
Security Headers
0/5 present
Missing: CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=31622400. Missing includeSubDomains. Missing preload directive.
SSL Certificate
Issues
Strengths: Certificate valid, 113 days remaining; Issued by Amazon. Issues: Wildcard certificate in use — broader attack surface if compromised.
DNSSEC
Not enabled
Strengths: 4 nameservers configured (ns-756.awsdns-30.net., ns-1281.awsdns-32.org., ns-1577.awsdns-05.co.uk., ns-509.awsdns-63.com.); 1 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.