Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
kubesail.com scored 65/100, meeting baseline requirements but with 3 findings that require attention. The vendor can proceed with a remediation timeline agreement.
Positive signals: Known Breaches, TLS Configuration, CVE Exposure 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 kubesail.com compares
Grade distribution across 2378 companies we've scanned. kubesail.com scores better than 34% 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
kubesail.com — Grade D (65/100)
2378 companies scanned
Security checks
Each check inspects a different part of kubesail.com's public security setup. Green means healthy, yellow needs attention, red is a problem.
DNS Configuration
Strengths: 4 nameservers configured (ns-204.awsdns-25.com., ns-841.awsdns-41.net., ns-1461.awsdns-54.org., ns-1953.awsdns-52.co.uk.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
DMARC / Email Security
Strengths: SPF record present with soft-fail (~all); DKIM configured (selectors: s1, s2). Issues: DMARC policy is 'none' (monitoring only, no enforcement).
Certificate Hygiene
Strengths: Certificate valid, 266 days remaining; Issued by Amazon. Issues: Wildcard certificate in use — broader attack surface if compromised.
HSTS Header
Could not fetch https://kubesail.com — connection failed or timed out.
Security Headers
Could not fetch https://kubesail.com — connection failed or timed out.
Known Breaches
No known breaches found in public disclosure databases.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_128_GCM_SHA256 (128-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
CVE Exposure
No server software versions detected in HTTP response headers. This is good practice (version hiding) but means CVE exposure cannot be assessed from external signals alone.
Recommended actions
3 items
Steps to improve kubesail.com's security grade, ranked by impact.
1
Strengthen email authentication configuration
Email authentication is partially configured for kubesail.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.kubesail.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 DNSSEC on your domain
Without DNSSEC, DNS responses for kubesail.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 kubesail.com
3
Review certificate configuration
Certificate issues found for kubesail.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.3
TLSv1.3 negotiated with TLS_AES_128_GCM_SHA256 (128-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: s1, s2). Issues: DMARC policy is 'none' (monitoring only, no enforcement).
SPF Record
Present
v=spf1 include:_spf.google.com include:amazonses.com include:sendgrid.net ~all
Security Headers
0/0 present
All headers configured.
HSTS
Not enabled
Could not fetch https://kubesail.com — connection failed or timed out.
SSL Certificate
Issues
Strengths: Certificate valid, 266 days remaining; Issued by Amazon. Issues: Wildcard certificate in use — broader attack surface if compromised.
DNSSEC
Not enabled
Strengths: 4 nameservers configured (ns-204.awsdns-25.com., ns-841.awsdns-41.net., ns-1461.awsdns-54.org., ns-1953.awsdns-52.co.uk.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.