Security checks — sorted by severity
HSTS Header
Strict-Transport-Security header is missing. Connections can be downgraded to HTTP via man-in-the-middle attacks.
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.
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.
CVE Exposure
Detected technologies: nginx/1.14.2, Express, Ghost/5.7. 1 critical-severity CVE(s) found (CVSS >= 9.0): CVE-2024-23724. Immediate patching recommended.
Detected technologies: nginx/1.14.2, Express, Ghost/5.7. 1 critical-severity CVE(s) found (CVSS >= 9.0): CVE-2024-23724. Immediate patching recommended.
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.
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.
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: 3 nameservers configured (ns3.digitalocean.com., ns2.digitalocean.com., ns1.digitalocean.com.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
Strengths: 3 nameservers configured (ns3.digitalocean.com., ns2.digitalocean.com., ns1.digitalocean.com.); 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).
TLSv1.2 negotiated. Issues: TLS 1.2 negotiated (1.3 preferred).
TLS Protocol Support
Strengths: TLS 1.2 supported; TLS 1.2 supported (consider enabling TLS 1.3). Protocol support: TLS 1.3: No, TLS 1.2: Yes, TLS 1.1: No, TLS 1.0: No.
Strengths: TLS 1.2 supported; TLS 1.2 supported (consider enabling TLS 1.3). Protocol support: TLS 1.3: No, TLS 1.2: Yes, TLS 1.1: No, TLS 1.0: No.
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.
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.
MX Records & Mail Provider
Strengths: Mail handled by Google Workspace; 5 MX record(s) configured; Multiple MX records provide redundancy.
Strengths: Mail handled by Google Workspace; 5 MX record(s) configured; Multiple MX records provide redundancy.
DMARC / Email Security
Strengths: DMARC policy set to reject (strongest); SPF record present with hard-fail (-all); DKIM configured (selectors: google, s1, s2). Issues: DMARC has no aggregate report URI (rua).
Strengths: DMARC policy set to reject (strongest); SPF record present with hard-fail (-all); DKIM configured (selectors: google, s1, s2). Issues: DMARC has no aggregate report URI (rua).
Known Breaches
No known breaches found in public disclosure databases.
No known breaches found in public disclosure databases.
Cookie Security
No cookies set on the homepage response. No cookie security flags to evaluate.
No cookies set on the homepage response. No cookie security flags to evaluate.
Certificate Hygiene
Strengths: Certificate valid, 42 days remaining; Issued by Let's Encrypt; 191 certificates logged in CT; Certificates from 3 CAs: Google Trust Services, Google Trust Services LLC, Let's Encrypt.
Strengths: Certificate valid, 42 days remaining; Issued by Let's Encrypt; 191 certificates logged in CT; Certificates from 3 CAs: Google Trust Services, Google Trust Services LLC, Let's Encrypt.
Recommended actions
1+ items
Steps to improve breakdev.org's security grade, ranked by impact.
1
Enable HSTS (HTTP Strict Transport Security)
The HSTS header is missing on breakdev.org. Without it, connections can be downgraded from HTTPS to HTTP via man-in-the-middle attacks. This is a straightforward server configuration change.
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://breakdev.org | grep -i strict
4
Submit to hstspreload.org after confirming the header is correct
See all 4 remaining recommendations
Enter your work email to unlock the full action plan.
No spam. We only send security-related updates.
Report unlocked.
AI Summary
What this means
breakdev.org 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: HSTS Header, Security Headers, CVE Exposure. Positive signals: MX Records & Mail Provider, DMARC / Email Security, Known Breaches 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 breakdev.org compares
Grade distribution across 2678 companies we've scanned. breakdev.org scores better than 15% of them.
88
A+
28
A
194
A-
200
B+
75
B
376
B-
137
C+
117
C
347
C-
123
D+
96
D
265
D-
632
F
breakdev.org — Grade F (52/100)
2678 companies scanned
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=reject
Strengths: DMARC policy set to reject (strongest); SPF record present with hard-fail (-all); DKIM configured (selectors: google, s1, s2). Issues: DMARC has no aggregate report URI (rua).
SPF Record
Present
v=spf1 a include:_spf.google.com include:amazonses.com -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
Valid
Strengths: Certificate valid, 42 days remaining; Issued by Let's Encrypt; 191 certificates logged in CT; Certificates from 3 CAs: Google Trust Services, Google Trust Services LLC, Let's Encrypt.
DNSSEC
Not enabled
Strengths: 3 nameservers configured (ns3.digitalocean.com., ns2.digitalocean.com., ns1.digitalocean.com.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
Similar companies
Other domains with comparable security profiles.
