Digital exposure report
dzbank.de
High exposure. Significant weaknesses put the brand, customers and email at risk.
Scanned: 2026-11-19 04:57 UTC
Full coverage: every applicable check was assessed.
What to do first
- 1.
Tell receiving mail servers how to treat fake email from your domain
Without this policy, inboxes have less guidance for spotting messages that impersonate you.
Who can fix it: Your email provider, together with whoever manages your DNS
How to verify after the fix
dig +short TXT _dmarc.dzbank.de
- 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://dzbank.de/ | grep -i "Content-Security-Policy"
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- dzbank.de
- Website request
- GET https://dzbank.de/ → https://www.dzbank.de/content/dzbank/de/home.html
- Scan time
- 2026-11-19 04:57:59 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 security | 20/30 | Spoofing email in the company's name is possible in some cases. |
| Encryption & certificate | 25/25 | Traffic to the site is encrypted and the certificate is valid. |
| Browser protections | 16/30 | Some browser protections are missing. |
| DNS infrastructure | 8/15 | The domain's infrastructure works, but recommended hardening is missing. |
Fix priorities
- 1.MediumDMARC — anti-spoofing policy · Hardening gap+10
- 2.MediumDNSSEC — signed DNS records · Hardening gap+7
- 3.MediumCSP — protection from script injection · Hardening gap+8
- 4.LowReferrer-Policy · Hardening gap+3
- 5.LowPermissions-Policy · Hardening gap+2
Findings
SPF — who may send mail for the domain
Passed · Severity: OK · 10/10An authorized sender list is defined and mail from other servers is rejected.
Valid SPF record with -all. 10 of the 10 allowed DNS lookups.
v=spf1 mx include:_spf.retarus.com include:spf.sendinblue.com include:spf1.dzbank.de include:spf2.dzbank.de include:spf3.dzbank.de include:spf4.dzbank.de include:spf5.atruvia.dzbank.de include:_spf.general.transactional-mail-a.com include:spf.protection.outlook.com -all
$ dig +short TXT dzbank.de
DMARC — anti-spoofing policy
Needs attention · Severity: Medium · Hardening gap · 5/15DMARC is in monitoring mode only — forged email still reaches recipients.
Policy p=none. p=none collects reports but does not protect.
v=DMARC1; p=none; aspf=s; rua=mailto:dmarc.report@dzbank.de; ruf=mailto:dmarc.forensic@dzbank.de; fo=d:s;
$ dig +short TXT _dmarc.dzbank.de
- Step 1 (monitoring, no effect on mail): publish p=none with an rua address to receive reports.
- Step 2: analyze reports for 2–4 weeks and make sure every legitimate sender passes SPF/DKIM.
- Step 3: move to p=quarantine, and finally to p=reject.
_dmarc.dzbank.de. TXT "v=DMARC1; p=none; rua=mailto:dmarc@dzbank.de; fo=1"
Safety: DNS changes are made only at your DNS provider. This tool only reads public data and changes nothing on the domain. Jumping straight to reject without a monitoring phase can block legitimate mail.
DKIM — digital signature on email
Passed · Severity: OK · 5/5A 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: selector1, selector2, mail. Confirm signing with dkim=pass in a sent message's Authentication-Results.
selector1._domainkey: v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCrPMITN2/ZigB6Kem8wLj8/PS/Mv0Rx9k0… selector2._domainkey: v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC4jbCgGHwhPLyVPDcaXCheCg2U0rNWUTMp… mail._domainkey: k=rsa;p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDeMVIzrCa3T14JsNY0IRv5/2V1/v2itlviLQBwXsa7sh…
$ dig +short TXT selector1._domainkey.dzbank.de
MX — inbound mail routing
Passed · Severity: OK · unscoredMail exchangers are published for the domain.
4 MX record(s). This shows where inbound mail is routed, not whether mail is sent from the domain.
10 mg1.dzbank.de 10 mg2.dzbank.de 10 mg3.dzbank.de 10 mg4.dzbank.de
$ dig +short MX dzbank.de
HTTPS available
Passed · Severity: OK · 10/10The site loads over an encrypted connection.
https://dzbank.de/ returned HTTP 200 (final URL: https://www.dzbank.de/content/dzbank/de/home.html). Client-side certificate validation passed.
HTTP 200 Final URL: https://www.dzbank.de/content/dzbank/de/home.html
$ curl -sIL https://dzbank.de/
HTTP → HTTPS redirect
Passed · Severity: OK · 7/7Visitors arriving at an unencrypted address are automatically sent to the secure version.
HTTP 301 → https://www.dzbank.de:443/
HTTP 301 Location: https://www.dzbank.de:443/
$ curl -sI http://dzbank.de/ | grep -iE "^(HTTP|location)"
SSL/TLS certificate validity
Passed · Severity: OK · 8/8The certificate was accepted by a validating TLS client at scan time.
Live TLS handshake succeeded. Latest issuance in CT logs: DigiCert, expiring 2027-01-28 (70 days). CT shows issued certificates, not necessarily the one served — confirm dates with the verify command.
Live TLS handshake: certificate accepted CT logs (context only, not scored): Issuer: DigiCert Valid from: 2026-01-29 Valid until: 2027-01-28 Names: autodiscover.dzbank.de, dzbank.de, mail.dzbank.de Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect dzbank.de:443 -servername dzbank.de 2>/dev/null | openssl x509 -noout -issuer -dates
HSTS — enforce encryption in the browser
Passed · Severity: OK · 7/8Browsers are told to always use an encrypted connection to the site.
max-age=31536000 (365 days), no includeSubDomains. ≥ 180 days recommended.
Strict-Transport-Security: max-age=31536000
$ curl -sIL https://dzbank.de/ | grep -i "Strict-Transport-Security"
CSP — protection from script injection
Failed · Severity: Medium · Hardening gap · 0/8Missing Content-Security-Policy header: this removes one layer of protection against script injection.
No Content-Security-Policy header found.
Content-Security-Policy: (missing)
$ curl -sIL https://dzbank.de/ | grep -i "Content-Security-Policy"
- First publish Content-Security-Policy-Report-Only — it blocks nothing, it only reports.
- Collect violations for a week or two and tune the policy to your legitimate sources.
- 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.
Clickjacking protection
Passed · Severity: OK · 5/5The site can't be embedded by foreign sites.
X-Frame-Options: SAMEORIGIN
X-Frame-Options: SAMEORIGIN
$ curl -sIL https://dzbank.de/ | grep -i "X-Frame-Options"
X-Content-Type-Options
Passed · Severity: OK · 4/4The browser won't guess file types in a way that could execute code.
nosniff is set.
X-Content-Type-Options: nosniff
$ curl -sIL https://dzbank.de/ | grep -i "X-Content-Type-Options"
Referrer-Policy
Failed · Severity: Low · Hardening gap · 0/3Internal URLs (including parameters) may leak to external sites.
Referrer-Policy is missing; the browser will use its default.
Referrer-Policy: (missing)
$ curl -sIL https://dzbank.de/ | grep -i "Referrer-Policy"
- 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.
Permissions-Policy
Needs attention · Severity: Low · Hardening gap · 0/2Access to sensitive features like the camera and location isn't restricted.
Missing Permissions-Policy header.
Permissions-Policy: (missing)
$ curl -sIL https://dzbank.de/ | grep -i "Permissions-Policy"
- 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.
Software version disclosure
Passed · Severity: OK · unscoredThe server doesn't disclose software versions.
No version numbers found in the Server / X-Powered-By headers.
server: cloudflare x-powered-by: (missing)
$ curl -sIL https://dzbank.de/ | grep -iE "^(server|x-powered-by)"
DNSSEC — signed DNS records
Needs attention · Severity: Medium · Hardening gap · 0/7The 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.
AD = false DS dzbank.de: NODATA
$ dig +short DS dzbank.de
- Enable DNSSEC at your DNS provider (one click at most providers).
- Copy the DS record your provider generates to your domain registrar.
- Wait for propagation and verify with DNSViz.
dig +dnssec dzbank.de SOA delv dzbank.de
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.
CAA — who may issue certificates
Passed · Severity: OK · 5/5Only authorized certificate authorities can issue certificates for the domain.
CAA records: 0 issue "telesec.de" | 0 issue "d-trust.net" | 0 issue "digicert.com" | 0 issuemail "digicert.com" | 0 issue "letsencrypt.org" | 0 issue "quovadisglobal.com" | 0 issue "pki.goog" | 0 issue "mailto:pki-info@dzbank.de" | 0 issuewild ";"
0 issue "telesec.de" 0 issue "d-trust.net" 0 issue "digicert.com" 0 issuemail "digicert.com" 0 issue "letsencrypt.org" 0 issue "quovadisglobal.com" 0 issue "pki.goog" 0 issue "mailto:pki-info@dzbank.de" 0 issuewild ";"
$ dig +short CAA dzbank.de
DNS server redundancy
Passed · Severity: OK · 3/3The domain is served by several DNS servers, so one server failing won't take it down.
2 NS servers.
ns1.dzbank.de ns2.dzbank.de
$ dig +short NS dzbank.de
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 rules1 observed gaps
- PCI DSS v4.01 observed gaps
- NIS2 / vendor due diligence2 observed gaps
- SOC 2 / ISO 27001 baseline2 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
| A | dzbank.de | 34.120.10.200 |
| AAAA | dzbank.de | — |
| MX | dzbank.de | 10 mg1.dzbank.de | 10 mg2.dzbank.de | 10 mg3.dzbank.de | 10 mg4.dzbank.de |
| NS | dzbank.de | ns1.dzbank.de | ns2.dzbank.de |
| TXT | dzbank.de | _telesec-domain-validation=4D62915E945CB6202B93BC5B63A5D79AFAD535321AACCAC6DF82B4CE3E19F6E1 | 9LlfWCyZdXzm2m1UYtCJKOBAPNpZ+cQ7x85gWJKAYmUvWZICUMgHBt7OxgxQkYiycgSTI8/Mpr6gBNG8AF1TNA== | amazonses:/hQbhqfeLlP/T92pGkcmMsGhkr2Kf4IzubUSP0gg2cU= | teamviewer-sso-verification=1dc1d101dcac44c1bc60f1edf7c0fc44 | D-TRUST=3CZIOZ6GN6OVY29KET7CS9G | swisssign-check=xhBXiHK7Rq6iXpZX2sEE8lQ4oJGltbwVk4JMObskcd | MS=ms49264968 | successfactors-site-verification=ZTk0ZjVkZWRhNWM4ZmJiZDI3Y2RiODg0NmMyMWViZWExYjNkZGE5ZjUwNTM1ODU4ZGQzZDEwYjk4M2Q4OTRiMw== | mYdDvRqXwKXqR8yqlqPcxG5i5S0h0oujdYGtpM8u2dw47lQWMgm2/6KUVpmi8AJRW4hT7CClzIfIi4DsqvwVXQ== | QuoVadis=183e936b-3411-47d0-b1f4-929056fc7b43 | google-site-verification=fcFcZ6cCCe0jSbasRmNiSyv_03da28VOo0eZ9lwc-W4 | _m1y17nx9yn8144nnt2ib12xjj8m3z89 | successfactors-site-verification=NjllNjFiMzhjNTc2NTg3OTVmZTI5NzcwYWE4NDNiMDcyMzg2ODcwZWEwMjliZDNlOTFlOTQyMTU5NzNjNDYzMg== | canva-site-verification=Zq2qa9sVslq7Ze-LBlw2iQ | Sendinblue-code:6ef1bdca0140128a0b0cdffd769c529f | v=spf1 mx include:_spf.retarus.com include:spf.sendinblue.com include:spf1.dzbank.de include:spf2.dzbank.de include:spf3.dzbank.de include:spf4.dzbank.de include:spf5.atruvia.dzbank.de include:_spf.general.transactional-mail-a.com include:spf.protection.outlook.com -all |
| TXT | _dmarc.dzbank.de | v=DMARC1; p=none; aspf=s; rua=mailto:dmarc.report@dzbank.de; ruf=mailto:dmarc.forensic@dzbank.de; fo=d:s; |
| CAA | dzbank.de | 0 issue "telesec.de" | 0 issue "d-trust.net" | 0 issue "digicert.com" | 0 issuemail "digicert.com" | 0 issue "letsencrypt.org" | 0 issue "quovadisglobal.com" | 0 issue "pki.goog" | 0 issue "mailto:pki-info@dzbank.de" | 0 issuewild ";" |
| DS | dzbank.de | — |