Skip to main content

DNS & Email Security Report for rabobank.nl

An automated analysis of rabobank.nl's DNS configuration, email authentication (SPF, DKIM, DMARC), DNSSEC chain, IPv6 readiness, and transport security, based on a scan made on November 9, 2026.

A93/100
Very Good

Strong security posture

Overall security score: 93/100 · Grade A (Very Good) · 39 checks passed, 5 failed, 17 not assessed

Key findings for rabobank.nl

SPF
rabobank.nl publishes an SPF record that ends in -all, so receivers are told to reject mail from servers it does not list.v=spf1 include:spf-imr.rabobank.nl include:spf.protection.outlook.com include:spf.eu.mailmarshal.cloud include:spf.serverbeheer.faceworks.nl ip4:145.72.121.0/24 ip4:83.137.145.128/25 ip4:54.229.31.57 -all
DMARC
The DMARC policy tells receivers to reject mail that fails authentication, and aggregate reports are requested via rua.v=DMARC1; p=reject; rua=mailto:difuwh3e@ag.eu.dmarcadvisor.com
DKIM
A DKIM public key was found at the selector "selector1".
MTA-STS
MTA-STS is in enforce mode, so sending servers must use verified TLS to deliver mail.
DNSSEC
The zone is DNSSEC-signed and validates from the root down.
CAA
7 CAA records restrict which certificate authorities may issue certificates for rabobank.nl.
IPv6
1 of 1 mail server can be reached over IPv6.

How rabobank.nl compares

With 93/100, rabobank.nl scores higher than 129 of the 133 other domains in the IntoDNS.ai report set (median score 71/100, all scanned in the same run). Within its sector, Dutch banks and fintech, it ranks 2 of 7.

Similar domains

All domain security reports

This report is a stored snapshot

This page shows a snapshot from November 9, 2026. DNS changes frequently — for live records, propagation, and deep checks, run a fresh interactive scan of rabobank.nl at /scan.

Run a fresh live scan

Detailed check results

DNS

100%pass
  • A record presentcritical

    2 A record(s) found

  • AAAA record presentrecommended

    2 AAAA record(s) found

  • MX records presentrecommended

    1 MX record(s) found

  • NS records presentcritical

    6 NS record(s) found

  • SOA record presentcritical

    SOA record found

  • Multiple nameserversrecommended

    6 nameservers configured ✓

  • SOA serial formatinfo

    Serial 2020122776 (YYYYMMDDnn format)

  • SOA timers validinfo

    Refresh: 7200s ✓, Retry: 1200s ✓, Expire: 2419200s ✓

  • No lame nameserversinfo

    6 NS all responding ✓

  • Glue records presentinfo

    No glue needed

  • WWW record configuredinfo

    A record matches apex

  • MX servers have PTR recordsrecommended

    8 MX IPs all have PTR records ✓

  • MX servers have FCrDNSrecommended

    8 MX IPs have forward-confirmed reverse DNS ✓

DNSSEC

100%pass
  • DNSSEC signedrecommended

    DNSSEC is enabled ✓

  • DNSSEC validation OKcritical

    DNSSEC validates correctly ✓

  • NSEC3 RFC 9276 compliantrecommended

    NSEC3 iterations=0, salt=empty — RFC 9276 compliant ✓

  • RRSIG signatures validrecommended

    RRSIG signature expires in 2 days — renewal needed

  • Modern DNSSEC algorithmoptional

    ECDSA P-256 (algorithm 13) — modern ✓

  • DS digest algorithm modernrecommended

    DS digest: SHA-256 — modern ✓

  • DNSKEY algorithm secureoptional

    DNSKEY: ECDSA P-256 — modern ✓

  • RRSIG TTL saferecommended

    Record TTLs do not exceed RRSIG validity periods ✓

  • Chain of trust completecritical

    Cryptographic chain validated to the root trust anchor with local BIND delv ✓

IPv6

100%pass
  • Website reachable via IPv6recommended

    2 AAAA record(s) ✓

  • Mail servers publish IPv6recommended

    1/1 MX server(s) publish IPv6 ✓

  • Nameservers reachable via IPv6recommended

    6/6 NS server(s) with IPv6 ✓

Email security

100%pass
  • SPF record presentcritical

    v=spf1 include:spf-imr.rabobank.nl include:spf.protection.outlook.com include:spf.eu.mailmarshal.cloud include:spf.serverbeheer.faceworks.nl ip4:145.72.121.0/24 ip4:83.137.145.128/25 ip4:54.229.31.57 -all

  • SPF syntax validcritical

    SPF syntax is correct ✓

  • SPF policy strict (-all)recommended

    SPF uses -all (hard fail) ✓

  • DKIM foundrecommended

    DKIM selector: selector1 ✓

  • DMARC record presentrecommended

    v=DMARC1; p=reject; rua=mailto:difuwh3e@ag.eu.dmarcadvisor.com

  • DMARC policy quarantine or betterrecommended

    DMARC policy: reject ✓

  • DMARC policy rejectoptional

    DMARC policy: reject ✓

  • BIMI record presentoptional

    BIMI logo: https://bimi.rabobank.nl/RABOImagemarkRGB-BIMI.svg

  • BIMI configuration validoptional

    BIMI correctly configured ✓

  • MTA-STS record presentoptional

    MTA-STS configured ✓

  • MTA-STS policy enforcedoptional

    MTA-STS mode: enforce ✓

  • MX records validcritical

    1 MX record(s) ✓

  • MX domains use DNSSECrecommended

    1/1 MX domain(s) use DNSSEC ✓

  • MX DNSSEC validation OKrecommended

    MX DNSSEC validates correctly ✓

  • Mail servers not blacklistedinfo

    Not listed on 11 blacklists, but Spamhaus SBL could not be checked from IntoDNS.ai — result inconclusive

  • No critical blacklist listingsinfo

    Not listed on 11 blacklists, but Spamhaus SBL could not be checked from IntoDNS.ai — result inconclusive

Web security

64%warning
  • CAA records presentrecommended

    7 CAA record(s) ✓

  • CAA policy strictoptional

    CAA limits certificate authorities ✓

  • TLSA records (DANE)optional

    No TLSA/DANE records. Add TLSA at _25._tcp.mail for DANE email encryption

  • DANE configuration validoptional

    No DANE configured

  • No sensitive info in TXTcritical

    No sensitive data leaked ✓

  • Verification records reviewedinfo

    10 verification records found (Google, DocuSign, Adobe IDP, OneTrust, Microsoft 365...). Review these - they reveal your tech stack to attackers. Remove unused service verifications

  • HTTPS availablecritical

    HTTPS working (status 403) ✓

  • Valid certificatecritical

    Certificate chain is valid and trusted ✓

  • HTTP redirects to HTTPSinfo

    Could not verify (plain-HTTP request was blocked or got no response)

  • HSTS enabledinfo

    Could not verify (homepage answered 403 to the scanner)

  • HSTS max-age >= 1 yearinfo

    Could not verify (homepage answered 403 to the scanner)

  • X-Frame-Options headerinfo

    Could not verify (homepage answered 403 to the scanner)

  • X-Content-Type-Options headerinfo

    Could not verify (homepage answered 403 to the scanner)

  • Content-Security-Policy headerinfo

    Could not verify (homepage answered 403 to the scanner)

  • Referrer-Policy headerinfo

    Could not verify (homepage answered 403 to the scanner)

  • security.txt presentinfo

    Could not verify (security.txt requests failed or were blocked)

  • security.txt validinfo

    Could not verify (security.txt requests failed or were blocked)

  • HTTP/3 (QUIC) supportedoptional

    No HTTP/3 support detected No h3 in Alt-Svc header No HTTPS DNS record (type 65) QUIC probe inconclusive (Inconclusive - no QUIC reply (trigger may be dropped or UDP/443 filtered)) — not a negative signal

  • QUIC UDP reachableinfo

    QUIC probe inconclusive (no reply — trigger may be dropped or UDP/443 filtered). Not a negative signal; h3 is judged from Alt-Svc / HTTPS record

  • HTTPS DNS record (SVCB)optional

    No HTTPS DNS record (type 65). Add HTTPS record for faster HTTP/3 discovery: rabobank.nl IN HTTPS 1 . alpn="h3,h2"

Issues found (2)

Excessive verification TXT records

Your domain has many third-party verification records. These reveal your tech stack to potential attackers (reconnaissance). Review and remove unused verifications

Learn more about Excessive verification TXT records

No HTTP/3 (QUIC) support

HTTP/3 uses QUIC for faster, more resilient connections. Enable it on your web server and open UDP/443 in your firewall

Learn more about No HTTP/3 (QUIC) support

Recommendations (2)

Review verification TXT records

Your domain has many third-party verification records that reveal your tech stack (Google, Microsoft, Atlassian, etc.). Review each one: 1) Remove records for services no longer used 2) Consider if each service really needs domain verification 3) Use a subdomain for less critical services. This is an information disclosure issue - attackers can map your SaaS footprint.

Impact: Reduces reconnaissance surface and limits attacker knowledge of your infrastructure

Enable HTTP/3 (QUIC)

Enable HTTP/3 for faster page loads and improved connection resilience. Nginx: add "listen 443 quic reuseport;" and "add_header Alt-Svc 'h3=":443"; ma=86400'". Caddy: HTTP/3 is enabled by default. Cloudflare: Enable under Speed → Protocol Optimization. Also add an HTTPS DNS record: example.com IN HTTPS 1 . alpn="h3,h2" Ensure UDP port 443 is open in your firewall (QUIC uses UDP, not TCP).

Impact: Faster page loads (0-RTT), better mobile performance, and connection migration between networks

About this report

IntoDNS.AI evaluates rabobank.nl against DNS hygiene, email authentication, and transport-security best practices, scoring each check and rolling them up into an overall grade. This is a stored snapshot of public DNS as observed on November 9, 2026; it may differ from a live scan if the domain has since changed its configuration.

Want to check your own domain? Scan any domain on the homepage.

Snapshot from: November 9, 2026 · Google Public DNS