Is kali.org safe to use as a vendor?

kali.org scored 75/100 on LynxRadar's security posture assessment. The domain partially meets security requirements with some gaps to address. 9 checks passed, 6 warnings, 0 critical issues across 16 passive checks including TLS, DMARC, security headers, breaches, and CVEs.

What TLS version does kali.org use?

kali.org 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 kali.org have SPF configured?

Yes. SPF record found: v=spf1 a ip4:208.88.127.98 ip4:52.44.83.41 include:_spf.google.com include:sendg...

Does kali.org have security headers configured?

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

Has kali.org been involved in a data breach?

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

Does kali.org 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.

kali.org Security Report — Grade C (75/100)

Q: Does kali.org have DMARC configured?

Yes. kali.org's DMARC policy is set to 'none'. SPF record: yes. Strengths: DMARC pct=100 — policy applies to all mail; Aggregate reports (rua) configured; Forensic reports (ruf) configured; SPF soft-fail (~all) configured; SPF DNS lookup count: 3/10 (within limit); DKIM configured (selectors: google). Issues: DMARC policy is 'none' (monitoring only, no enforcement).

Q: Does kali.org use HSTS?

Partially. HSTS configured with max-age=2592000s (30 days) — below the recommended 180-day minimum (15552000s). Browsers will enforce HTTPS but the policy caches for a short window. Increase max-age to 15552000 or higher.

Q: Is kali.org's SSL certificate valid?

Issues detected. Strengths: Certificate valid, 54 days remaining; Issued by Google Trust Services; 4809 certificates logged in CT. Issues: Certificates issued by 11 different CAs (threshold: 8 for 4809 logged certs) — possible misconfiguration or shadow IT. Note: Wildcard certificate in use (*.domain) — covers all subdomains. Common practice; worth noting that compromise would affect all subdomains.

Q: Does kali.org have DNSSEC enabled?

No. Strengths: 2 nameservers configured (nina.ns.cloudflare.com, nash.ns.cloudflare.com); SOA record present and MNAME consistent with NS set; 5 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 partially configured: DNSKEY present at apex but DS record is absent from the parent zone — resolvers cannot validate signatures. Upload the DS record at your domain registrar to complete the chain of trust..

Trust rating

Fair · 75/100

Procurement snapshot

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

Strengths

MX Records & Mail Provider

DNS CAA Records

TLS Configuration

TLS Protocol Support

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 October 17, 2026

Score

100 75 50 25 0

kali.org

75/100

Compliance & Certifications

Not yet verified

SOC 2 Type II

Audit report not on file

3rd party · AICPA

ISO 27001

Certificate not on file

3rd party · accredited body

GDPR

DPA not on file

Self-reported

CCPA

Self-reported

Incident History

No public breaches on record

Security Posture

6 items need attention

9 passed

Finish turning on DNSSEC (one record left)

DNS Configuration

30 minutes High

DNS responses for this domain currently have no real protection against tampering. DNSSEC is half set up for kali.org — the signing part is done, but one more record (called a "DS record") still needs to be copied over to your domain registrar to finish activating it. Until then, it provides no protection.

NIST 800-53SC-20

Secure name/address resolution service

How to fix this

1Log in to your domain registrar (the company you bought the domain from — not necessarily your DNS/website host).

2Find the "DNSSEC" or "DS records" section of the domain's settings.

3Go to your DNS provider's dashboard in your Cloudflare DNS dashboard (https://developers.cloudflare.com/dns/manage-dns-records/how-to/create-dns-records/), copy the DS record shown there, and paste it into the registrar.

4Confirm it worked: search "dnssec checker" and enter kali.org.

DNSSEC guide

Report unlocked.

View all 9 passed checks

MX Records & Mail Provider

DNS CAA Records

TLS Configuration

TLS Protocol Support

Known Breaches

security.txt (RFC 9116)

Cookie Security

Subprocessors & Tech Stack

CVE Exposure

Couldn't check: Malware / Phishing Blocklist — the check didn't complete (the site blocked or timed out our scanner, or a data source was unavailable), so this isn't counted in the score.

Company Signals

Operational risk

Last funding

Employees

Trust Resources

Claim profile →

Trust Center

Not detected

Security contact (security.txt)

kali.org/.well-known/security.txt

DPA (Data Processing Agreement)

Subprocessors List

Similar companies

Appears in

Vendors graded C

720 companies · LynxRadar ranking

High Priority

Not enabled

Strengths: 2 nameservers configured (nina.ns.cloudflare.com, nash.ns.cloudflare.com); SOA record present and MNAME consistent with NS set; 5 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 partially configured: DNSKEY present at apex but DS record is absent from the parent zone — resolvers cannot validate signatures. Upload the DS record at your domain registrar to complete the chain of trust..

Likelihood: ★★☆☆☆

Impact: ★★★☆☆

p=none

Strengths: DMARC pct=100 — policy applies to all mail; Aggregate reports (rua) configured; Forensic reports (ruf) configured; SPF soft-fail (~all) configured; SPF DNS lookup count: 3/10 (within limit); DKIM configured (selectors: google). Issues: DMARC policy is 'none' (monitoring only, no enforcement).

Likelihood: ★★★☆☆

Impact: ★★★☆☆

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

HSTS configured with max-age=2592000s (30 days) — below the recommended 180-day minimum (15552000s). Browsers will enforce HTTPS but the policy caches for a short window. Increase max-age to 15552000 or higher.

Likelihood: ★★☆☆☆

Impact: ★★☆☆☆

Best Practice

4/5 present

Missing: CSP

Likelihood: ★★☆☆☆

Impact: ★☆☆☆☆

Issues

Strengths: Certificate valid, 54 days remaining; Issued by Google Trust Services; 4809 certificates logged in CT. Issues: Certificates issued by 11 different CAs (threshold: 8 for 4809 logged certs) — possible misconfiguration or shadow IT. Note: Wildcard certificate in use (*.domain) — covers all subdomains. Common practice; worth noting that compromise would affect all subdomains.

Likelihood: ★★☆☆☆

Impact: ★★☆☆☆