Mobile.de
mobile.de · Automotive retail software · checked 2026-09-03
- 1 found
- 2 not found
- 9 not measured
We measured 3 of 12 criteria for Mobile.de on 2026-09-03. We found 1 with a source and did not find 2 at the addresses we checked; 9 we could not measure at all. Below our threshold there is no score and no rank, and that is a statement about our measurement.
Overview
Transparency labelsaas-ranking.com
Mobile.de
- A
- B
- C
- D
- E
- F
Published commitments9 not measured
- not measuredData processing agreement×3
- not measuredSubprocessor list×3
- not measuredData location stated×3
- not measuredStatus page with history×2
- not measuredPublic pricing×2
- not measuredNotice before subprocessors change×2
- not measuredCertifications named×1
- not measuredUptime SLA with a figure×1
- not measuredNamed privacy contact×1
Measured behaviour1 of 3 found
- not foundHTTPS enforced with HSTS×2
- not foundNo third-party tracking before consent×2
- foundsecurity.txt (RFC 9116)×1
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. We could measure 3 of 12 criteria, which is below our threshold, so there is no rank. That is a statement about our measurement, not about Mobile.de.
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 Mobile.de has no such document.
Gaps, heaviest first
HTTPS enforced with HSTS
weight 2 of 3No enforced HTTPS with HSTS found.
Checked 2 addresses on 2026-09-03.
Show the 2 addresses we checked
http://mobile.de/– redirects to https://mobile.de/https://mobile.de/– no HSTS header
No third-party tracking before consent
weight 2 of 3No consent-free first load found.
Checked 1 address on 2026-09-03.
Show the 1 address we checked
https://mobile.de/– third-party requests before any interaction: static.classistatic.de
Evidence
The full source lists sit behind these two groups, so that the answer above stays readable.
Published, with a source 1
security.txt (RFC 9116)
weight 1 of 3Served at /.well-known/security.txt.
Source: https://www.mobile.de/.well-known/security.txt · checked 2026-09-03
Not measured by us 9
Data processing agreement
weight 3 of 3Not measured. The vendor’s server blocked or rate-limited our crawler, so this was not measured.
Show the 8 addresses we checked
https://mobile.de/legal/dpa– blocked or unavailable (HTTP 403)https://mobile.de/dpa– blocked or unavailable (HTTP 403)https://mobile.de/legal/data-processing-agreement– blocked or unavailable (HTTP 403)https://mobile.de/data-processing-agreement– blocked or unavailable (HTTP 403)https://mobile.de/legal/data-processing-addendum– blocked or unavailable (HTTP 403)https://mobile.de/legal/gdpr– blocked or unavailable (HTTP 403)https://mobile.de/trust/dpa– blocked or unavailable (HTTP 403)https://mobile.de/privacy/dpa– blocked or unavailable (HTTP 403)
Subprocessor list
weight 3 of 3Not measured. The vendor’s server blocked or rate-limited our crawler, so this was not measured.
Show the 7 addresses we checked
https://mobile.de/legal/subprocessors– blocked or unavailable (HTTP 403)https://mobile.de/subprocessors– blocked or unavailable (HTTP 403)https://mobile.de/sub-processors– blocked or unavailable (HTTP 403)https://mobile.de/legal/sub-processors– blocked or unavailable (HTTP 403)https://mobile.de/trust/subprocessors– blocked or unavailable (HTTP 403)https://mobile.de/privacy/subprocessors– blocked or unavailable (HTTP 403)https://mobile.de/legal/subprocessor-list– blocked or unavailable (HTTP 403)
Data location stated
weight 3 of 3Not measured. The vendor’s server blocked or rate-limited our crawler, so this was not measured.
Show the 7 addresses we checked
https://mobile.de/security– blocked or unavailable (HTTP 403)https://mobile.de/trust– blocked or unavailable (HTTP 403)https://mobile.de/legal/privacy– blocked or unavailable (HTTP 403)https://mobile.de/privacy– blocked or unavailable (HTTP 403)https://mobile.de/privacy-policy– blocked or unavailable (HTTP 403)https://mobile.de/compliance– blocked or unavailable (HTTP 403)https://mobile.de/legal/privacy-policy– blocked or unavailable (HTTP 403)
Status page with history
weight 2 of 3Not measured. The vendor’s server blocked or rate-limited our crawler, so this was not measured.
Show the 3 addresses we checked
https://status.mobile.de/– blocked or unavailable (HTTP 403)https://mobile.de/status– blocked or unavailable (HTTP 403)https://mobile.de.statuspage.io/– Could not be fetched: fetch failed.
Public pricing
weight 2 of 3Not measured. The vendor’s server blocked or rate-limited our crawler, so this was not measured.
Show the 5 addresses we checked
https://mobile.de/pricing– blocked or unavailable (HTTP 403)https://mobile.de/pricing/– blocked or unavailable (HTTP 403)https://mobile.de/plans– blocked or unavailable (HTTP 403)https://mobile.de/en/pricing– blocked or unavailable (HTTP 403)https://mobile.de/pricing-plans– blocked or unavailable (HTTP 403)
Notice before subprocessors change
weight 2 of 3Not measured. The vendor’s server blocked or rate-limited our crawler, so this was not measured.
Show the 8 addresses we checked
https://mobile.de/legal/subprocessors– blocked or unavailable (HTTP 403)https://mobile.de/subprocessors– blocked or unavailable (HTTP 403)https://mobile.de/sub-processors– blocked or unavailable (HTTP 403)https://mobile.de/legal/dpa– blocked or unavailable (HTTP 403)https://mobile.de/dpa– blocked or unavailable (HTTP 403)https://mobile.de/legal/data-processing-agreement– blocked or unavailable (HTTP 403)https://mobile.de/trust/subprocessors– blocked or unavailable (HTTP 403)https://mobile.de/legal/sub-processors– blocked or unavailable (HTTP 403)
Certifications named
weight 1 of 3Not measured. The vendor’s server blocked or rate-limited our crawler, so this was not measured.
Show the 6 addresses we checked
https://mobile.de/security– blocked or unavailable (HTTP 403)https://mobile.de/trust– blocked or unavailable (HTTP 403)https://mobile.de/trust-center– blocked or unavailable (HTTP 403)https://mobile.de/compliance– blocked or unavailable (HTTP 403)https://mobile.de/legal/security– blocked or unavailable (HTTP 403)https://trust.mobile.de/– blocked or unavailable (HTTP 403)
Uptime SLA with a figure
weight 1 of 3Not measured. The vendor’s server blocked or rate-limited our crawler, so this was not measured.
Show the 6 addresses we checked
https://mobile.de/legal/sla– blocked or unavailable (HTTP 403)https://mobile.de/sla– blocked or unavailable (HTTP 403)https://mobile.de/legal/service-level-agreement– blocked or unavailable (HTTP 403)https://mobile.de/trust/sla– blocked or unavailable (HTTP 403)https://mobile.de/uptime– blocked or unavailable (HTTP 403)https://mobile.de/legal/uptime-sla– blocked or unavailable (HTTP 403)
Named privacy contact
weight 1 of 3Not measured. The vendor’s server blocked or rate-limited our crawler, so this was not measured.
Show the 7 addresses we checked
https://mobile.de/legal/privacy– blocked or unavailable (HTTP 403)https://mobile.de/privacy– blocked or unavailable (HTTP 403)https://mobile.de/privacy-policy– blocked or unavailable (HTTP 403)https://mobile.de/legal/privacy-policy– blocked or unavailable (HTTP 403)https://mobile.de/legal/privacy-notice– blocked or unavailable (HTTP 403)https://mobile.de/trust/privacy– blocked or unavailable (HTTP 403)https://mobile.de/datenschutz– blocked or unavailable (HTTP 403)
History
Not enough completed runs yet to draw a line. The next runs fill this in.