82
screen.studio
Findings
6
·
1
·
1
Checks
8 passive
Executive Summary
AI-GENERATED
screen.studio scored 82/100, demonstrating a strong security posture. Minor improvements are noted below.
Critical gaps in: Security Headers. Positive signals: Known Breaches, TLS Configuration, HSTS Header 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.
Action Items
Ordered by priority · 2 items
1
Add missing security headers (X-Content-Type-Options, Referrer-Policy, Permissions-Policy)
3 of 5 recommended security headers are missing on screen.studio: X-Content-Type-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
Remediation Steps
1
Add: X-Content-Type-Options: nosniff
2
Add: Referrer-Policy: strict-origin-when-cross-origin
3
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
4
Verify with: curl -sI https://screen.studio | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
Unlock the full remediation plan
Get detailed steps, compliance mapping, and ownership for all 2 action items. Free — just enter your work email.
No spam. We'll only contact you about this report.
✓ Report unlocked. Scroll down for full details.
2
Strengthen email authentication configuration
Email authentication is partially configured for screen.studio but has gaps. Actions needed: upgrade DMARC policy from 'none' to 'quarantine' or 'reject'. Until DMARC enforcement is active, spoofed emails may still reach recipients.
Compliance Impact
NIST CSFPR.AC-7
Email authentication is a required access control
Remediation Steps
1
Upgrade DMARC policy to p=quarantine (then p=reject after monitoring)
2
Verify with: nslookup -type=txt _dmarc.screen.studio
Scan Findings
Security Headers
Critical
DMARC / Email Security
Warning
Known Breaches
Healthy
TLS Configuration
Healthy
HSTS Header
Healthy
CVE Exposure
Healthy
DNS Configuration
Healthy
Certificate Hygiene
Healthy