Is clear.in safe to use as a vendor?

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

What TLS version does clear.in use?

clear.in uses TLSv1.3 with TLS_AES_128_GCM_SHA256. TLSv1.3 negotiated with TLS_AES_128_GCM_SHA256 (128-bit). Strong configuration with no deprecated protocols or weak ciphers detected.

Does clear.in have DMARC configured?

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

Does clear.in have SPF configured?

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

Does clear.in have security headers configured?

clear.in has 5 of 5 recommended security headers. Present: CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy. All recommended headers present.

Does clear.in use HSTS?

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

Has clear.in been involved in a data breach?

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

Does clear.in have known CVE vulnerabilities?

Detected technologies: nginx, Proxy/CDN. (Proxy/CDN detected but excluded from CVE matching — upstream infrastructure). No version information exposed — CVE matching not possible (this is good practice).

clear.in Security Report — Grade A- (92/100)

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

Issues detected. Strengths: Certificate valid, 275 days remaining; Issued by Amazon. Issues: Wildcard certificate in use — broader attack surface if compromised.

Q: Does clear.in have DNSSEC enabled?

No. Strengths: 4 nameservers configured (ns-15.awsdns-01.com., ns-1800.awsdns-33.co.uk., ns-697.awsdns-23.net., ns-1133.awsdns-13.org.); 6 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.

A-

Pass · 92/100

Demonstrates a solid security posture with minor gaps. Positive signals: Known Breaches, TLS Configuration, and DMARC / Email Security all passed. 2 action items identified, including 0 critical. The issues are configuration gaps, not architectural problems. A focused remediation effort of 1–2 days could address all findings.

Trust Score Trend

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

Your rating Industry average

Score

100 75 50 25 0

A-

clear.in

92/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

2 items need attention

8 passed

Turn on DNSSEC for your domain

DNS Configuration

1–3 days (mostly waiting, not active work)

This allows an attacker to silently redirect your visitors to a fake site. DNSSEC is a signature system that stops attackers from forging DNS answers — without it, someone could redirect visitors of clear.in to a fake site without them noticing. Turning it on takes coordination between your DNS provider and your domain registrar, but it's a one-time setup.

NIST 800-53SC-20

Secure name/address resolution service

How to fix this

1Check whether your DNS provider supports DNSSEC in your DNS provider's dashboard (whichever company manages this domain's DNS — often your registrar, e.g. GoDaddy, Namecheap, or Cloudflare) — most major ones do (Cloudflare, Route53, GoDaddy, Namecheap).

2Turn on DNSSEC signing there — it will generate a DS record for you.

3Copy that DS record into your domain registrar's DNSSEC settings for the .in domain.

4Confirm it worked: search "dnssec checker" and enter clear.in.

DNSSEC guide

Report unlocked.

View all 8 passed checks

Known Breaches

TLS Configuration

DMARC / Email Security

MX Records & Mail Provider

HSTS Header

Security Headers

CVE Exposure

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.clear.in ↗

Security page

clear.in/security ↗

clear.in/privacy ↗

DPA (Data Processing Agreement)

clear.in/dpa ↗

Updated recently

Subprocessors List

clear.in/policies/subprocessors ↗

Tech Stack Detected

Subprocessors

Amazon CloudFront

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

Medium Priority

Not enabled

Strengths: 4 nameservers configured (ns-15.awsdns-01.com., ns-1800.awsdns-33.co.uk., ns-697.awsdns-23.net., ns-1133.awsdns-13.org.); 6 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.

Likelihood: ★★☆☆☆

Impact: ★★★☆☆

Best Practice

Issues

Strengths: Certificate valid, 275 days remaining; Issued by Amazon. Issues: Wildcard certificate in use — broader attack surface if compromised.

Likelihood: ★★☆☆☆

Impact: ★★☆☆☆