Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
starsky.io scored 85/100, demonstrating a strong security posture. No material issues found.
Critical gaps in: DMARC / Email Security. Positive signals: Known Breaches, TLS Configuration, HSTS Header all passed.
1 action item identified, including 1 critical. The issues are configuration gaps, not architectural problems. A focused remediation effort of 2–5 days could address all findings.
How starsky.io compares
Grade distribution across 2598 companies we've scanned. starsky.io scores better than 78% 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
starsky.io — Grade B (85/100)
2598 companies scanned
Security checks
Each check inspects a different part of starsky.io's public security setup. Green means healthy, yellow needs attention, red is a problem.
DMARC / Email Security
Issues: No DMARC record found — email spoofing is not prevented; No SPF record found; No DKIM records found for common selectors (domain may use custom selectors — this is not a confirmed gap).
Known Breaches
No known breaches found in public disclosure databases.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
HSTS Header
HSTS enabled: max-age=31536000 with includeSubDomains and preload. Meets best-practice configuration.
Security Headers
4/5 security headers present. Missing: Permissions-Policy.
DNS Configuration
Strengths: 2 nameservers configured (launch2.spaceship.net., launch1.spaceship.net.); DNSSEC enabled; Zone transfers properly restricted.
CVE Exposure
Detected technologies: openresty. No version information exposed — CVE matching not possible (this is good practice).
Certificate Hygiene
Strengths: Certificate valid, 61 days remaining; Issued by Let's Encrypt.
Recommended actions
1 item
Steps to improve starsky.io's security grade, ranked by impact.
1
Set up email authentication (DMARC, SPF, DKIM)
Without email authentication, anyone can send emails that appear to come from starsky.io. This is the most common vector for phishing attacks targeting employees and customers. DMARC, SPF, DKIM are not configured.
Compliance impact
NIST CSFPR.AC-7
Email authentication is a required access control
ISO 27001A.13.2.1
Information transfer policies require email security controls
HIPAA§164.312(e)
Transmission security for electronic PHI
How to fix this
1
Add SPF record to DNS: v=spf1 include:_spf.google.com ~all (adjust for your email provider)
2
Configure DKIM signing with your email provider and publish the public key in DNS
3
Add DMARC record: v=DMARC1; p=quarantine; rua=mailto:[email protected]
4
Monitor DMARC reports for 2–4 weeks, then upgrade policy to p=reject
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
Not configured
Issues: No DMARC record found — email spoofing is not prevented; No SPF record found; No DKIM records found for common selectors (domain may use custom selectors — this is not a confirmed gap).
SPF Record
Missing
No SPF record found.
Security Headers
4/5 present
Missing: Permissions-Policy
HSTS
Enabled
HSTS enabled: max-age=31536000 with includeSubDomains and preload. Meets best-practice configuration.
SSL Certificate
Valid
Strengths: Certificate valid, 61 days remaining; Issued by Let's Encrypt.
DNSSEC
Enabled
Strengths: 2 nameservers configured (launch2.spaceship.net., launch1.spaceship.net.); DNSSEC enabled; Zone transfers properly restricted.