Skip to content

No SSL Encryption Detected

It indicates that the domain does not support HTTPS or lacks an SSL/TLS certificate entirely. This means communication between the client and the server occurs over unencrypted HTTP, exposing sensitive data to interception or tampering.

Analyst Q&A

What this signal answers

Three questions every analyst asks before acting on this signal.

What it detects01

What does 'No SSL Encryption Detected' mean in SOC or web analysis?

It indicates that the domain does not support HTTPS or lacks an SSL/TLS certificate entirely. This means communication between the client and the server occurs over unencrypted HTTP, exposing sensitive data to interception or tampering.

Why it matters02

Why is the absence of SSL encryption considered risky?

Because without SSL/TLS, transmitted data—such as credentials, cookies, or session tokens—can be intercepted or modified by attackers. The lack of encryption also makes phishing or spoofing pages harder to detect by browsers.

How analysts use it03

Do all domains without SSL indicate malicious intent?

No. Some legacy or misconfigured domains may simply lack proper setup. However, in modern infrastructures, the absence of SSL is rare for legitimate services and is often seen in low-quality, abandoned, or malicious sites.

Often paired with:alert_only
Evidence shape

What No SSL Encryption Detected looks like in the response

A realistic shape of the entry the engine appends to the risk_signals array when this signal fires. Evidence keys are subgroup-default; per-signal overrides documented in the API reference.

json
{
  "slug": "no_ssl_usage",
  "name": "No SSL Encryption Detected",
  "group": "http_crawling_history",
  "subgroup": "ssl_behavior",
  "direction": "malicious",
  "evidence": {
    "cert_issued_days_ago": 9,
    "issuer": "letsencrypt",
    "valid_for_days": 90,
    "rotation_count_90d": 3,
    "cert_type": "DV"
  }
}
See in API reference
Siblings

Peers in SSL Behavior

15 other signals share the same subgroup. They detect related behaviors and often co-fire on the same IOC.

Critical SSL Certificate Authentication Failure

It means that the SSL/TLS certificate presented by the domain failed critical validation checks. This can occur due to m

MaliciousCore
Invalid Hostname Validation (CN/SAN Mismatch)

It means the SSL/TLS certificate’s Common Name (CN) or Subject Alternative Name (SAN) does not match the accessed domain

MaliciousCore
Organization-Validated (OV) SSL Certificate Detected

It means the SSL/TLS certificate of the domain includes verified organizational details that have been authenticated by

SafeCore
Self-Signed SSL Certificate Detected

It means the domain is using an SSL/TLS certificate that was generated and signed by the same entity, without verificati

MaliciousCore
Show 11 more in SSL Behavior
In the wild

See No SSL Encryption Detected fire on real IOCs

The Verdict Gallery is a curated stream of real verdicts. Filter by this signal to see exactly which IOCs it caught, what other signals fired alongside it, and what the engine recommended.

Open Verdict Gallery
Pre-filtered to No SSL Encryption Detected. See real IOCs this signal caught and the verdicts the engine returned.
Verdicts ✓

Start free, in five minutes

100 IOCs/day on the free tier, LLM layer included. No card required.