SaaS Ranking
Menu

Egress

egress.com · Email security · checked 2026-09-03

39/100EBand E

Rank 7 of 18 in Email security, where the median is 28.

We measured 12 of 12 criteria for Egress on 2026-09-03. We found 4 with a source and did not find 8 at the addresses we checked. That is a transparency score of 39 out of 100, band E.

Overview

Transparency labelsaas-ranking.com

Egress

egress.com · Email security

  1. A
  2. B
  3. C
  4. D
  5. E
  6. F
E 39of 100 Rank 7 of 18

Published commitments3 of 9 found

Measured behaviour1 of 3 found

Checked 2026-09-03. Every line links the page we found it on. A cross means we found nothing at the addresses we checked, not that the vendor has no such document. A transparency score, not a product rating.

We do not issue badges: a badge is the first step towards a paid placement, and there is none here. The SVG is a document with the date in it, for your own files.

The label is the whole measurement in one object: every criterion with its weight, the band, and the date. Public transparency score, not a product or security rating.

Every line in it links the page we found the result on, or lists the addresses we checked. A cross means we found nothing there, not that Egress has no such document.

Gaps, heaviest first

✗

Subprocessor list

weight 3 of 3

No subprocessor list found.

Checked 7 addresses on 2026-09-03.

Show the 7 addresses we checked
  1. https://egress.com/legal/subprocessors – reached, no match (HTTP 200)
  2. https://egress.com/subprocessors – reached, no match (HTTP 200)
  3. https://egress.com/sub-processors – reached, no match (HTTP 200)
  4. https://egress.com/legal/sub-processors – blocked or unavailable (HTTP 403)
  5. https://egress.com/trust/subprocessors – reached, no match (HTTP 200)
  6. https://egress.com/privacy/subprocessors – reached, no match (HTTP 200)
  7. https://egress.com/legal/subprocessor-list – reached, no match (HTTP 200)

Is this wrong? Send us the URL

✗

Status page with history

weight 2 of 3

No public status page found.

Checked 3 addresses on 2026-09-03.

Show the 3 addresses we checked
  1. https://status.egress.com/ – No answer within 10 seconds.
  2. https://egress.com/status – reached, no match (HTTP 200)
  3. https://egress.com.statuspage.io/ – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

✗

Public pricing

weight 2 of 3

No public pricing with figures found.

Checked 5 addresses on 2026-09-03.

Show the 5 addresses we checked
  1. https://egress.com/pricing – reached and rendered, no match
  2. https://egress.com/pricing/ – reached, no match (HTTP 200)
  3. https://egress.com/plans – reached, no match (HTTP 200)
  4. https://egress.com/en/pricing – reached, no match (HTTP 200)
  5. https://egress.com/pricing-plans – reached, no match (HTTP 200)

Is this wrong? Send us the URL

✗

No third-party tracking before consent

weight 2 of 3

No consent-free first load found.

Checked 1 address on 2026-09-03.

Show the 1 address we checked
  1. https://egress.com/ – third-party requests before any interaction: 7052064.fs1.hubspotusercontent-na1.net, ad.doubleclick.net, alb.reddit.com, analytics.revsure.cloud, api.hubapi.com, api.rudderstack.com, app.hubspot.com, assets.revsure.cloud, b.6sc.co, bat.bing.com, bzr.openai.com, bzrcdn.openai.com, c.6sc.co, cta-service-cms2.hubspot.com, e.clarity.ms, epsilon.6sense.com, ipv6.6sc.co, j.6sc.co, js.hs-analytics.net, js.hs-banner.com, js.hsadspixel.net, js.hubspot.com, js.usemessages.com, js.zi-scripts.com, perf-na1.hsforms.com, player.vimeo.com, px.ads.linkedin.com, region1.analytics.google.com, scout-cdn.salesloft.com, scout.salesloft.com, scripts.clarity.ms, secure.adnxs.com, snap.licdn.com, stats.g.doubleclick.net, track.hubspot.com, tracking-api.g2.com, tracking.g2crowd.com, www.clarity.ms, www.google.com, www.google.de, www.googletagmanager.com, www.knowbe4.com, www.redditstatic.com

Is this wrong? Send us the URL

✗

Notice before subprocessors change

weight 2 of 3

No commitment to give notice before subprocessors change found.

Checked 8 addresses on 2026-09-03.

Show the 8 addresses we checked
  1. https://egress.com/legal/subprocessors – reached, no match (HTTP 200)
  2. https://egress.com/subprocessors – reached, no match (HTTP 200)
  3. https://egress.com/sub-processors – reached, no match (HTTP 200)
  4. https://egress.com/legal/dpa – reached, no match (HTTP 200)
  5. https://egress.com/dpa – reached, no match (HTTP 200)
  6. https://egress.com/legal/data-processing-agreement – reached, no match (HTTP 200)
  7. https://egress.com/trust/subprocessors – reached, no match (HTTP 200)
  8. https://egress.com/legal/sub-processors – blocked or unavailable (HTTP 403)

Is this wrong? Send us the URL

✗

Certifications named

weight 1 of 3

No named certification found.

Checked 6 addresses on 2026-09-03.

Show the 6 addresses we checked
  1. https://egress.com/security – reached, no match (HTTP 200)
  2. https://egress.com/trust – reached, no match (HTTP 200)
  3. https://egress.com/trust-center – reached, no match (HTTP 200)
  4. https://egress.com/compliance – reached, no match (HTTP 200)
  5. https://egress.com/legal/security – reached, no match (HTTP 200)
  6. https://trust.egress.com/ – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

✗

Uptime SLA with a figure

weight 1 of 3

No uptime figure found.

Checked 6 addresses on 2026-09-03.

Show the 6 addresses we checked
  1. https://egress.com/legal/sla – reached, no match (HTTP 200)
  2. https://egress.com/sla – reached, no match (HTTP 200)
  3. https://egress.com/legal/service-level-agreement – reached, no match (HTTP 200)
  4. https://egress.com/trust/sla – reached, no match (HTTP 200)
  5. https://egress.com/uptime – reached, no match (HTTP 200)
  6. https://egress.com/legal/uptime-sla – reached, no match (HTTP 200)

Is this wrong? Send us the URL

✗

security.txt (RFC 9116)

weight 1 of 3

No security.txt found.

Checked 1 address on 2026-09-03.

Show the 1 address we checked
  1. https://egress.com/.well-known/security.txt – reached, no match (HTTP 200)

Is this wrong? Send us the URL

Evidence

The full source lists sit behind these two groups, so that the answer above stays readable.

Published, with a source 4
✓

Data processing agreement

weight 3 of 3

Published and readable without a login.

Source: https://www.knowbe4.com/legal/global-data-processing-addendum · checked 2026-09-03

✓

Data location stated

weight 3 of 3

The hosting location is stated on a public page.

Source: https://www.knowbe4.com/legal/product-privacy-notice · checked 2026-09-03

✓

HTTPS enforced with HSTS

weight 2 of 3

HTTP redirects to HTTPS and the HSTS header is set.

Source: https://egress.com/ · checked 2026-09-03

✓

Named privacy contact

weight 1 of 3

A data protection officer or a dedicated privacy address is named.

Source: https://www.knowbe4.com/legal/product-privacy-notice · checked 2026-09-03

History

Not enough completed runs yet to draw a line. The next runs fill this in.

Compare