Is webaudit.in safe to use as a vendor?

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

What TLS version does webaudit.in use?

webaudit.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 webaudit.in have SPF configured?

Yes. SPF record: v=spf1 include:_spf.mx.cloudflare.net ~all

Does webaudit.in have security headers configured?

webaudit.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 webaudit.in use HSTS?

Yes. HSTS enabled: max-age=31536000s (365 days). includeSubDomains present. Missing preload directive.

Has webaudit.in been involved in a data breach?

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

Does webaudit.in have known CVE vulnerabilities?

Detected technologies: cloudflare. (cloudflare detected but excluded from CVE matching — upstream infrastructure). All detected technologies are upstream CDN/proxy infrastructure. No application-level software versions exposed.

webaudit.in Security Report — Grade B- (80/100)

Q: Does webaudit.in have DMARC configured?

Yes. webaudit.in's DMARC policy is set to 'quarantine'. SPF record: yes. Strengths: DMARC policy set to quarantine; DMARC pct=100 — policy applies to all mail; Aggregate reports (rua) configured; SPF soft-fail (~all) configured; SPF DNS lookup count: 1/10 (within limit). Issues: DMARC policy is 'quarantine', not 'reject' — spoofed mail is moved to spam rather than blocked outright; No DKIM records found for common selectors (domain may use custom selectors — this is not a confirmed gap).

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

Issues detected. Strengths: Certificate valid, 61 days remaining; Issued by Google Trust Services; 69 certificates logged in CT. Issues: Certificates issued by 4 different CAs (threshold: 3 for 69 logged certs) — possible misconfiguration or shadow IT.

Q: Does webaudit.in have DNSSEC enabled?

No. Strengths: 2 nameservers configured (simon.ns.cloudflare.com, sydney.ns.cloudflare.com); SOA record present and MNAME consistent with NS set; 3 MX record(s) present; Zone transfers properly restricted on all nameservers; Address records present: 2 A record(s), 2 AAAA record(s). Issues: All nameservers are from a single provider (cloudflare.com) — a provider outage takes down the domain; DNSSEC not configured — DNS responses can be spoofed or tampered with in transit (DNS cache poisoning).

B-

Trust rating

Good · 80/100

Procurement snapshot

No critical findings. The 6 remaining items are configuration gaps, not architectural problems.

Strengths

MX Records & Mail Provider

TLS Protocol Support

TLS Configuration

HSTS Header

Questions to ask

Confirm MTA-STS rollout plans for inbound email

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 July 22, 2026

Score

100 75 50 25 0

B-

webaudit.in

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

CCPA

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

6 items need attention

9 passed

Finish setting up email authentication

DMARC / Email Security

2–4 hours

Spoofed emails can still reach your customers and partners until this is fully enforced. Email authentication for webaudit.in is partly set up, but there are gaps: DKIM isn't set up. Until it's fully in place, someone could still send a convincing fake email pretending to be you.

NIST CSFPR.AC-7

Email authentication is a required access control

How to fix this

1Your MX records point to Cloudflare Email Routing, which forwards incoming mail to wherever you actually read it — it's a separate thing from sending. DKIM signs outbound mail, so it needs to be set up wherever you actually send email FROM (e.g. the service your team uses for newsletters, receipts, or day-to-day mail — this could be Cloudflare's own Email Sending feature if you've turned that on separately, or a different provider entirely). Check that service's admin settings for "DKIM".

2Double-check it's live: search "dmarc record checker" and enter webaudit.in.

Email authentication guide

Report unlocked.

View all 9 passed checks

MX Records & Mail Provider

TLS Protocol Support

TLS Configuration

HSTS Header

Cookie Security

security.txt (RFC 9116)

Known Breaches

Subprocessors & Tech Stack

CVE Exposure

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

Security page

webaudit.in/security ↗

webaudit.in/privacy ↗

DPA (Data Processing Agreement)

webaudit.in/dpa ↗

Updated recently

Subprocessors List

webaudit.in/policies/subprocessors ↗

Similar companies

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

Warn

Issues: No MTA-STS configured — email in transit is vulnerable to TLS downgrade attacks; sending servers cannot verify your mail server requires TLS; No TLSRPT record (_smtp._tls) — TLS delivery failures won't be reported to the domain owner.

Likelihood: ★★☆☆☆

Impact: ★★★☆☆

Not enabled

Strengths: 2 nameservers configured (simon.ns.cloudflare.com, sydney.ns.cloudflare.com); SOA record present and MNAME consistent with NS set; 3 MX record(s) present; Zone transfers properly restricted on all nameservers; Address records present: 2 A record(s), 2 AAAA record(s). Issues: All nameservers are from a single provider (cloudflare.com) — a provider outage takes down the domain; DNSSEC not configured — DNS responses can be spoofed or tampered with in transit (DNS cache poisoning).

Likelihood: ★★☆☆☆

Impact: ★★★☆☆

p=quarantine

Strengths: DMARC policy set to quarantine; DMARC pct=100 — policy applies to all mail; Aggregate reports (rua) configured; SPF soft-fail (~all) configured; SPF DNS lookup count: 1/10 (within limit). Issues: DMARC policy is 'quarantine', not 'reject' — spoofed mail is moved to spam rather than blocked outright; No DKIM records found for common selectors (domain may use custom selectors — this is not a confirmed gap).

Likelihood: ★★★☆☆

Impact: ★★★☆☆

Best Practice

Warn

No CAA records found in the DNS tree for this domain. Without CAA, any Certificate Authority can issue certificates for this domain. Adding CAA records restricts issuance to authorised CAs only, reducing the risk of misissued certificates.

Likelihood: ★☆☆☆☆

Impact: ★☆☆☆☆

5/5 present

All headers configured.

Likelihood: ★★☆☆☆

Impact: ★☆☆☆☆

Issues

Strengths: Certificate valid, 61 days remaining; Issued by Google Trust Services; 69 certificates logged in CT. Issues: Certificates issued by 4 different CAs (threshold: 3 for 69 logged certs) — possible misconfiguration or shadow IT.

Likelihood: ★★☆☆☆

Impact: ★★☆☆☆