Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
xvideos.com scored 78/100, meeting baseline requirements but with 6 findings that require attention. The vendor can proceed with a remediation timeline agreement.
Critical gaps in: HSTS Header. Positive signals: MX Records & Mail Provider, TLS Configuration, TLS Protocol Support 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 xvideos.com compares
Grade distribution across 2565 companies we've scanned. xvideos.com scores better than 60% of them.
81
A+
25
A
186
A-
194
B+
73
B
357
B-
122
C+
114
C
328
C-
119
D+
95
D
247
D-
624
F
xvideos.com — Grade C+ (78/100)
2565 companies scanned
Security checks
Each check inspects a different part of xvideos.com's public security setup. Green means healthy, yellow needs attention, red is a problem.
HSTS Header
Strict-Transport-Security header is missing. Connections can be downgraded to HTTP via man-in-the-middle attacks.
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.
MTA-STS & TLS Reporting
Strengths: SMTP TLS Reporting (TLSRPT) configured — delivery failures will be reported. Issues: No MTA-STS configured — email in transit is vulnerable to TLS downgrade attacks. Sending servers cannot verify that your mail server requires TLS.
DNS Configuration
Strengths: 3 nameservers configured (ns1.wgcz.net., ns2.wgcz.net., ns3.wgcz.net.); 7 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
Security Headers
3/5 security headers present. Missing: X-Content-Type-Options, Permissions-Policy.
Cookie Security
Strengths: 1 cookie(s) analyzed; All cookies have Secure flag; All cookies have HttpOnly flag. Issues: 1/1 cookie(s) missing SameSite attribute (session_token).
Certificate Hygiene
Strengths: Certificate valid, 288 days remaining; Issued by Sectigo Limited; 714 certificates logged in CT. Issues: Certificates issued by 10 different CAs (threshold: 8 for 714 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 Configuration
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-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.
Known Breaches
No known breaches found in public disclosure databases.
security.txt (RFC 9116)
Strengths: security.txt found with 2 field(s); Contact: https://hackerone.com/xvideos; Expires in 261 days (2026-12-31T09:12:00.000Z). Issues: Not PGP signed (recommended for authenticity).
CVE Exposure
Detected technologies: nginx. No version information exposed — CVE matching not possible (this is good practice).
DMARC / Email Security
Strengths: DMARC policy set to reject (strongest); SPF record present with hard-fail (-all); DKIM configured (selectors: default, google, s1, s2, smtpapi).
Recommended actions
4 items
Steps to improve xvideos.com's security grade, ranked by impact.
1
Enable HSTS (HTTP Strict Transport Security)
The HSTS header is missing on xvideos.com. Without it, connections can be downgraded from HTTPS to HTTP via man-in-the-middle attacks. This is a straightforward server configuration change.
Compliance impact
PCI-DSS 4.0Req 6.4.1
Required application security controls
NIST 800-53SC-8
Transmission confidentiality and integrity
How to fix this
1
Add header: Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
2
Verify all subdomains support HTTPS before adding includeSubDomains
3
Test with: curl -sI https://xvideos.com | grep -i strict
4
Submit to hstspreload.org after confirming the header is correct
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 xvideos.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 xvideos.com
3
Add optional security headers (X-Content-Type-Options, Permissions-Policy)
xvideos.com has most security headers configured. Missing: X-Content-Type-Options, Permissions-Policy. These are best-practice additions that reduce the attack surface for client-side vulnerabilities.
How to fix this
1
Add: X-Content-Type-Options: nosniff
2
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
3
Verify with: curl -sI https://xvideos.com | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
4
Review certificate configuration
Certificate issues found for xvideos.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=reject
Strengths: DMARC policy set to reject (strongest); SPF record present with hard-fail (-all); DKIM configured (selectors: default, google, s1, s2, smtpapi).
SPF Record
Present
v=spf1 mx ip4:69.55.53.62/32 ip4:141.0.172.202/32 ip4:69.55.53.149/32 ip4:69.55.53.150/32 ip4:141.0.
Security Headers
3/5 present
Missing: X-Content-Type-Options, Permissions-Policy
HSTS
Not enabled
Strict-Transport-Security header is missing. Connections can be downgraded to HTTP via man-in-the-middle attacks.
SSL Certificate
Issues
Strengths: Certificate valid, 288 days remaining; Issued by Sectigo Limited; 714 certificates logged in CT. Issues: Certificates issued by 10 different CAs (threshold: 8 for 714 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: 3 nameservers configured (ns1.wgcz.net., ns2.wgcz.net., ns3.wgcz.net.); 7 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.