Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
xhamster.com scored 85/100, demonstrating a strong security posture. Minor improvements are noted below.
Critical gaps in: Cookie Security. Positive signals: MX Records & Mail Provider, TLS Protocol Support, TLS Configuration all passed.
3 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 xhamster.com compares
Grade distribution across 2565 companies we've scanned. xhamster.com scores better than 78% 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
xhamster.com — Grade B (85/100)
2565 companies scanned
Security checks
Each check inspects a different part of xhamster.com's public security setup. Green means healthy, yellow needs attention, red is a problem.
Cookie Security
Strengths: 4 cookie(s) analyzed. Issues: 4/4 cookie(s) missing Secure flag (cookie_accept_v2, ff_thumb_offset, recs_show_time...); 4/4 cookie(s) missing HttpOnly flag (cookie_accept_v2, ff_thumb_offset, recs_show_time...); 4/4 cookie(s) missing SameSite attribute (cookie_accept_v2, ff_thumb_offset, recs_show_time...).
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 (sima.ns.cloudflare.com., anuj.ns.cloudflare.com.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
Known Breaches
1 breach(es) found (1 verified). Total accounts affected: 377,377. Breaches: xHamster (2016-11-28, 377,377 accounts).
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.
Security Headers
3/5 security headers present. Missing: X-Content-Type-Options, Referrer-Policy.
MX Records & Mail Provider
Strengths: Mail handled by Google Workspace; 5 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.
DMARC / Email Security
Strengths: DMARC policy set to reject (strongest); SPF record present with hard-fail (-all); DKIM configured (selectors: google, mail).
HSTS Header
HSTS enabled: max-age=31536000s (365 days) with includeSubDomains and preload. Meets best-practice configuration.
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.
Certificate Hygiene
Strengths: Certificate valid, 72 days remaining; Issued by Let's Encrypt.
Recommended actions
3 items
Steps to improve xhamster.com's security grade, ranked by impact.
1
Enable DNSSEC on your domain
Without DNSSEC, DNS responses for xhamster.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 xhamster.com
See all recommendations
Enter your work email to unlock the full action plan.
No spam. We only send security-related updates.
Report unlocked.
2
Review unverified breach disclosure
xhamster.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
3
Add optional security headers (X-Content-Type-Options, Referrer-Policy)
xhamster.com has most security headers configured. Missing: X-Content-Type-Options, Referrer-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: Referrer-Policy: strict-origin-when-cross-origin
3
Verify with: curl -sI https://xhamster.com | 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_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: google, mail).
SPF Record
Present
v=spf1 include:_spf.google.com include:_spf.smtp.advancedhosters.com ip4:88.208.60.232 -all
Security Headers
3/5 present
Missing: X-Content-Type-Options, Referrer-Policy
HSTS
Enabled
HSTS enabled: max-age=31536000s (365 days) with includeSubDomains and preload. Meets best-practice configuration.
SSL Certificate
Valid
Strengths: Certificate valid, 72 days remaining; Issued by Let's Encrypt.
DNSSEC
Not enabled
Strengths: 2 nameservers configured (sima.ns.cloudflare.com., anuj.ns.cloudflare.com.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.