Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
screen.studio scored 82/100, demonstrating a strong security posture. Minor improvements are noted below.
Critical gaps in: Security Headers. Positive signals: MX Records & Mail Provider, TLS Configuration, TLS Protocol Support 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 screen.studio compares
Grade distribution across 2599 companies we've scanned. screen.studio scores better than 72% of them.
84
A+
25
A
190
A-
196
B+
75
B
362
B-
129
C+
114
C
330
C-
119
D+
95
D
252
D-
628
F
screen.studio — Grade B- (82/100)
2599 companies scanned
Security checks
Each check inspects a different part of screen.studio's public security setup. Green means healthy, yellow needs attention, red is a problem.
Security Headers
2/5 security headers present. Missing: X-Content-Type-Options, Referrer-Policy, Permissions-Policy. This exposes the application to clickjacking, MIME-sniffing, and other client-side attacks.
MTA-STS & TLS Reporting
Issues: No MTA-STS configured — email in transit is vulnerable to TLS downgrade attacks. Sending servers cannot verify that your mail server requires TLS; No TLSRPT record — TLS delivery failures won't be reported to domain owner.
DNS CAA Records
No CAA records found. Without CAA, any Certificate Authority can issue certificates for this domain. Adding CAA records restricts issuance to authorized CAs only, reducing the risk of misissued certificates.
security.txt (RFC 9116)
No security.txt found. Publishing a security.txt at /.well-known/security.txt is the industry standard (RFC 9116) for vulnerability disclosure policies. Its absence may indicate a less mature security program.
DMARC / Email Security
Strengths: SPF record present with soft-fail (~all); DKIM configured (selectors: google). Issues: No DMARC record found — email spoofing is not prevented.
MX Records & Mail Provider
Strengths: Mail handled by Google Workspace; 5 MX record(s) configured; Multiple MX records provide redundancy.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_128_GCM_SHA256 (128-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
TLS Protocol Support
Strengths: TLS 1.3 supported; TLS 1.2 supported; TLS 1.3 supported (strongest). Protocol support: TLS 1.3: Yes, TLS 1.2: Yes, TLS 1.1: No, TLS 1.0: No.
HSTS Header
HSTS enabled: max-age=63072000s (730 days). Missing includeSubDomains — subdomains not covered. Missing preload directive.
Cookie Security
No cookies set on the homepage response. No cookie security flags to evaluate.
Known Breaches
No known breaches found in public disclosure databases.
DNS Configuration
Strengths: 4 nameservers configured (ns-cloud-a4.googledomains.com., ns-cloud-a1.googledomains.com., ns-cloud-a2.googledomains.com., ns-cloud-a3.googledomains.com.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.
CVE Exposure
Detected technologies: Vercel, Next.js. (Vercel detected but excluded from CVE matching — upstream infrastructure). No version information exposed — CVE matching not possible (this is good practice).
Certificate Hygiene
Strengths: Certificate valid, 66 days remaining; Issued by Let's Encrypt; 220 certificates logged in CT; Certificates from 3 CAs: Google Trust Services, Google Trust Services LLC, Let's Encrypt.
Recommended actions
2 items
Steps to improve screen.studio's security grade, ranked by impact.
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
How to fix this
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'
See all recommendations
Enter your work email to unlock the full action plan.
No spam. We only send security-related updates.
Report unlocked.
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
How to fix this
1
Upgrade DMARC policy to p=quarantine (then p=reject after monitoring)
2
Verify with: nslookup -type=txt _dmarc.screen.studio
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
Not configured
Strengths: SPF record present with soft-fail (~all); DKIM configured (selectors: google). Issues: No DMARC record found — email spoofing is not prevented.
SPF Record
Present
v=spf1 include:_spf.google.com ~all
Security Headers
2/5 present
Missing: X-Content-Type-Options, Referrer-Policy, Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=63072000s (730 days). Missing includeSubDomains — subdomains not covered. Missing preload directive.
SSL Certificate
Valid
Strengths: Certificate valid, 66 days remaining; Issued by Let's Encrypt; 220 certificates logged in CT; Certificates from 3 CAs: Google Trust Services, Google Trust Services LLC, Let's Encrypt.
DNSSEC
Enabled
Strengths: 4 nameservers configured (ns-cloud-a4.googledomains.com., ns-cloud-a1.googledomains.com., ns-cloud-a2.googledomains.com., ns-cloud-a3.googledomains.com.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.