Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
windsor.io scored 52/100 and does not currently meet the minimum security posture threshold. Multiple configuration gaps were identified that require attention before approval.
Positive signals: Known Breaches, DMARC / Email Security, CVE Exposure 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 windsor.io compares
Grade distribution across 2378 companies we've scanned. windsor.io scores better than 16% 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
windsor.io — Grade F (52/100)
2378 companies scanned
Security checks
Each check inspects a different part of windsor.io's public security setup. Green means healthy, yellow needs attention, red is a problem.
DNS Configuration
Strengths: 2 nameservers configured (ns1.vercel-dns.com., ns2.vercel-dns.com.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
Certificate Hygiene
Issues: Could not retrieve certificate details.
TLS Configuration
Could not complete TLS handshake with windsor.io:443 — [SSL: TLSV1_ALERT_INTERNAL_ERROR] tlsv1 alert internal error (_ssl.c:1081)
HSTS Header
Could not fetch https://windsor.io — connection failed or timed out.
Security Headers
Could not fetch https://windsor.io — connection failed or timed out.
Known Breaches
No known breaches found in public disclosure databases.
DMARC / Email Security
Strengths: DMARC policy set to quarantine; SPF record present with soft-fail (~all); DKIM configured (selectors: google).
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
2 items
Steps to improve windsor.io's security grade, ranked by impact.
1
Enable DNSSEC on your domain
Without DNSSEC, DNS responses for windsor.io 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 .io TLD
4
Verify: dig +dnssec windsor.io
See all recommendations
Enter your work email to unlock the full action plan.
No spam. We only send security-related updates.
Report unlocked.
2
Review certificate configuration
Certificate issues found for windsor.io: . These are operational hygiene items, not immediate security risks.
How to fix this
1
Consolidate certificate issuance to 1–2 trusted CAs
At a glance
Key data points from the scan.
TLS Version
Issues detected
Could not complete TLS handshake with windsor.io:443 — [SSL: TLSV1_ALERT_INTERNAL_ERROR] tlsv1 alert internal error (_ssl.c:1081)
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 mx include:_spf.google.com include:sendgrid.net include:21130310.spf07.hubspotemail.net ~all
Security Headers
0/0 present
All headers configured.
HSTS
Not enabled
Could not fetch https://windsor.io — connection failed or timed out.
SSL Certificate
Issues
Issues: Could not retrieve certificate details.
DNSSEC
Not enabled
Strengths: 2 nameservers configured (ns1.vercel-dns.com., ns2.vercel-dns.com.); 5 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.