Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
wiz.io scored 88/100, demonstrating a strong security posture. Minor improvements are noted below.
Positive signals: TLS Configuration, HSTS Header, CVE Exposure 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 wiz.io compares
Grade distribution across 2520 companies we've scanned. wiz.io scores better than 81% of them.
79
A+
25
A
184
A-
190
B+
73
B
351
B-
121
C+
113
C
324
C-
117
D+
93
D
237
D-
613
F
wiz.io — Grade B+ (88/100)
2520 companies scanned
Security checks
Each check inspects a different part of wiz.io's public security setup. Green means healthy, yellow needs attention, red is a problem.
DMARC / Email Security
Strengths: DMARC policy set to reject (strongest); DKIM configured (selectors: google, s1). Issues: No SPF record found.
Security Headers
3/5 security headers present. Missing: X-Frame-Options, Permissions-Policy.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_128_GCM_SHA256 (128-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
HSTS Header
HSTS enabled: max-age=31536000 with includeSubDomains and preload. Meets best-practice configuration.
CVE Exposure
Detected technologies: Vercel. (Vercel detected but excluded from CVE matching — upstream infrastructure). All detected technologies are upstream CDN/proxy infrastructure. No application-level software versions exposed.
Known Breaches
No known breaches found in public disclosure databases.
DNS Configuration
Strengths: 4 nameservers configured (ns-1334.awsdns-38.org., ns-1611.awsdns-09.co.uk., ns-457.awsdns-57.com., ns-883.awsdns-46.net.); 1 MX records present; DNSSEC enabled; Zone transfers properly restricted.
Certificate Hygiene
Strengths: Certificate valid, 38 days remaining; Issued by Let's Encrypt.
Recommended actions
2 items
Steps to improve wiz.io's security grade, ranked by impact.
1
Strengthen email authentication configuration
Email authentication is partially configured for wiz.io but has gaps. Actions needed: add SPF record. Until DMARC enforcement is active, spoofed emails may still reach recipients.
Compliance impact
NIST CSFPR.AC-7
Email authentication is a required access control
How to fix this
1
Add SPF record if missing: v=spf1 include:_spf.google.com -all
2
Verify with: nslookup -type=txt _dmarc.wiz.io
See all recommendations
Enter your work email to unlock the full action plan.
No spam. We only send security-related updates.
Report unlocked.
2
Add optional security headers (X-Frame-Options, Permissions-Policy)
wiz.io has most security headers configured. Missing: X-Frame-Options, Permissions-Policy. These are best-practice additions that reduce the attack surface for client-side vulnerabilities.
How to fix this
1
Add: X-Frame-Options: DENY (or SAMEORIGIN if you use iframes)
2
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
3
Verify with: curl -sI https://wiz.io | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
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); DKIM configured (selectors: google, s1). Issues: No SPF record found.
SPF Record
Missing
No SPF record found.
Security Headers
3/5 present
Missing: X-Frame-Options, Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=31536000 with includeSubDomains and preload. Meets best-practice configuration.
SSL Certificate
Valid
Strengths: Certificate valid, 38 days remaining; Issued by Let's Encrypt.
DNSSEC
Enabled
Strengths: 4 nameservers configured (ns-1334.awsdns-38.org., ns-1611.awsdns-09.co.uk., ns-457.awsdns-57.com., ns-883.awsdns-46.net.); 1 MX records present; DNSSEC enabled; Zone transfers properly restricted.