Overview
Findings
Actions
Details
Related
B
85 / 100

colabsoftware.com

Security report · Scanned February 18, 2026

Checks
8
Passed
6
Warnings
1
Critical
1
AI-Generated Summary
What this means

colabsoftware.com scored 85/100, demonstrating a strong security posture. Minor improvements are noted below.

Critical gaps in: Security Headers. Positive signals: Known Breaches, TLS Configuration, DNS Configuration all passed.

2 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 colabsoftware.com compares

Grade distribution across 2378 companies we've scanned. colabsoftware.com scores better than 78% of them.

78th percentile
0 Percentile rank 100
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
colabsoftware.com — Grade B (85/100) 2378 companies scanned
Security checks

Each check inspects a different part of colabsoftware.com's public security setup. Green means healthy, yellow needs attention, red is a problem.

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.
Problem
Certificate Hygiene
Strengths: Certificate valid, 53 days remaining; Issued by Google Trust Services. Issues: Wildcard certificate in use — broader attack surface if compromised.
Needs work
DNS Configuration
Strengths: 5 nameservers configured (franklin.ns.colabsoftware.com., hopper.ns.colabsoftware.com., tesla.ns.colabsoftware.com., curie.ns.colabsoftware.com.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.
Healthy
Known Breaches
No known breaches found in public disclosure databases.
Healthy
TLS Configuration
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
Healthy
HSTS Header
HSTS enabled: max-age=31536000. Missing includeSubDomains. Missing preload directive.
Healthy
DMARC / Email Security
Strengths: DMARC policy set to quarantine; SPF record present with soft-fail (~all); DKIM configured (selectors: google).
Healthy
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.
Healthy
Recommended actions
2 items

Steps to improve colabsoftware.com's security grade, ranked by impact.

1
Add missing security headers (CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy)
Impact: 1–2 Hours
HIGH
5 of 5 recommended security headers are missing on colabsoftware.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://colabsoftware.com | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
2
Review certificate configuration
Impact: 1–2 Hours
LOW
Certificate issues found for colabsoftware.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=quarantine
Strengths: DMARC policy set to quarantine; SPF record present with soft-fail (~all); DKIM configured (selectors: google).
SPF Record
Present
v=spf1 include:_spf.google.com include:amazonses.com include:21767886.spf06.hubspotemail.net include
Security Headers
0/5 present
Missing: CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=31536000. Missing includeSubDomains. Missing preload directive.
SSL Certificate
Issues
Strengths: Certificate valid, 53 days remaining; Issued by Google Trust Services. Issues: Wildcard certificate in use — broader attack surface if compromised.
DNSSEC
Enabled
Strengths: 5 nameservers configured (franklin.ns.colabsoftware.com., hopper.ns.colabsoftware.com., tesla.ns.colabsoftware.com., curie.ns.colabsoftware.com.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.