Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
stripchat.com scored 75/100, meeting baseline requirements but with 6 findings that require attention. The vendor can proceed with a remediation timeline agreement.
Critical gaps in: Security Headers. Positive signals: MX Records & Mail Provider, TLS Protocol Support, TLS Configuration 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 stripchat.com compares
Grade distribution across 2522 companies we've scanned. stripchat.com scores better than 55% of them.
79
A+
25
A
183
A-
191
B+
72
B
353
B-
121
C+
116
C
324
C-
117
D+
94
D
241
D-
606
F
stripchat.com — Grade C (75/100)
2522 companies scanned
Security checks
Each check inspects a different part of stripchat.com's public security setup. Green means healthy, yellow needs attention, red is a problem.
Security Headers
1/5 security headers present. Missing: CSP, 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.
DNS Configuration
Strengths: 2 nameservers configured (amy.ns.cloudflare.com., duke.ns.cloudflare.com.); 7 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
Cookie Security
Strengths: 2 cookie(s) analyzed; All cookies have Secure flag; All cookies have HttpOnly flag. Issues: 1/2 cookie(s) missing SameSite attribute (__cf_bm).
Known Breaches
1 breach(es) found (1 verified). Total accounts affected: 10,001,355. Breaches: Stripchat (2021-11-05, 10,001,355 accounts).
Certificate Hygiene
Strengths: Certificate valid, 89 days remaining; Issued by Google Trust Services; 684 certificates logged in CT. Issues: Certificates issued by 11 different CAs (threshold: 8 for 684 logged certs) — possible misconfiguration or shadow IT. Note: Wildcard certificate in use (*.domain) — covers all subdomains. Common practice; worth noting that compromise would affect all subdomains.
MX Records & Mail Provider
Strengths: Mail handled by Google Workspace; 7 MX record(s) configured; Multiple MX records provide redundancy.
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.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
HSTS Header
HSTS enabled: max-age=31536000s (365 days). includeSubDomains present. Missing preload directive.
DMARC / Email Security
Strengths: DMARC policy set to quarantine; SPF record present with hard-fail (-all); DKIM configured (selectors: google, zendesk1, zendesk2).
security.txt (RFC 9116)
Strengths: security.txt found with 5 field(s); Contact: https://hackerone.com/stripchat/reports/new; Expires in 267 days (2026-12-31T23:01:00.000Z); Disclosure policy: https://hackerone.com/stripchat; Preferred languages: en; Acknowledgments/hall-of-fame link included. Issues: Not PGP signed (recommended for authenticity).
CVE Exposure
Detected technologies: cloudflare. (cloudflare detected but excluded from CVE matching — upstream infrastructure). All detected technologies are upstream CDN/proxy infrastructure. No application-level software versions exposed.
Recommended actions
4 items
Steps to improve stripchat.com's security grade, ranked by impact.
1
Add missing security headers (CSP, X-Content-Type-Options, Referrer-Policy, Permissions-Policy)
4 of 5 recommended security headers are missing on stripchat.com: CSP, 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 a Content-Security-Policy header. Safe starting value (works with Google Fonts and inline styles/scripts): default-src 'self'; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com; script-src 'self' 'unsafe-inline'; upgrade-insecure-requests. Test your site after adding it, then tighten over time by removing 'unsafe-inline'.
2
Add: X-Content-Type-Options: nosniff
3
Add: Referrer-Policy: strict-origin-when-cross-origin
4
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
5
Verify with: curl -sI https://stripchat.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
Enable DNSSEC on your domain
Without DNSSEC, DNS responses for stripchat.com 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 .com TLD
4
Verify: dig +dnssec stripchat.com
3
Review unverified breach disclosure
stripchat.com appears in an unverified breach report. This may be a false positive or data aggregation error. Investigate to confirm or rule out exposure.
How to fix this
1
Review the breach details on haveibeenpwned.com
2
Cross-reference with internal incident records
3
If confirmed, follow breach response procedures
4
Review certificate configuration
Certificate issues found for stripchat.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_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
DMARC Policy
p=quarantine
Strengths: DMARC policy set to quarantine; SPF record present with hard-fail (-all); DKIM configured (selectors: google, zendesk1, zendesk2).
SPF Record
Present
v=spf1 include:spf.stripchat.com -all
Security Headers
1/5 present
Missing: CSP, X-Content-Type-Options, Referrer-Policy, Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=31536000s (365 days). includeSubDomains present. Missing preload directive.
SSL Certificate
Issues
Strengths: Certificate valid, 89 days remaining; Issued by Google Trust Services; 684 certificates logged in CT. Issues: Certificates issued by 11 different CAs (threshold: 8 for 684 logged certs) — possible misconfiguration or shadow IT. Note: Wildcard certificate in use (*.domain) — covers all subdomains. Common practice; worth noting that compromise would affect all subdomains.
DNSSEC
Not enabled
Strengths: 2 nameservers configured (amy.ns.cloudflare.com., duke.ns.cloudflare.com.); 7 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.