Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
groww.in scored 80/100, demonstrating a strong security posture. Minor improvements are noted below.
Critical gaps in: Security Headers. Positive signals: Known Breaches, DNS Configuration, TLS Configuration 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 groww.in compares
Grade distribution across 2599 companies we've scanned. groww.in scores better than 64% of them.
84
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
groww.in — Grade B- (80/100)
2599 companies scanned
Security checks
Each check inspects a different part of groww.in's public security setup. Green means healthy, yellow needs attention, red is a problem.
Security Headers
Only 2/5 security headers present. Missing: CSP, Referrer-Policy, Permissions-Policy. This exposes the application to clickjacking, MIME-sniffing, and other client-side attacks.
HSTS Header
HSTS present but max-age is low (15552000s). Recommended minimum: 15768000 (6 months).
Certificate Hygiene
Strengths: Certificate valid, 53 days remaining; Issued by GoDaddy.com, Inc.. Issues: Wildcard certificate in use — broader attack surface if compromised.
DNS Configuration
Strengths: 2 nameservers configured (nicole.ns.cloudflare.com., norm.ns.cloudflare.com.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.
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.
DMARC / Email Security
Strengths: DMARC policy set to quarantine; SPF record present with hard-fail (-all); DKIM configured (selectors: google, s1, s2).
CVE Exposure
Detected technologies: cloudflare, Proxy/CDN. (cloudflare, Proxy/CDN detected but excluded from CVE matching — upstream infrastructure). All detected technologies are upstream CDN/proxy infrastructure. No application-level software versions exposed.
Recommended actions
3 items
Steps to improve groww.in's security grade, ranked by impact.
1
Add missing security headers (CSP, Referrer-Policy, Permissions-Policy)
3 of 5 recommended security headers are missing on groww.in: CSP, Referrer-Policy, Permissions-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: Referrer-Policy: strict-origin-when-cross-origin
3
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
4
Verify with: curl -sI https://groww.in | 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
Increase HSTS max-age duration
HSTS is enabled but the max-age (0s) is below the recommended minimum of 15768000s (6 months). A short max-age means browsers forget the HTTPS-only policy quickly, reducing protection between visits.
Compliance impact
PCI-DSS 4.0Req 6.4.1
Application security header configuration
How to fix this
1
Update header: Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
2
Verify: curl -sI https://groww.in | grep -i strict
3
Review certificate configuration
Certificate issues found for groww.in: 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 hard-fail (-all); DKIM configured (selectors: google, s1, s2).
SPF Record
Present
v=spf1 include:amazonses.com include:ncapp02.com include:_spf.google.com ip4:34.93.185.212 ip4:35.20
Security Headers
2/5 present
Missing: CSP, Referrer-Policy, Permissions-Policy
HSTS
Not enabled
HSTS present but max-age is low (15552000s). Recommended minimum: 15768000 (6 months).
SSL Certificate
Issues
Strengths: Certificate valid, 53 days remaining; Issued by GoDaddy.com, Inc.. Issues: Wildcard certificate in use — broader attack surface if compromised.
DNSSEC
Enabled
Strengths: 2 nameservers configured (nicole.ns.cloudflare.com., norm.ns.cloudflare.com.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.