Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
labdoor.com scored 48/100 and does not currently meet the minimum security posture threshold. Multiple configuration gaps were identified that require attention before approval.
Critical gaps in: HSTS Header, Security Headers. Positive signals: Known Breaches all passed.
7 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 labdoor.com compares
Grade distribution across 2378 companies we've scanned. labdoor.com scores better than 15% of them.
71
A+
22
A
180
A-
181
B+
69
B
333
B-
111
C+
111
C
295
C-
110
D+
92
D
216
D-
587
F
labdoor.com — Grade F (48/100)
2378 companies scanned
Security checks
Each check inspects a different part of labdoor.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.
Security Headers
Only 0/5 security headers 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.
DNS Configuration
Strengths: 4 nameservers configured (ns-2011.awsdns-59.co.uk., ns-643.awsdns-16.net., ns-115.awsdns-14.com., ns-1304.awsdns-35.org.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
TLS Configuration
TLSv1.2 negotiated. Issues: TLS 1.2 negotiated (1.3 preferred).
DMARC / Email Security
Strengths: SPF record present; DKIM configured (selectors: google, k1, mandrill). Issues: DMARC policy is 'none' (monitoring only, no enforcement).
CVE Exposure
Detected technologies: Apache/2.4.62. 1 high-severity CVE(s) found (CVSS 7.0–8.9): CVE-2024-40898. Patching recommended.
Certificate Hygiene
Strengths: Certificate valid, 371 days remaining; Issued by GoDaddy.com, Inc.. Issues: Wildcard certificate in use — broader attack surface if compromised.
Known Breaches
No known breaches found in public disclosure databases.
Recommended actions
7 items
Steps to improve labdoor.com's security grade, ranked by impact.
1
Strengthen email authentication configuration
Email authentication is partially configured for labdoor.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.labdoor.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
Enable HSTS (HTTP Strict Transport Security)
The HSTS header is missing on labdoor.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://labdoor.com | grep -i strict
4
Submit to hstspreload.org after confirming the header is correct
3
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 labdoor.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 Content-Security-Policy header (start with report-only to avoid breakage)
2
Add: X-Content-Type-Options: nosniff
3
Add: X-Frame-Options: DENY (or SAMEORIGIN if you use iframes)
4
Add: Referrer-Policy: strict-origin-when-cross-origin
5
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
6
Verify with: curl -sI https://labdoor.com | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
4
Enable DNSSEC on your domain
Without DNSSEC, DNS responses for labdoor.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 labdoor.com
5
Review potential CVE exposure in detected software
Software detected on labdoor.com has potential CVE matches. Review the specific CVEs and confirm whether the installed version is affected.
How to fix this
1
Review matched CVEs and confirm installed versions
2
Update software if vulnerable versions are confirmed
3
Consider hiding version information in server headers
6
Upgrade to TLS 1.3
labdoor.com negotiated TLSv1.2. TLS 1.2 is still compliant under all major security frameworks and is not a vulnerability. TLS 1.3 offers faster handshakes and removes legacy cipher negotiation. This is a best-practice improvement, not a compliance gap.
How to fix this
1
Update web server config to prefer TLS 1.3 (nginx: ssl_protocols TLSv1.2 TLSv1.3)
2
Verify: openssl s_client -connect labdoor.com:443 -tls1_3
7
Review certificate configuration
Certificate issues found for labdoor.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.2
TLSv1.2 negotiated. Issues: TLS 1.2 negotiated (1.3 preferred).
DMARC Policy
p=none
Strengths: SPF record present; DKIM configured (selectors: google, k1, mandrill). Issues: DMARC policy is 'none' (monitoring only, no enforcement).
SPF Record
Present
v=spf1 include:spf.mandrillapp.com redirect=_spf.google.com
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, 371 days remaining; Issued by GoDaddy.com, Inc.. Issues: Wildcard certificate in use — broader attack surface if compromised.
DNSSEC
Not enabled
Strengths: 4 nameservers configured (ns-2011.awsdns-59.co.uk., ns-643.awsdns-16.net., ns-115.awsdns-14.com., ns-1304.awsdns-35.org.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.