Digital exposure report
abnamro.com
Low exposure. The domain is well protected in most areas checked.
Scanned: 2026-11-19 05:57 UTC
Full coverage: every applicable check was assessed.
What to do first
- 1.
Limit what your site shares when visitors click links
This reduces how much page address detail is passed to other websites.
Who can fix it: Your website developer or web host
How to verify after the fix
curl -sIL https://abnamro.com/ | grep -i "Referrer-Policy"
- 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://abnamro.com/ | grep -i "Content-Security-Policy"
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- abnamro.com
- Website request
- GET https://abnamro.com/ → https://www.abnamro.com/nl/home
- Scan time
- 2026-11-19 05:57:58 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 | 21/30 | Some browser protections are missing. |
| DNS infrastructure | 15/15 | The domain's infrastructure is well hardened. |
Fix priorities
- 1.LowReferrer-Policy · Hardening gap+3
- 2.LowPermissions-Policy · Hardening gap+2
- 3.LowCSP — protection from script injection · Hardening gap+3
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. 2 of the 10 allowed DNS lookups.
v=spf1 include:spf.protection.outlook.com include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email -all$ dig +short TXT abnamro.com
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:dmarc_agg@vali.email; ruf=mailto:dmarc2@nl.abnamro.com; fo=1
$ dig +short TXT _dmarc.abnamro.com
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, s2. Confirm signing with dkim=pass in a sent message's Authentication-Results.
selector1._domainkey: v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAuycE8ToVoP8gl4N0kxBMHBjAICpX… selector2._domainkey: v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA2GOrXVn7GndZdjxO3FM8HUzDL7G4… s2._domainkey: k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAtUsNISu83sOXnWA9CLpTqrgbeDI7kKjA…
$ dig +short TXT selector1._domainkey.abnamro.com
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.
10 abnamro-com.k-v1.mx.microsoft
$ dig +short MX abnamro.com
HTTPS available
Passed · Severity: OK · 10/10The site loads over an encrypted connection.
https://abnamro.com/ returned HTTP 200 (final URL: https://www.abnamro.com/nl/home). Client-side certificate validation passed.
HTTP 200 Final URL: https://www.abnamro.com/nl/home
$ curl -sIL https://abnamro.com/
HTTP → HTTPS redirect
Passed · Severity: OK · 7/7Visitors arriving at an unencrypted address are automatically sent to the secure version.
HTTP 301 → https://abnamro.com/
HTTP 301 Location: https://abnamro.com/
$ curl -sI http://abnamro.com/ | 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-05-23 (185 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: 2026-11-06 Valid until: 2027-05-23 Names: abnamro.com, aditium.nl, www.abnamro.com, www.aditium.nl Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect abnamro.com:443 -servername abnamro.com 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://abnamro.com/ | grep -i "Strict-Transport-Security"
CSP — protection from script injection
Needs attention · Severity: Low · Hardening gap · 5/8A script policy exists, but it's permissive and offers only partial protection.
script-src includes: 'unsafe-inline', 'unsafe-eval', a broad source (* / https: / data:) — weakens XSS protection.
Content-Security-Policy: default-src *.abnamro.nl data: 'unsafe-inline' 'unsafe-eval' https:; script-src 'unsafe-inline' 'unsafe-eval' https: *.tealiumiq.com *.abnamro.nl *.qualtrics.com *.facebook.net *.dwin1.com *.licdn.com api.eu.kaltura.com beursinfo.abnamro.nl *.tiqcdn.com w.usabilla.com api.usabilla.com google-analytics.com *.googletagmanager.com nieuwsbrieven.abnamro.nl *.optimizely.com *.kameleoon.com *.kameleoon.eu *.kameleoon.io channel.royalcast.com; connect-src https: *.tealiumiq.com api.usabilla.com *.omtrdc.net dpm.demdex.net *.linkedin.com *.qualtrics.com *.google-analytics.com *.g.doubleclick.net *.doubleclick.net region1.google-analytics.com *.analytics.google.com nieuwsbrieven.abnamro.nl *.optimizely.com *.kameleoon.com *.kameleoon.eu *.kameleoon.io *.googletagmanager.com *.google.com *.google.nl channel.royalcast.com; style-src 'unsafe-inline' https: blob: fonts.googleapis.com; img-src data: https: abnamro.sc.omtrdc.net cfvod.eu.kaltura.com *.googletagmanager.com d6tizftlrpuof.cloudfront.net images.ctfassets.net *.google-analytics.com *.analytics.google.co *.google.com *.google.nl *.tealiumiq.com w.usabilla.com abnamro.sc.omtrdc.net *.qualtrics.com *.facebook.com *.awin1.com *.g.doubleclick.net *.doubleclick.net px.ads.linkedin.com region1.google-analytics.com channel.royalcast.com; font-src https: fonts.gstatic.com; media-src 'self' https: blob:; frame-src https://feedback.abnamro.com *.feedback.abnamro.com https://abnamro.slgnt.eu *.qualtrics.com abnamrobank.qualtrics.com beursinfo.abnamro.nl d6tizftlrpuof.cloudfront.net *.doubleclick.net *.awin1.com localfocuswidgets.net assets.abnamro.com www.youtube.com https://www.youtube-nocookie.com www.google.com nieuwsbrieven.abnamro.nl *.optimizely.com *.kameleoon.com *.kameleoon.eu *.kameleoon.io channel.royalcast.com omny.fm https://*.spotify.com https://mee.mail.abnamro.com https://sdk.companywebcast.com; worker-src 'self' https: blob:; frame-ancestors https: beursinfo.abnamro.nl nieuwsbrieven.abnamro.nl *.optimizely.com *.kameleoon.com *.kameleoon.eu *.kameleoon.io channel.royalcast.com sdk.companywebcast.com
$ curl -sIL https://abnamro.com/ | 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 frame-ancestors https: beursinfo.abnamro.nl nieuwsbrieven.abnamro.nl *.optimizely.com *.kameleoon.com *.kameleoon.eu *.kameleoon.io channel.royalcast.com sdk.companywebcast.com
X-Frame-Options: DENY CSP frame-ancestors: https: beursinfo.abnamro.nl nieuwsbrieven.abnamro.nl *.optimizely.com *.kameleoon.com *.kameleoon.eu *.kameleoon.io channel.royalcast.com sdk.companywebcast.com
$ curl -sIL https://abnamro.com/ | 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://abnamro.com/ | 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://abnamro.com/ | 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://abnamro.com/ | 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://abnamro.com/ | grep -iE "^(server|x-powered-by)"
DNSSEC — signed DNS records
Passed · Severity: OK · 7/7The domain's records are digitally signed and hard to forge.
An AD (Authenticated Data) flag was returned by a validating resolver.
AD = true
$ dig +dnssec abnamro.com | grep -E "flags:.* ad"
CAA — who may issue certificates
Passed · Severity: OK · 5/5Only authorized certificate authorities can issue certificates for the domain.
CAA records: 0 iodef "mailto:domainmanagement@nl.abnamro.com" | 0 issue "amazon.com" | 0 issue "amazonaws.com" | 0 issue "amazontrust.com" | 0 issue "awstrust.com" | 0 issue "entrust.net" | 0 issue "kpn.com" | 0 issue "quovadisglobal.com" | 0 issue "sectigo.com" | 0 issuewild ";" | 0 contactemail "domainmanagement@nl.abnamro.com"
0 iodef "mailto:domainmanagement@nl.abnamro.com" 0 issue "amazon.com" 0 issue "amazonaws.com" 0 issue "amazontrust.com" 0 issue "awstrust.com" 0 issue "entrust.net" 0 issue "kpn.com" 0 issue "quovadisglobal.com" 0 issue "sectigo.com" 0 issuewild ";" 0 contactemail "domainmanagement@nl.abnamro.com"
$ dig +short CAA abnamro.com
DNS server redundancy
Passed · Severity: OK · 3/3The domain is served by several DNS servers, so one server failing won't take it down.
6 NS servers.
a1-47.akam.net a4-64.akam.net a7-65.akam.net a9-66.akam.net a16-66.akam.net a20-67.akam.net
$ dig +short NS abnamro.com
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 diligenceNo gaps observed
- SOC 2 / ISO 27001 baseline1 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 | abnamro.com | 23.205.89.134 | 23.205.89.161 |
| AAAA | abnamro.com | 2600:1408:ec00:10::1730:cb0b | 2600:1408:ec00:10::1730:cb13 |
| MX | abnamro.com | 10 abnamro-com.k-v1.mx.microsoft |
| NS | abnamro.com | a1-47.akam.net | a4-64.akam.net | a7-65.akam.net | a9-66.akam.net | a16-66.akam.net | a20-67.akam.net |
| TXT | abnamro.com | MS=ms20241111 | MS=ms84846211 | docusign=fc7327fa-38b6-4991-907f-cbaebbee00a2 | 1de1f07f-ae4a-4d87-90ec-f743e30783d8 | apple-domain-verification=vITayiAaYoZUIUdF | 877f95f4-ef95-4938-a4df-0689263afd38-05072018 | docusign=1fa6964a-9856-4bed-8adf-f62818cdc12b | docusign=d8a9cd8f-6254-4c1c-a950-8d3bf04ba96d | fastly-domain-delegation-cnjr8398vhwc-25012023 | onetrust-domain-verification=8cad52366959485fb71d7c28183382f9 | dtm-domain-verification=eIHSc4Ss3YUagYjxCLITkagHdAcKN3Pzql9XLyEvAN8 | dtm-domain-verification=u0IowLtDGPGNRCiZJa7KGIQx09hYf2TV8oufDXB9QAI | google-site-verification=1S_Aalr_ym2W9WZK5u9JKZ9_5-zWaSWksZVlV5xjJ-E | google-site-verification=wniEoAQ9OuOuQpbCld-j0Ob3sc6njKgOyRO54QJdupQ | google-site-verification=zG2tRyCQ8X91u8PevocGUTIgjjFnOlcTs6bC274f9FM | h1-domain-verification=KtXVrbKjwGKvXqJsf6XzMwo4581YoxiE6tncKTvpFBSMYZnF | 6yYNgh6NJTiLW8Gv9JT9xXOcEQC+frfYm+wj+lSbtcZxjCs82FMY6j26mIeAI5IG4R9GAk44mZhaRI2dg1/44Q== | atlassian-domain-verification=d8UqBYnxsRaWayiB5nsnx/saLNyaRca/olaB2I3HhY18h4WjwnYShTJWkOitbUdf | v=spf1 include:spf.protection.outlook.com include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email -all | postman-domain-verification=914e46d134a29d22dfe12b939172400e4bd4b98ada8d99be8d0d08ef161757531fd167cd0ad75548c4c12727b3f49c766c7b611988e9932622dfe01cf2829d93 |
| TXT | _dmarc.abnamro.com | v=DMARC1; p=reject; rua=mailto:dmarc_agg@vali.email; ruf=mailto:dmarc2@nl.abnamro.com; fo=1 |
| CAA | abnamro.com | 0 iodef "mailto:domainmanagement@nl.abnamro.com" | 0 issue "amazon.com" | 0 issue "amazonaws.com" | 0 issue "amazontrust.com" | 0 issue "awstrust.com" | 0 issue "entrust.net" | 0 issue "kpn.com" | 0 issue "quovadisglobal.com" | 0 issue "sectigo.com" | 0 issuewild ";" | 0 contactemail "domainmanagement@nl.abnamro.com" |
| DS | abnamro.com | 31272 13 2 770c99d8e6489dc0635a346f05ea9fc4e560b11d5980d8559083db41a44196d5 |