Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
garten.co scored 68/100, meeting baseline requirements but with 4 findings that require attention. The vendor can proceed with a remediation timeline agreement.
Critical gaps in: HSTS Header. Positive signals: Known Breaches, DMARC / Email Security, CVE Exposure 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 garten.co compares
Grade distribution across 2378 companies we've scanned. garten.co scores better than 38% 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
garten.co — Grade D+ (68/100)
2378 companies scanned
Security checks
Each check inspects a different part of garten.co's public security setup. Green means healthy, yellow needs attention, red is a problem.
HSTS Header
Strict-Transport-Security header is missing. Connections can be downgraded to HTTP via man-in-the-middle attacks.
DNS Configuration
Strengths: 4 nameservers configured (ns-2018.awsdns-60.co.uk., ns-746.awsdns-29.net., ns-1117.awsdns-11.org., ns-200.awsdns-25.com.); 4 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).
Security Headers
3/5 security headers present. Missing: CSP, Permissions-Policy.
Certificate Hygiene
Strengths: Issued by Let's Encrypt. Issues: Certificate expires in 19 days — renewal recommended; Wildcard certificate in use — broader attack surface if compromised.
Known Breaches
No known breaches found in public disclosure databases.
DMARC / Email Security
Strengths: DMARC policy set to quarantine; SPF record present with hard-fail (-all); DKIM configured (selectors: google, mandrill, zendesk1, zendesk2).
CVE Exposure
Detected technologies: nginx/1.25.0. No high or critical CVEs found for detected versions.
Recommended actions
5 items
Steps to improve garten.co's security grade, ranked by impact.
1
Enable HSTS (HTTP Strict Transport Security)
The HSTS header is missing on garten.co. Without it, connections can be downgraded from HTTPS to HTTP via man-in-the-middle attacks. This is a straightforward server configuration change.
Compliance impact
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://garten.co | grep -i strict
4
Submit to hstspreload.org after confirming the header is correct
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 garten.co 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 .co TLD
4
Verify: dig +dnssec garten.co
3
Review certificate configuration — expires in 19 days
Certificate issues found for garten.co: certificate expires in 19 days; 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
4
Upgrade to TLS 1.3
garten.co negotiated TLSv1.2. TLS 1.2 is still compliant under all major security frameworks and is not a vulnerability. TLS 1.3 offers faster handshakes and removes legacy cipher negotiation. This is a best-practice improvement, not a compliance gap.
How to fix this
1
Update web server config to prefer TLS 1.3 (nginx: ssl_protocols TLSv1.2 TLSv1.3)
2
Verify: openssl s_client -connect garten.co:443 -tls1_3
5
Add optional security headers (CSP, Permissions-Policy)
garten.co has most security headers configured. Missing: CSP, Permissions-Policy. These are best-practice additions that reduce the attack surface for client-side vulnerabilities.
How to fix this
1
Add Content-Security-Policy header (start with report-only to avoid breakage)
2
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
3
Verify with: curl -sI https://garten.co | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
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=quarantine
Strengths: DMARC policy set to quarantine; SPF record present with hard-fail (-all); DKIM configured (selectors: google, mandrill, zendesk1, zendesk2).
SPF Record
Present
v=spf1 include:_u.garten.co._spf.dmarclc.com include:mail.zendesk.com include:spf.zoho.com include:t
Security Headers
3/5 present
Missing: CSP, 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
Issues
Strengths: Issued by Let's Encrypt. Issues: Certificate expires in 19 days — renewal recommended; Wildcard certificate in use — broader attack surface if compromised.
DNSSEC
Not enabled
Strengths: 4 nameservers configured (ns-2018.awsdns-60.co.uk., ns-746.awsdns-29.net., ns-1117.awsdns-11.org., ns-200.awsdns-25.com.); 4 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.