Back to results

Digital exposure report

zalando.com

Critical findings in the observed public configuration. Some basic protections were not detected.

Scanned: 2026-11-15 19:22 UTC

Full coverage: every applicable check was assessed.

F
58/100

What to do first

  1. 1.

    Tell browsers to always use the secure version

    Helps browsers use HTTPS on future visits after they have received the policy.

    Who can fix it: Your web host

    How to verify after the fix

    curl -sIL https://zalando.com/ | grep -i "Strict-Transport-Security"
  2. 2.

    Limit what scripts your pages are allowed to run

    This adds one layer of protection against injected scripts.

    Who can fix it: Your website developer or web host

    How to verify after the fix

    curl -sIL https://zalando.com/ | grep -i "Content-Security-Policy"

A starting point, not a security guarantee.

What this grade means

Tested hostname
zalando.com
Website request
GET https://zalando.com/
Scan time
2026-11-15 19:22:42 UTC
Grading method
Version 2How grading works
Unverified or excluded checks
None. Every applicable check was assessed.

This is a snapshot of the public configuration checks listed in this report. It does not verify the site's owner, business legitimacy, application security, or absence of vulnerabilities. It is not a security certification.

Score by category

Email security30/30Spoofing email from this domain is hard.
Encryption & certificate25/25Traffic to the site is encrypted and the certificate is valid.
Browser protections0/30Several browser hardening headers are missing, which removes layers of protection against script injection and framing.
DNS infrastructure3/15The domain's infrastructure lacks basic protections.

Fix priorities

  1. 1.HighHSTS — enforce encryption in the browser · Hardening gap+8
  2. 2.MediumClickjacking protection · Hardening gap+5
  3. 3.MediumDNSSEC — signed DNS records · Hardening gap+7
  4. 4.MediumCSP — protection from script injection · Hardening gap+8
  5. 5.LowCAA — who may issue certificates · Hardening gap+5
  6. 6.LowX-Content-Type-Options · Hardening gap+4
  7. 7.LowReferrer-Policy · Hardening gap+3
  8. 8.LowPermissions-Policy · Hardening gap+2

Findings

SPF — who may send mail for the domain

Passed · Severity: OK · 10/10

An authorized sender list is defined and mail from other servers is rejected.

Valid SPF record with -all. 2 of the 10 allowed DNS lookups.

Source data: DNS TXT zalando.com
v=spf1 ip4:63.185.125.73 include:_spf.google.com ip4:80.237.155.68 ip4:195.71.68.47 ip4:149.96.14.2 ip4:185.85.220.205 include:_spf.salesforce.com -all
$ dig +short TXT zalando.com
Documentation: RFC 7208 — SPF (https://www.rfc-editor.org/rfc/rfc7208) · M3AAWG — Email Authentication Best Practices (https://www.m3aawg.org/sites/default/files/m3aawg-email-authentication-recommended-best-practices-09-2020.pdf)

DMARC — anti-spoofing policy

Passed · Severity: OK · 15/15

Forged email in the company's name is blocked by mail servers.

Policy p=reject.

Source data: DNS TXT _dmarc.zalando.com
v=DMARC1; p=reject; fo=1; rua=mailto:dmarc_rua@zalando.com; ruf=mailto:dmarc_ruf@zalando.com; adkim=s; pct=100;
$ dig +short TXT _dmarc.zalando.com
Documentation: RFC 7489 — DMARC (https://www.rfc-editor.org/rfc/rfc7489) · dmarc.org — FAQ (https://dmarc.org/resources/frequently-asked-questions/)

DKIM — digital signature on email

Passed · Severity: OK · 5/5

A DKIM public key is published. On its own this doesn't prove outgoing mail is signed or aligned with your From domain.

DKIM public key found for selector: google. Confirm signing with dkim=pass in a sent message's Authentication-Results.

Source data: DNS TXT <selector>._domainkey.zalando.com
google._domainkey: v=DKIM1;k=rsa;p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAsiJ5JH4s77DUTcORY/qbKzbu2LFDdB…
$ dig +short TXT google._domainkey.zalando.com
Documentation: RFC 6376 — DKIM (https://www.rfc-editor.org/rfc/rfc6376) · M3AAWG — Email Authentication Best Practices (https://www.m3aawg.org/sites/default/files/m3aawg-email-authentication-recommended-best-practices-09-2020.pdf)

MX — inbound mail routing

Passed · Severity: OK · unscored

Mail exchangers are published for the domain.

1 MX record(s). This shows where inbound mail is routed, not whether mail is sent from the domain.

Source data: DNS MX zalando.com
1 smtp.google.com
$ dig +short MX zalando.com
Documentation: RFC 7505 — Null MX (https://www.rfc-editor.org/rfc/rfc7505) · RFC 5321 §5.1 — Locating the target host (https://www.rfc-editor.org/rfc/rfc5321#section-5.1)

HTTPS available

Passed · Severity: OK · 10/10

The site loads over an encrypted connection.

https://zalando.com/ returned HTTP 200 (final URL: https://zalando.com/). Client-side certificate validation passed.

Source data: HTTPS GET https://zalando.com/
HTTP 200
Final URL: https://zalando.com/
$ curl -sIL https://zalando.com/
Documentation: OWASP — Transport Layer Security Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/Transport_Layer_Security_Cheat_Sheet.html) · Mozilla — Server Side TLS (https://wiki.mozilla.org/Security/Server_Side_TLS)

HTTP → HTTPS redirect

Passed · Severity: OK · 7/7

Visitors arriving at an unencrypted address are automatically sent to the secure version.

HTTP 301 → https://zalando.com/

Source data: HTTP GET http://zalando.com/ (redirects not followed)
HTTP 301
Location: https://zalando.com/
$ curl -sI http://zalando.com/ | grep -iE "^(HTTP|location)"
Documentation: OWASP — Transport Layer Security Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/Transport_Layer_Security_Cheat_Sheet.html) · RFC 6797 — HSTS (https://www.rfc-editor.org/rfc/rfc6797)

SSL/TLS certificate validity

Passed · Severity: OK · 8/8

The certificate was accepted by a validating TLS client at scan time.

Live TLS handshake succeeded. Latest issuance in CT logs: Amazon Trust Services, expiring 2027-04-08 (144 days). CT shows issued certificates, not necessarily the one served — confirm dates with the verify command.

Source data: Certificate Transparency logs (certspotter) for zalando.com
Live TLS handshake: certificate accepted
CT logs (context only, not scored):
Issuer: Amazon Trust Services
Valid from: 2026-09-23
Valid until: 2027-04-08
Names: *.zalando.com, *.zalando.com.au, *.zalando.com.tr, zalando.at, zalando.be, zalando.bg
Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect zalando.com:443 -servername zalando.com 2>/dev/null | openssl x509 -noout -issuer -dates
Documentation: Certificate Transparency (https://certificate.transparency.dev/) · Let's Encrypt — Docs (https://letsencrypt.org/docs/) · Mozilla — Server Side TLS (https://wiki.mozilla.org/Security/Server_Side_TLS)

HSTS — enforce encryption in the browser

Failed · Severity: High · Hardening gap · 0/8

Browsers aren't told to always use an encrypted connection, enabling interception attacks on public networks.

No Strict-Transport-Security header. Users are exposed to SSL stripping on the first request.

Source data: Response headers from https://zalando.com/
Strict-Transport-Security: (missing)
$ curl -sIL https://zalando.com/ | grep -i "Strict-Transport-Security"
Fix recommendation (effort: Easy)
  1. Start with a short max-age (300 seconds) and make sure every subdomain works over HTTPS.
  2. Gradually raise it to 31536000 (one year) and add includeSubDomains.
  3. Consider preload only once the policy is stable — removal from the preload list is slow.
/*
  Strict-Transport-Security: max-age=31536000; includeSubDomains

Safety: This change is made in your server/CDN settings. Test on staging before production. HSTS is cached in the visitor's browser — a long max-age on a site without working HTTPS will block access.

Documentation: MDN — Strict-Transport-Security (https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Strict-Transport-Security) · RFC 6797 — HSTS (https://www.rfc-editor.org/rfc/rfc6797) · OWASP — HTTP Headers Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Headers_Cheat_Sheet.html)

CSP — protection from script injection

Failed · Severity: Medium · Hardening gap · 0/8

Missing Content-Security-Policy header: this removes one layer of protection against script injection.

No Content-Security-Policy header found.

Source data: Response headers from https://zalando.com/
Content-Security-Policy: (missing)
$ curl -sIL https://zalando.com/ | grep -i "Content-Security-Policy"
Fix recommendation (effort: Complex)
  1. First publish Content-Security-Policy-Report-Only — it blocks nothing, it only reports.
  2. Collect violations for a week or two and tune the policy to your legitimate sources.
  3. Switch to the Content-Security-Policy header and replace 'unsafe-inline' with a nonce or hash.
/*
  Content-Security-Policy-Report-Only: default-src 'self'; script-src 'self'; object-src 'none'; base-uri 'self'; frame-ancestors 'self'

Safety: This change is made in your server/CDN settings. Test on staging before production. An overly strict CSP will break scripts — that's why you start in Report-Only mode.

Documentation: MDN — Content Security Policy (https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CSP) · OWASP — CSP Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/Content_Security_Policy_Cheat_Sheet.html)

Clickjacking protection

Failed · Severity: Medium · Hardening gap · 0/5

Missing X-Frame-Options / frame-ancestors: this removes one layer of protection against clickjacking.

No valid X-Frame-Options and no frame-ancestors in the CSP.

Source data: Response headers from https://zalando.com/
X-Frame-Options: (missing)
$ curl -sIL https://zalando.com/ | grep -i "X-Frame-Options"
Fix recommendation (effort: Easy)
  1. Add X-Frame-Options: SAMEORIGIN (or DENY if the site is never embedded anywhere).
  2. Also set frame-ancestors in the CSP — the modern alternative.
/*
  X-Frame-Options: SAMEORIGIN

Safety: This change is made in your server/CDN settings. Test on staging before production. If partners embed the site in an iframe, add them to frame-ancestors instead of using DENY.

Documentation: MDN — X-Frame-Options (https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/X-Frame-Options) · OWASP — Clickjacking Defense (https://cheatsheetseries.owasp.org/cheatsheets/Clickjacking_Defense_Cheat_Sheet.html)

X-Content-Type-Options

Failed · Severity: Low · Hardening gap · 0/4

The browser may interpret files as code unintentionally.

Missing X-Content-Type-Options: nosniff header (MIME sniffing).

Source data: Response headers from https://zalando.com/
X-Content-Type-Options: (missing)
$ curl -sIL https://zalando.com/ | grep -i "X-Content-Type-Options"
Fix recommendation (effort: Easy)
  1. Add X-Content-Type-Options: nosniff to every response.
/*
  X-Content-Type-Options: nosniff

Safety: This change is made in your server/CDN settings. Test on staging before production.

Documentation: MDN — X-Content-Type-Options (https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/X-Content-Type-Options) · OWASP — HTTP Headers Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Headers_Cheat_Sheet.html)

Referrer-Policy

Failed · Severity: Low · Hardening gap · 0/3

Internal URLs (including parameters) may leak to external sites.

Referrer-Policy is missing; the browser will use its default.

Source data: Response headers from https://zalando.com/
Referrer-Policy: (missing)
$ curl -sIL https://zalando.com/ | grep -i "Referrer-Policy"
Fix recommendation (effort: Easy)
  1. Set Referrer-Policy: strict-origin-when-cross-origin.
/*
  Referrer-Policy: strict-origin-when-cross-origin

Safety: This change is made in your server/CDN settings. Test on staging before production.

Documentation: MDN — Referrer-Policy (https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Referrer-Policy) · OWASP — HTTP Headers Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Headers_Cheat_Sheet.html)

Permissions-Policy

Needs attention · Severity: Low · Hardening gap · 0/2

Access to sensitive features like the camera and location isn't restricted.

Missing Permissions-Policy header.

Source data: Response headers from https://zalando.com/
Permissions-Policy: (missing)
$ curl -sIL https://zalando.com/ | grep -i "Permissions-Policy"
Fix recommendation (effort: Easy)
  1. Disable browser features the site doesn't need (camera, microphone, geolocation).
/*
  Permissions-Policy: camera=(), microphone=(), geolocation=()

Safety: This change is made in your server/CDN settings. Test on staging before production. Don't disable a feature the site actually uses.

Documentation: MDN — Permissions-Policy (https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Permissions-Policy) · OWASP — HTTP Headers Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Headers_Cheat_Sheet.html)

Software version disclosure

Passed · Severity: OK · unscored

The server doesn't disclose software versions.

No version numbers found in the Server / X-Powered-By headers.

Source data: Response headers from https://zalando.com/
server: cloudflare
x-powered-by: (missing)
$ curl -sIL https://zalando.com/ | grep -iE "^(server|x-powered-by)"
Documentation: OWASP — HTTP Headers Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Headers_Cheat_Sheet.html)

DNSSEC — signed DNS records

Needs attention · Severity: Medium · Hardening gap · 0/7

The domain's records aren't signed, so in some scenarios users could be redirected to a forged server.

No DS record is published at the parent zone, so there's no DNSSEC chain of trust for this zone.

Source data: DNS-over-HTTPS (Cloudflare / Google): AD flag and DS record at the parent
AD = false
DS zalando.com: NODATA
$ dig +short DS zalando.com
Fix recommendation (effort: Medium)
  1. Enable DNSSEC at your DNS provider (one click at most providers).
  2. Copy the DS record your provider generates to your domain registrar.
  3. Wait for propagation and verify with DNSViz.
dig +dnssec zalando.com SOA
delv zalando.com

Safety: DNS changes are made only at your DNS provider. This tool only reads public data and changes nothing on the domain. A wrong DS record at the registrar will make the domain stop resolving — copy it exactly from the provider.

Documentation: RFC 4033 — DNSSEC (https://www.rfc-editor.org/rfc/rfc4033) · ICANN — DNSSEC: what and why (https://www.icann.org/resources/pages/dnssec-what-is-it-why-important-2019-03-05-en)

CAA — who may issue certificates

Needs attention · Severity: Low · Hardening gap · 0/5

Any certificate authority can issue a certificate for the domain, raising the risk of mis-issuance.

No CAA records found. RFC 8659 lets the domain owner restrict which CAs are authorized.

Source data: DNS CAA zalando.com
(no CAA records found)
$ dig +short CAA zalando.com
Fix recommendation (effort: Easy)
  1. Identify which certificate authority issued your current certificate (see the certificate check).
  2. Publish CAA for that authority only, and add iodef to receive alerts.
zalando.com.  CAA  0 issue "letsencrypt.org"
zalando.com.  CAA  0 iodef "mailto:security@zalando.com"

Safety: DNS changes are made only at your DNS provider. This tool only reads public data and changes nothing on the domain. If your CDN issues certificates on your behalf, include it too — otherwise certificate renewal will fail.

Documentation: RFC 8659 — CAA (https://www.rfc-editor.org/rfc/rfc8659)

DNS server redundancy

Passed · Severity: OK · 3/3

The domain is served by several DNS servers, so one server failing won't take it down.

4 NS servers.

Source data: DNS NS zalando.com
ns-1337.awsdns-39.org
ns-1818.awsdns-35.co.uk
ns-456.awsdns-57.com
ns-578.awsdns-08.net
$ dig +short NS zalando.com
Documentation: RFC 2182 — Secondary DNS server operation (https://www.rfc-editor.org/rfc/rfc2182)

Indicative alignment

Best-practice mapping of public findings to common frameworks. Passive scanning tests public configuration only; it doesn't prove compliance or a violation.

  • Google & Yahoo sender rulesNo gaps observed
  • PCI DSS v4.03 observed gaps
  • NIS2 / vendor due diligence3 observed gaps
  • SOC 2 / ISO 27001 baseline4 observed gaps

Indicative alignment only, based on public configuration. It doesn't establish whether a framework applies to you, and it isn't legal advice, an audit or a certification.

Public DNS records

Azalando.com3.170.51.107 | 3.170.51.38 | 3.170.51.42 | 3.170.51.88
AAAAzalando.com2600:9000:2873:b200:14:68:5500:93a1 | 2600:9000:2873:c600:14:68:5500:93a1 | 2600:9000:2873:f800:14:68:5500:93a1 | 2600:9000:2873:800:14:68:5500:93a1 | 2600:9000:2873:a600:14:68:5500:93a1 | 2600:9000:2873:c800:14:68:5500:93a1 | 2600:9000:2873:2e00:14:68:5500:93a1 | 2600:9000:2873:5400:14:68:5500:93a1
MXzalando.com1 smtp.google.com
NSzalando.comns-1337.awsdns-39.org | ns-1818.awsdns-35.co.uk | ns-456.awsdns-57.com | ns-578.awsdns-08.net
TXTzalando.comMS=ms31863815 | apple-domain-verification=TkIaXP7tOVNFj7Ma | facebook-domain-verification=91v041mbqqze167es1w24ja4qj96h5 | figma-domain-verification=600059c02c8f9330d8215ff97cbea3e6c079adefa6bff91eae765be9649160ac-1730372047 | github-verification=bDQKg8MbDvYwZms6btrWxxFmqzfVHXcXxsTCJLkh | google-site-verification=BER9CXK3xkVm2RqIvjSNn7Uqnl29B0xVywNcMd4xwrg | google-site-verification=mh9kmi3G6mUKcGuf-pLJjzFbh4bb9_gC5lunPWW8-bs | miro-verification=90efd7829ae5a1098db6b0691a9e4cb1280746a7 | openai-domain-verification=dv-4sVY6t1iE79IPToTxeVLHU6o | v=spf1 ip4:63.185.125.73 include:_spf.google.com ip4:80.237.155.68 ip4:195.71.68.47 ip4:149.96.14.2 ip4:185.85.220.205 include:_spf.salesforce.com -all | zscaler-verification-44864592-2012026-K3wNnYLpSy
TXT_dmarc.zalando.comv=DMARC1; p=reject; fo=1; rua=mailto:dmarc_rua@zalando.com; ruf=mailto:dmarc_ruf@zalando.com; adkim=s; pct=100;
CAAzalando.com—
DSzalando.com—
Passive check only: reading public DNS records, Certificate Transparency logs and ordinary GET requests to the homepage over HTTPS and HTTP. No changes were made to the scanned domain. Results are an indication and do not replace a professional security assessment.

Check your own domain