Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
myvidster.com scored 52/100 and does not currently meet the minimum security posture threshold. Multiple configuration gaps were identified that require attention before approval.
Critical gaps in: Known Breaches, HSTS Header, Security Headers, Cookie Security. Positive signals: DNS Configuration, TLS Protocol Support, TLS Configuration all passed.
5 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 myvidster.com compares
Grade distribution across 2598 companies we've scanned. myvidster.com scores better than 15% of them.
83
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
myvidster.com — Grade F (52/100)
2598 companies scanned
Security checks
Each check inspects a different part of myvidster.com's public security setup. Green means healthy, yellow needs attention, red is a problem.
Known Breaches
2 breach(es) found (2 verified). Total accounts affected: 3,884,227. Breaches: MyVidster (2015) (2015-08-15, 19,863 accounts); MyVidster (2025) (2025-10-24, 3,864,364 accounts).
HSTS Header
Strict-Transport-Security header is missing. Connections can be downgraded to HTTP via man-in-the-middle attacks.
Security Headers
None of the 5 recommended security headers are present (missing: CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy). This exposes the application to clickjacking, MIME-sniffing, and other client-side attacks.
Cookie Security
Strengths: 2 cookie(s) analyzed. Issues: 2/2 cookie(s) missing Secure flag (PHPSESSID, referral); 2/2 cookie(s) missing HttpOnly flag (PHPSESSID, referral); 2/2 cookie(s) missing SameSite attribute (PHPSESSID, referral).
MX Records & Mail Provider
Strengths: Mail handled by mail.myvidster.com; 1 MX record(s) configured. Issues: Only 1 MX record — no failover if primary mail server is unavailable.
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.
DMARC / Email Security
Strengths: SPF record present with soft-fail (~all); DKIM configured (selectors: default, s1, s2). Issues: DMARC policy is 'none' (monitoring only, no enforcement); DMARC has no aggregate report URI (rua).
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.
Certificate Hygiene
Strengths: Certificate valid, 51 days remaining; Issued by Let's Encrypt; 613 certificates logged in CT. Issues: Certificates issued by 10 different CAs (threshold: 8 for 613 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.
DNS Configuration
Strengths: 2 nameservers configured (amanda.ns.cloudflare.com., norman.ns.cloudflare.com.); 1 MX records present; DNSSEC enabled; Zone transfers properly restricted.
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.
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
5 items
Steps to improve myvidster.com's security grade, ranked by impact.
1
Address 2 known data breaches
myvidster.com appears in 2 public breach disclosures. Breached credentials may still be in use. Assess exposure, force password resets for affected accounts, and review whether notification obligations apply.
Compliance impact
PDPA (SG)Part 6A
Mandatory breach notification to PDPC
NIST CSFRS.CO-2
Incidents are reported consistent with criteria
How to fix this
1
Identify which accounts and data types were exposed
2
Force password resets for any affected accounts
3
Check if breach notification has been filed with relevant authorities
4
Review and update incident response procedures
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 myvidster.com 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.myvidster.com
3
Enable HSTS (HTTP Strict Transport Security)
The HSTS header is missing on myvidster.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://myvidster.com | grep -i strict
4
Submit to hstspreload.org after confirming the header is correct
4
Add missing security headers (CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy)
5 of 5 recommended security headers are missing on myvidster.com: CSP, X-Content-Type-Options, X-Frame-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: X-Frame-Options: SAMEORIGIN (use DENY only if you never embed your pages in iframes)
4
Add: Referrer-Policy: strict-origin-when-cross-origin
5
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
6
Verify with: curl -sI https://myvidster.com | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
5
Review certificate configuration
Certificate issues found for myvidster.com: wildcard certificate in use. Wildcard certificates have a broader blast radius if compromised. Ensure auto-renewal is configured to prevent expiry. These are operational hygiene items, not immediate security risks.
How to fix this
1
Verify auto-renewal is configured (Let's Encrypt: certbot renew --dry-run)
2
Consider replacing wildcard cert with individual certs for critical subdomains
3
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=none
Strengths: SPF record present with soft-fail (~all); DKIM configured (selectors: default, s1, s2). Issues: DMARC policy is 'none' (monitoring only, no enforcement); DMARC has no aggregate report URI (rua).
SPF Record
Present
v=spf1 +mx +a +ip4:212.7.203.250 ~all
Security Headers
0/5 present
Missing: CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, 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, 51 days remaining; Issued by Let's Encrypt; 613 certificates logged in CT. Issues: Certificates issued by 10 different CAs (threshold: 8 for 613 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
Enabled
Strengths: 2 nameservers configured (amanda.ns.cloudflare.com., norman.ns.cloudflare.com.); 1 MX records present; DNSSEC enabled; Zone transfers properly restricted.