SaaS Ranking
Menu

SMTPeter

smtpeter.com · Transactional email and notifications · checked 2026-09-05

36/100EBand E

Rank 12 of 32 in Transactional email and notifications, where the median is 28.

We measured 11 of 12 criteria for SMTPeter on 2026-09-05. We found 4 with a source and did not find 7 at the addresses we checked; 1 we could not measure at all. That is a transparency score of 36 out of 100, band E.

Overview

Transparency labelsaas-ranking.com

SMTPeter

smtpeter.com · Transactional email and notifications

  1. A
  2. B
  3. C
  4. D
  5. E
  6. F
E 36of 100 Rank 12 of 32

Published commitments3 of 9 found

Measured behaviour1 of 2 found, 1 not measured

Checked 2026-09-05. 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.

The evidence pack carries every criterion with its source, the addresses we checked, the date and the data snapshot id – the four things a procurement file needs and a screenshot loses. We do not issue badges: a badge is the first step towards a paid placement, and there is none here.

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 SMTPeter has no such document.

What they state

The exact figures and names we read off the pages linked below, with the sentence they stand in. This is what they publish, not what we verified about their systems.

Gaps, heaviest first

✗

Data processing agreement

weight 3 of 3

No data processing agreement found.

Checked 8 addresses on 2026-09-05.

Show the 8 addresses we checked
  1. https://smtpeter.com/legal/dpa – reached, no match (HTTP 404)
  2. https://smtpeter.com/dpa – reached, no match (HTTP 404)
  3. https://smtpeter.com/legal/data-processing-agreement – reached, no match (HTTP 404)
  4. https://smtpeter.com/data-processing-agreement – reached, no match (HTTP 404)
  5. https://smtpeter.com/legal/data-processing-addendum – reached, no match (HTTP 404)
  6. https://smtpeter.com/legal/gdpr – reached, no match (HTTP 404)
  7. https://smtpeter.com/trust/dpa – reached, no match (HTTP 404)
  8. https://smtpeter.com/privacy/dpa – reached, no match (HTTP 404)

Is this wrong? Send us the URL

✗

Subprocessor list

weight 3 of 3

No subprocessor list found.

Checked 7 addresses on 2026-09-05.

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

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-05.

Show the 3 addresses we checked
  1. https://status.smtpeter.com/ – The name "status.smtpeter.com" could not be resolved.
  2. https://smtpeter.com/status – reached, no match (HTTP 404)
  3. https://smtpeter.com.statuspage.io/ – Could not be fetched: fetch failed.

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-05.

Show the 1 address we checked
  1. https://smtpeter.com/ – third-party requests before any interaction: api.leadinfo.com, cdn.leadinfo.net, cdnjs.cloudflare.com, collector.leadinfo.net, collector4.leadinfo.net, fonts.gstatic.com, media.copernica.com, scriptkit.copernica.com, www.google.com, www.gstatic.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-05.

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

Is this wrong? Send us the URL

✗

Certifications named

weight 1 of 3

No named certification found.

Checked 6 addresses on 2026-09-05.

Show the 6 addresses we checked
  1. https://smtpeter.com/security – reached, no match (HTTP 404)
  2. https://smtpeter.com/trust – reached, no match (HTTP 404)
  3. https://smtpeter.com/trust-center – reached, no match (HTTP 404)
  4. https://smtpeter.com/compliance – reached, no match (HTTP 404)
  5. https://smtpeter.com/legal/security – reached, no match (HTTP 404)
  6. https://trust.smtpeter.com/ – The name "trust.smtpeter.com" could not be resolved.

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-05.

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

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 location stated

weight 3 of 3

The hosting location is stated on a public page.

Source: https://www.smtpeter.com/en/privacy-policy · checked 2026-09-05

✓

Public pricing

weight 2 of 3

Actual numbers on a public page.

Source: https://www.smtpeter.com/en/pricing/ · checked 2026-09-05

✓

HTTPS enforced with HSTS

weight 2 of 3

HTTP redirects to HTTPS and the HSTS header is set.

  • HSTS max-age 2678000 seconds (30 days).
    Show the exact wording

    max-age=2678000

    Read at https://smtpeter.com/

Source: https://smtpeter.com/ · checked 2026-09-05

✓

Named privacy contact

weight 1 of 3

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

Source: https://www.smtpeter.com/en/privacy-policy · checked 2026-09-05

Not measured by us 1
–

security.txt (RFC 9116)

weight 1 of 3

Not measured. The vendor’s server blocked or rate-limited our crawler, so this was not measured.

Show the 1 address we checked
  1. https://smtpeter.com/.well-known/security.txt – blocked or unavailable (HTTP 403)

Is this wrong? Send us the URL

History

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

Compare

A shortlist holds up to six vendors across categories and lives entirely in the address of its page: share the link, bookmark it, put it in a ticket. Nothing is stored, so we do not know it exists.