Overview
Findings
Actions
Details
Related
LynxRadar → Directory → okcredit.in
A
95 / 100

okcredit.in

Security report · Scanned February 18, 2026

Checks
8
Passed
7
Warnings
1
Critical
0
AI-Generated Summary
What this means

okcredit.in scored 95/100, demonstrating a strong security posture. Minor improvements are noted below.

Positive signals: Known Breaches, TLS Configuration, HSTS Header all passed.

1 action item 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 okcredit.in compares

Grade distribution across 2378 companies we've scanned. okcredit.in scores better than 96% of them.

96th percentile
0 Percentile rank 100
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
okcredit.in — Grade A (95/100) 2378 companies scanned
Security checks

Each check inspects a different part of okcredit.in's public security setup. Green means healthy, yellow needs attention, red is a problem.

Certificate Hygiene
Strengths: Certificate valid, 56 days remaining; Issued by Let's Encrypt. Issues: Wildcard certificate in use — broader attack surface if compromised.
Needs work
Known Breaches
No known breaches found in public disclosure databases.
Healthy
TLS Configuration
TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
Healthy
HSTS Header
HSTS enabled: max-age=31536000 with includeSubDomains and preload. Meets best-practice configuration.
Healthy
Security Headers
4/5 security headers present. Missing: Permissions-Policy.
Healthy
DNS Configuration
Strengths: 4 nameservers configured (ns-cloud-c4.googledomains.com., ns-cloud-c3.googledomains.com., ns-cloud-c2.googledomains.com., ns-cloud-c1.googledomains.com.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.
Healthy
CVE Exposure
Detected technologies: istio-envoy, Proxy/CDN. (istio-envoy, Proxy/CDN detected but excluded from CVE matching — upstream infrastructure). All detected technologies are upstream CDN/proxy infrastructure. No application-level software versions exposed.
Healthy
DMARC / Email Security
Strengths: DMARC policy set to reject (strongest); SPF record present with soft-fail (~all); DKIM configured (selectors: google, s1, s2).
Healthy
Recommended actions
1 item

Steps to improve okcredit.in's security grade, ranked by impact.

1
Review certificate configuration
Impact: 1–2 Hours
LOW
Certificate issues found for okcredit.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=reject
Strengths: DMARC policy set to reject (strongest); SPF record present with soft-fail (~all); DKIM configured (selectors: google, s1, s2).
SPF Record
Present
v=spf1 include:_spf.google.com ~all
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
Issues
Strengths: Certificate valid, 56 days remaining; Issued by Let's Encrypt. Issues: Wildcard certificate in use — broader attack surface if compromised.
DNSSEC
Enabled
Strengths: 4 nameservers configured (ns-cloud-c4.googledomains.com., ns-cloud-c3.googledomains.com., ns-cloud-c2.googledomains.com., ns-cloud-c1.googledomains.com.); 5 MX records present; DNSSEC enabled; Zone transfers properly restricted.