Digital exposure report
raiffeisen.at
Moderate exposure. There are gaps an attacker could exploit — fix them soon.
Scanned: 2026-11-19 02:56 UTC
Full coverage: every applicable check was assessed.
What to do first
- 1.
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://raiffeisen.at/ | grep -i "Content-Security-Policy"
- 2.
Turn on DNS signing for your domain
Signing helps resolvers detect forged answers about your domain.
Who can fix it: Your domain registrar or DNS provider
How to verify after the fix
dig +short DS raiffeisen.at
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- raiffeisen.at
- Website request
- GET https://raiffeisen.at/ → https://www.raiffeisen.at/de/privatkunden.html
- Scan time
- 2026-11-19 02:56:07 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 | 30/30 | Spoofing email from this domain is hard. |
| Encryption & certificate | 25/25 | Traffic to the site is encrypted and the certificate is valid. |
| Browser protections | 13/30 | Several browser hardening headers are missing, which removes layers of protection against script injection and framing. |
| DNS infrastructure | 8/15 | The domain's infrastructure works, but recommended hardening is missing. |
Fix priorities
- 1.MediumDNSSEC — signed DNS records · Hardening gap+7
- 2.MediumCSP — protection from script injection · Hardening gap+8
- 3.LowX-Content-Type-Options · Hardening gap+4
- 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. 1 of the 10 allowed DNS lookups.
v=spf1 include:spf.raiffeisen.at.eu-7yizepaq.e1.dspf.app -all
$ dig +short TXT raiffeisen.at
DMARC — anti-spoofing policy
Passed · Severity: OK · 15/15Forged email in the company's name is blocked by mail servers.
Policy p=reject.
v=DMARC1; p=reject; rua=mailto:7yizepaq@ag.eu.dmarcadvisor.com; ruf=mailto:7yizepaq@fr.eu.dmarcadvisor.com
$ dig +short TXT _dmarc.raiffeisen.at
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. Confirm signing with dkim=pass in a sent message's Authentication-Results.
selector1._domainkey: v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAyI6/sTJEd6C/xuBwUU8hSF2XEq5/… selector2._domainkey: v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAxm0j0Ud5NciBdQS0VY6NtLQp0uwe…
$ dig +short TXT selector1._domainkey.raiffeisen.at
MX — inbound mail routing
Passed · Severity: OK · unscoredMail 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.
0 raiffeisen-at.mail.protection.outlook.com
$ dig +short MX raiffeisen.at
HTTPS available
Passed · Severity: OK · 10/10The site loads over an encrypted connection.
https://raiffeisen.at/ returned HTTP 200 (final URL: https://www.raiffeisen.at/de/privatkunden.html). Client-side certificate validation passed.
HTTP 200 Final URL: https://www.raiffeisen.at/de/privatkunden.html
$ curl -sIL https://raiffeisen.at/
HTTP → HTTPS redirect
Passed · Severity: OK · 7/7Visitors arriving at an unencrypted address are automatically sent to the secure version.
HTTP 301 → https://raiffeisen.at/
HTTP 301 Location: https://raiffeisen.at/
$ curl -sI http://raiffeisen.at/ | 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: Sectigo, expiring 2027-01-14 (56 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: Sectigo Valid from: 2025-12-15 Valid until: 2027-01-14 Names: *.raiffeisen.at, raiffeisen.at Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect raiffeisen.at:443 -servername raiffeisen.at 2>/dev/null | openssl x509 -noout -issuer -dates
HSTS — enforce encryption in the browser
Passed · Severity: OK · 8/8Browsers are told to always use an encrypted connection to the site.
max-age=63072000 (730 days), includeSubDomains. ≥ 180 days recommended.
Strict-Transport-Security: max-age=63072000; includeSubDomains
$ curl -sIL https://raiffeisen.at/ | 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://raiffeisen.at/ | 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: Deny
X-Frame-Options: Deny
$ curl -sIL https://raiffeisen.at/ | grep -i "X-Frame-Options"
X-Content-Type-Options
Failed · Severity: Low · Hardening gap · 0/4The browser may interpret files as code unintentionally.
Missing X-Content-Type-Options: nosniff header (MIME sniffing).
X-Content-Type-Options: (missing)
$ curl -sIL https://raiffeisen.at/ | grep -i "X-Content-Type-Options"
- 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.
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://raiffeisen.at/ | 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://raiffeisen.at/ | 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://raiffeisen.at/ | 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 raiffeisen.at: NODATA
$ dig +short DS raiffeisen.at
- 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 raiffeisen.at SOA delv raiffeisen.at
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 iodef "mailto:cert@r-it.at" | 0 issue "a-trust.at" | 0 issue "amazonaws.com" | 0 issue "comodoca.com" | 0 issue "digicert.com" | 0 issue "entrust.net" | 0 issue "letsencrypt.org" | 0 issue "quovadisglobal.com" | 0 issue "ssl.com" | 0 issue "thawte.com" | 0 issuewild "digicert.com" | 0 issuewild "entrust.net" | 0 issuewild "thawte.com"
0 iodef "mailto:cert@r-it.at" 0 issue "a-trust.at" 0 issue "amazonaws.com" 0 issue "comodoca.com" 0 issue "digicert.com" 0 issue "entrust.net" 0 issue "letsencrypt.org" 0 issue "quovadisglobal.com" 0 issue "ssl.com" 0 issue "thawte.com" 0 issuewild "digicert.com" 0 issuewild "entrust.net" 0 issuewild "thawte.com"
$ dig +short CAA raiffeisen.at
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.
ns0233.secondary.cloudflare.com ns0115.secondary.cloudflare.com
$ dig +short NS raiffeisen.at
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.01 observed gaps
- NIS2 / vendor due diligence1 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 | raiffeisen.at | 149.154.103.100 |
| AAAA | raiffeisen.at | — |
| MX | raiffeisen.at | 0 raiffeisen-at.mail.protection.outlook.com |
| NS | raiffeisen.at | ns0233.secondary.cloudflare.com | ns0115.secondary.cloudflare.com |
| TXT | raiffeisen.at | 7mcqpr98ng1w2zgrbnc9rtn7mzk9t8j1 | 864a6dfd-23a9-4ff1-bb6a-3e3c8731ed4e | MS=ms80382828 | _9z7vov27f18ygucrup931tjegknak4u | _a3vyq4fx6i30bly61yd9v5frlo2ucd3 | _e5wrptaisg5ytgf32pt3fnj1xzzw3e3 | _ty7llg0oi95pbm81ytbqxzak3svm4z1 | _w9bdpcj49ltzrd32jpe0cun0udhlzlo | b7snlfpj9t3363wlxlh7tpndd5vhxp31 | cloudControl-verification: 1797e942a572ed11007477e7f60aa7d6fc9222cdd4ee3937b7af7ba78431a0ed | facebook-domain-verification=jue6bxha8djmhfxdsvrqmj304ufqk3 | facebook-domain-verification=oj3qzllxljrwoxnzpxvsioxrl6c6l4 | google-site-verification=RAJkK15lSj8RvCdDLRILt1_QWDQ-isiUezzxipeIxB4 | google-site-verification=hFBGOYNDGQqP70049uG5aZSP7uZBqe-xZFCnoUHLkBg | k5dbqlyk84p6l4q7wgr10zb3q0ngcyt1 | kaujVhsOf6mD/5Z2/hUZHNB+klvTcL7JVpbyJMDQHFw9UX4+j6AAF/NcGEgro0aBCcS0LovziI1IxDshDrIspA== | swisssign-check=USB2ZJTnGtxzcwRBiouTSvSxDjw | v=spf1 include:spf.raiffeisen.at.eu-7yizepaq.e1.dspf.app -all | xvx26t2bjlk0f3583rdl14ljr5vlj73r | z5nff516t8sxxf2497hgftpf0l667rz9 |
| TXT | _dmarc.raiffeisen.at | v=DMARC1; p=reject; rua=mailto:7yizepaq@ag.eu.dmarcadvisor.com; ruf=mailto:7yizepaq@fr.eu.dmarcadvisor.com |
| CAA | raiffeisen.at | 0 iodef "mailto:cert@r-it.at" | 0 issue "a-trust.at" | 0 issue "amazonaws.com" | 0 issue "comodoca.com" | 0 issue "digicert.com" | 0 issue "entrust.net" | 0 issue "letsencrypt.org" | 0 issue "quovadisglobal.com" | 0 issue "ssl.com" | 0 issue "thawte.com" | 0 issuewild "digicert.com" | 0 issuewild "entrust.net" | 0 issuewild "thawte.com" |
| DS | raiffeisen.at | — |