Is okcredit.in safe to use as a vendor?

okcredit.in scored 95/100 on LynxRadar's security posture assessment. The domain meets baseline security requirements. 9 checks passed, 1 warnings, 0 critical issues across 10 passive checks including TLS, DMARC, security headers, breaches, and CVEs.

What TLS version does okcredit.in use?

okcredit.in uses TLSv1.3 with TLS_AES_256_GCM_SHA384. TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.

Does okcredit.in have DMARC configured?

Yes. okcredit.in's DMARC policy is set to 'reject'. SPF record: yes. Strengths: DMARC policy set to reject (strongest); SPF record present with soft-fail (~all); DKIM configured (selectors: google, s1, s2).

Does okcredit.in have SPF configured?

Yes. SPF record: v=spf1 include:_spf.google.com ~all

Does okcredit.in have security headers configured?

okcredit.in has 4 of 5 recommended security headers. Present: CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy. Missing: Permissions-Policy.

Does okcredit.in use HSTS?

Yes. HSTS enabled: max-age=31536000 with includeSubDomains and preload. Meets best-practice configuration.

Has okcredit.in been involved in a data breach?

No known breaches found. No known breaches found in public disclosure databases.

Does okcredit.in have known CVE vulnerabilities?

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.

Does okcredit.in have DNSSEC enabled?

Yes. 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.

okcredit.in Security Report — Grade A (95/100)

Q: Is okcredit.in's SSL certificate valid?

Issues detected. Strengths: Certificate valid, 56 days remaining; Issued by Let's Encrypt. Issues: Wildcard certificate in use — broader attack surface if compromised.

Trust rating

Excellent · 95/100

Procurement snapshot

No critical findings. The 1 remaining item is configuration gap, not architectural problems.

Strengths

Known Breaches

TLS Configuration

HSTS Header

Security Headers

Estimated remediation effort: 1–2 days

Based on a passive external scan — supplement with vendor-provided attestations, not a replacement.

Trust Score Trend

→ No change 1 scan · Last scanned February 18, 2026

Your rating Industry average

Score

100 75 50 25 0

okcredit.in

95/100

Compliance & Certifications

Not yet verified

SOC 2 Type II

Audit report not on file

3rd party · AICPA

Pro subscribers only

ISO 27001

Certificate not on file

3rd party · accredited body

Pro subscribers only

GDPR

DPA not on file

Self-reported

Pro subscribers only

Incident History

None in 12 months

March 2026

ChatGPT data exposure

1 source

Resolved

Pro subscribers only

April 2023 – Feb 2026

ChatGPT data exposure

1 source

Resolved

Pro subscribers only

Security Posture

1 item need attention

9 passed

Tidy up your SSL certificate setup

Certificate Hygiene

1–2 hours

This is a minor certificate-hygiene item, not an active risk. Nothing urgent here, but worth cleaning up: you're using a "wildcard" certificate that covers every subdomain at once. A wildcard certificate is convenient, but if it's ever compromised, every subdomain is exposed at once — separate certificates per subdomain limit that risk. The main thing to check is that renewal happens automatically so this doesn't become urgent later.

How to fix this

1Check that your certificate renews itself automatically (most hosts and Let's Encrypt do this by default — look for "auto-renew" in your hosting dashboard).

2Consider using separate certificates for sensitive subdomains instead of one wildcard covering everything.

3Stick to one certificate provider (e.g. Let's Encrypt) rather than mixing several — it's easier to track renewals.

View all 9 passed checks

Known Breaches

TLS Configuration

HSTS Header

Security Headers

DNS Configuration

CVE Exposure

DMARC / Email Security

MX Records & Mail Provider

Subprocessors & Tech Stack

Company Signals

Claim profile →

Operational risk

Low

11 yrs operating. Well-funded

Lynxradar · Composite signal

Last funding

$40B

Series F · Mar 2025 · SoftBank-led

Crunchbase ↗

Employees

~3,000

+40% YoY growth

LinkedIn ↗

Trust Resources

Claim profile →

Trust Center

trust.okcredit.in ↗

Security page

okcredit.in/security ↗

okcredit.in/privacy ↗

DPA (Data Processing Agreement)

okcredit.in/dpa ↗

Updated recently

Subprocessors List

okcredit.in/policies/subprocessors ↗

Similar companies in B2B SaaS / Software

Appears in

Claim profile →

SOC 2 Type II certified vendors

847 companies · Updated weekly by LynxRadar

Track

ISO 27001 certified SaaS

312 companies · Updated weekly by LynxRadar

Track

Top AI vendors by trust score

94 companies · LynxRadar ranking

Track

Enterprise-ready SaaS · Trust score A or above

203 companies · LynxRadar ranking

Track

Best Practice

Issues

Strengths: Certificate valid, 56 days remaining; Issued by Let's Encrypt. Issues: Wildcard certificate in use — broader attack surface if compromised.

Likelihood: ★★☆☆☆

Impact: ★★☆☆☆