bnnvara.nl

Checked 21 October 2026, 21:00 UTC · via 8.8.8.8
!Passed with warnings
29 passed 4 warnings 0 failed 2 info

SPF

pass

SPF record published

Found

Record
v=spf1 include:bls8bnbdd2.powerspf.com ~all
DNS lookups
3 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 3 of 10 DNS lookups #2
    SPF record needs 3 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=reject (_dmarc.bnnvara.nl)

Found

Record
v=DMARC1; p=reject; sp=none; aspf=s; rua=mailto:4tlq5y0ymz@rua.powerdmarc.com,mailto:dmarc_agg@vali.email; ruf=mailto:4tlq5y0ymz@ruf.powerdmarc.com,mailto:dmarc_agg@vali.email; fo=1; t=n;
Found at
_dmarc.bnnvara.nl
External report address
mailto:4tlq5y0ymz@rua.powerdmarc.com (authorized)
External report address
mailto:dmarc_agg@vali.email (authorized)
External report address
mailto:4tlq5y0ymz@ruf.powerdmarc.com (authorized)
TagValueMeaning
vDMARC1Version
prejectPolicy
spnoneSubdomain policy
ruamailto:4tlq5y0ymz@rua.powerdmarc.com,mailto:dmarc_agg@vali.emailAggregate report addresses
rufmailto:4tlq5y0ymz@ruf.powerdmarc.com,mailto:dmarc_agg@vali.emailFailure report addresses
aspfsSPF alignment (r = relaxed, s = strict)
fo1Failure reporting options
tn

Checks

  • ✓ Policy: reject #4
    DMARC policy is set to 'reject', which provides the strongest protection against email spoofing.
  • ✓ 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:4tlq5y0ymz@rua.powerdmarc.com, 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, s1, s2

Found

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

Checks

  • ✓ Keys found: selector1, s1, s2 #7
    DKIM keys found for this domain with selectors: selector1, s1, s2
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: selector1 (1024 bits), 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 (1)
DS at parent
Yes
Algorithms
ECDSAP256SHA256 (13)
Key tags
19143
Signatures valid until
29 October 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-10-29 #21
    DNSKEY signatures are valid until 2026-10-29T00:00:00Z.

MX

warn

1 mail server

Found

PriorityHostRecordsReverse DNS
8bnnvara-nl.mail.protection.outlook.comA 52.101.73.120 A 52.101.91.162 A 52.101.73.123 A 52.101.68.12 AAAA 2a01:111:f403:ca09::28 AAAA 2a01:111:f403:ca09::26 AAAA 2a01:111:f403:ca04::10 AAAA 2a01:111:f403:ca04::dmail-am7pr02cu00300.inbound.protection.outlook.com ✓ mail-matpr04cu00302.inbound.protection.outlook.com ✓ mail-am6pr02cu00203.inbound.protection.outlook.com ✓ mail-db9pr02cu00204.inbound.protection.outlook.com ✓ mail-am6pr02cu00300.inbound.protection.outlook.com ✓ mail-am8pr83cu00106.inbound.protection.outlook.com ✓ mail-dbapr03cu00100.inbound.protection.outlook.com ✓ mail-db6pr03cu00105.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 · TLS-RPT · DANE on 0 of 1 MX hosts

Found

MTA-STS record
v=STSv1; id=20240214095610322258;
Policy URL
https://mta-sts.bnnvara.nl/.well-known/mta-sts.txt
Mode
testing
Allowed MX
bnnvara-nl.mail.protection.outlook.com
Max age
86400 seconds
TLS-RPT record
v=TLSRPTv1;rua=mailto:4tlq5y0ymz@tls.powerdmarc.com

DANE (TLSA records)

MX hostTLSADNSSEC
bnnvara-nl.mail.protection.outlook.comnone-

Checks

  • ✓ Record published #32
    MTA-STS record found with id 20240214095610322258.
  • !
    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.
    #33
  • ✓ All MX hosts covered #34
    Every MX host matches an mx: line of the MTA-STS policy.
  • ✓ Reports enabled #35
    TLS reports are sent to: mailto:4tlq5y0ymz@tls.powerdmarc.com
  • 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