nbb.be

Checked 22 October 2026, 06:51 UTC · via 8.8.8.8
!Passed with warnings
27 passed 6 warnings 0 failed 2 info

SPF

pass

SPF record published

Found

Record
v=spf1 mx a:mail01.nbb.be a:mail02.nbb.be include:spf.protection.outlook.com -all
DNS lookups
4 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 4 of 10 DNS lookups #2
    SPF record needs 4 DNS lookups (limit is 10).
  • ✓ Ends with -all #3
    SPF record properly uses -all to restrict unauthorized senders.
  • ✓ Record published #6
    SPF record exists for this domain.
  • ✓ Single record #16
    Exactly one SPF record is published.
  • ✓ Valid syntax #25
    All SPF mechanisms and modifiers are valid.
  • ✓ No void lookups #26
    All include/redirect targets exist.
  • ✓ No overly broad IP ranges #27
    All ip4/ip6 ranges are narrow enough.

DMARC

warn

p=quarantine (_dmarc.nbb.be)

Found

Record
v=DMARC1; p=quarantine; sp=none;rua=mailto:58bd3536@mxtoolbox.dmarc-report.com,mailto:Infrastructure.Mail@nbb.be,mailto:dmarc_agg@vali.email;ruf=mailto:58bd3536@forensics.dmarc-report.com,mailto:Infrastructure.Mail@nbb.be;fo=1
Found at
_dmarc.nbb.be
External report address
mailto:58bd3536@mxtoolbox.dmarc-report.com (authorized)
External report address
mailto:dmarc_agg@vali.email (authorized)
External report address
mailto:58bd3536@forensics.dmarc-report.com (authorized)
TagValueMeaning
vDMARC1Version
pquarantinePolicy
spnoneSubdomain policy
ruamailto:58bd3536@mxtoolbox.dmarc-report.com,mailto:Infrastructure.Mail@nbb.be,mailto:dmarc_agg@vali.emailAggregate report addresses
rufmailto:58bd3536@forensics.dmarc-report.com,mailto:Infrastructure.Mail@nbb.beFailure report addresses
fo1Failure reporting options

Checks

  • !
    Policy: quarantine
    DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.
    #4
  • ✓ Record published #5
    DMARC record exists for this domain.
  • ✓ Valid syntax #17
    DMARC record syntax is valid.
  • ✓ Applies to 100% of mail #18
    DMARC policy applies to all failing mail.
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:58bd3536@mxtoolbox.dmarc-report.com, mailto:Infrastructure.Mail@nbb.be, mailto:dmarc_agg@vali.email
  • !
    Subdomains unprotected (sp=none)
    DMARC subdomain policy is sp=none, so spoofed mail from subdomains is not blocked. Consider sp=quarantine or sp=reject.
    #20
  • ✓ External report addresses authorized #29
    Report addresses in other domains have published their authorization.

DKIM

warn

Selectors: selector1, selector2, s1, s2

Found

Selectors
selector1, selector2, s1, s2
_domainkey
NOERROR
SelectorKeyFlags
selector1RSA 2048 bits
selector2RSA 2048 bits
s1RSA 2048 bits
s2RSA 1024 bits

Checks

  • ✓ Keys found: selector1, selector2, s1, s2 #7
    DKIM keys found for this domain with selectors: selector1, selector2, s1, s2
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: s2 (1024 bits). Rotate to a 2048-bit key.
    #23
  • ✓ No problematic flags #24
    No keys in test mode, revoked, or limited to SHA-1.

DNSSEC

pass

Signed, DS published at parent

Found

DNSKEY records
Yes (2)
DS at parent
Yes
Algorithms
ECDSAP256SHA256 (13)
Key tags
7215, 47016
Signatures valid until
27 November 2026, 00:00 UTC

Checks

  • ✓ Signed, DS published at parent #8
    DNSSEC is enabled for this domain (DNSKEY and DS present), providing additional security for DNS lookups.
  • ✓ Signatures valid until 2026-11-27 #21
    DNSKEY signatures are valid until 2026-11-27T00:00:23Z.

MX

warn

1 mail server

Found

PriorityHostRecordsReverse DNS
10nbb-be.mail.protection.outlook.comA 52.101.185.21 A 52.101.209.28 A 52.101.91.159 A 52.101.73.155 AAAA 2a01:111:f403:ca21::8 AAAA 2a01:111:f403:ca38::8 AAAA 2a01:111:f403:ca3c::a AAAA 2a01:111:f403:ca09::amail-zrxpr05cu00105.inbound.protection.outlook.com ✓ mail-cpjpr05cu00104.inbound.protection.outlook.com ✓ mail-matpr04cu00207.inbound.protection.outlook.com ✓ mail-am7pr02cu00203.inbound.protection.outlook.com ✓ mail-matpr04cu00100.inbound.protection.outlook.com ✓ mail-wa4pr04cu00100.inbound.protection.outlook.com ✓ mail-zrxpr07cu00102.inbound.protection.outlook.com ✓ mail-am7pr02cu00202.inbound.protection.outlook.com ✓

Checks

  • ✓ 1 MX record #9
    Found 1 MX records for this domain.
  • ✓ All hosts resolve #10
    All MX records resolve to valid IP addresses.
  • ✓ All hosts have IPv6 #11
    All MX records resolve to IPv6 addresses.
  • !
    Single MX host, no backup
    Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • ✓ At most 5 MX records #13
    Found 1 MX records, which is within the recommended range (1-5).
  • ✓ No localhost targets #14
    No MX records pointing to localhost found.
  • ✓ No private IP addresses #15
    No MX records resolving to private IP addresses found.
  • ✓ No CNAME targets #22
    No MX records point to a CNAME.
  • ✓ Reverse DNS confirmed #30
    All 8 MX addresss have a PTR record that resolves back to them.

TLS

warn

MTA-STS testing · no TLS-RPT · DANE on 0 of 1 MX hosts

Found

MTA-STS record
v=STSv1; id=20250729000000Z;
Policy URL
https://mta-sts.nbb.be/.well-known/mta-sts.txt
Mode
testing
Allowed MX
nbb-be.mail.protection.outlook.com
Max age
3600 seconds

DANE (TLSA records)

MX hostTLSADNSSEC
nbb-be.mail.protection.outlook.comnone-

Checks

  • ✓ Record published #32
    MTA-STS record found with id 20250729000000Z.
  • !
    Policy in testing mode
    With mode: testing, senders only report TLS problems (via TLS-RPT) and still deliver without TLS. Switch to mode: enforce once reports are clean. max_age is only 3600 seconds; use at least a week (604800) so the policy stays cached.
    #33
  • ✓ All MX hosts covered #34
    Every MX host matches an mx: line of the MTA-STS policy.
  • !
    Not configured
    MTA-STS or DANE is used without TLS-RPT, so you get no reports when senders fail to deliver because of TLS problems. Publish _smtp._tls TXT "v=TLSRPTv1; rua=mailto:...".
    #35
  • i
    Not used
    No MX host publishes TLSA records. DANE lets senders verify your mail server's certificate through DNSSEC; it requires DNSSEC on the MX host's zone.
    #36

BIMI

info

No BIMI record

Checks

  • i
    Not configured
    BIMI shows your logo next to your mail in supporting mail clients. It requires DMARC enforcement.
    #38