Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
goldbelly.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 goldbelly.com compares
Grade distribution across 2378 companies we've scanned. goldbelly.com scores better than 78% 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
goldbelly.com — Grade B (85/100)
2378 companies scanned
Security checks
Each check inspects a different part of goldbelly.com's public security setup. Green means healthy, yellow needs attention, red is a problem.
Security Headers
Only 1/5 security headers present. Missing: CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy. This exposes the application to clickjacking, MIME-sniffing, and other client-side attacks.
Certificate Hygiene
Strengths: Certificate valid, 34 days remaining; Issued by Let's Encrypt. Issues: Wildcard certificate in use — broader attack surface if compromised.
DNS Configuration
Strengths: 2 nameservers configured (apollo.ns.cloudflare.com., wally.ns.cloudflare.com.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.
TLS Configuration
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
Known Breaches
No known breaches found in public disclosure databases.
HSTS Header
HSTS enabled: max-age=63072000. Missing includeSubDomains. Missing preload directive.
DMARC / Email Security
Strengths: DMARC policy set to quarantine; SPF record present with soft-fail (~all); DKIM configured (selectors: google, s1, s2, k1, zendesk1, zendesk2).
CVE Exposure
Detected technologies: cloudflare, Next.js. (cloudflare detected but excluded from CVE matching — upstream infrastructure). No version information exposed — CVE matching not possible (this is good practice).
Recommended actions
2 items
Steps to improve goldbelly.com's security grade, ranked by impact.
1
Add missing security headers (CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy)
4 of 5 recommended security headers are missing on goldbelly.com: CSP, X-Content-Type-Options, X-Frame-Options, Referrer-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
Verify with: curl -sI https://goldbelly.com | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
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 goldbelly.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, s1, s2, k1, zendesk1, zendesk2).
SPF Record
Present
v=spf1 mx ip4:167.89.0.0/17 ip4:208.117.48.0/20 ip4:50.31.32.0/19 ip4:198.37.144.0/20 ip4:198.21.0.0
Security Headers
1/5 present
Missing: CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy
HSTS
Enabled
HSTS enabled: max-age=63072000. Missing includeSubDomains. Missing preload directive.
SSL Certificate
Issues
Strengths: Certificate valid, 34 days remaining; Issued by Let's Encrypt. Issues: Wildcard certificate in use — broader attack surface if compromised.
DNSSEC
Enabled
Strengths: 2 nameservers configured (apollo.ns.cloudflare.com., wally.ns.cloudflare.com.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.