bouwendnederland.nl

Checked 21 October 2026, 21:00 UTC · via 8.8.8.8
!Passed with warnings
27 passed 5 warnings 0 failed 1 info

SPF

pass

SPF record published

Found

Record
v=spf1 include:amazonses.com include:_spf.mailplus.nl include:spf.protection.outlook.com include:spf.topdesk.net include:spfklant.pinkroccade.nl include:spf.steam-connect.com ip4:85.90.79.37 ip4:90.145.221.192 ip4:92.66.66.141 ip4:213.197.217.201 ip4:213.197.217.202 ip4:85.90.79.53 ip4:88.151.120.64/26 ip4:5.255.75.0/24 ip4:89.20.185.128/27 ip6:2a00:1ca8:1f:63::0/64 ip4:188.64.79.15 ~all
DNS lookups
6 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 6 of 10 DNS lookups #2
    SPF record needs 6 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.bouwendnederland.nl)

Found

Record
v=DMARC1; p=quarantine; rua=mailto:dmarc-reports@bouwendnederland.nl
Found at
_dmarc.bouwendnederland.nl
TagValueMeaning
vDMARC1Version
pquarantinePolicy
ruamailto:dmarc-reports@bouwendnederland.nlAggregate report addresses

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:dmarc-reports@bouwendnederland.nl
  • ✓ Subdomain policy: quarantine #20
    Subdomains are covered by policy 'quarantine'.
  • ✓ Report addresses in own domain #29
    All report addresses are in your own organizational domain.

DKIM

warn

Selectors: mail, selector1, s1, s2

Found

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

Checks

  • ✓ Keys found: mail, selector1, s1, s2 #7
    DKIM keys found for this domain with selectors: mail, selector1, s1, s2
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: mail (1024 bits), selector1 (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
15804, 26021
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
0bouwendnederland-nl.c-v1.mx.microsoftA 52.101.68.21 A 52.101.73.155 A 52.101.185.21 A 52.101.68.8 AAAA 2a01:111:f403:ca04::f AAAA 2a01:111:f403:c967::a AAAA 2a01:111:f403:ca09::20 AAAA 2a01:111:f403:ca04::bmail-db4pr02cu00205.inbound.protection.outlook.com ✓ mail-am7pr02cu00203.inbound.protection.outlook.com ✓ mail-zrxpr05cu00105.inbound.protection.outlook.com ✓ mail-du0pr03cu00100.inbound.protection.outlook.com ✓ mail-db7pr03cu00507.inbound.protection.outlook.com ✓ mail-cpjpr05cu00102.inbound.protection.outlook.com ✓ mail-as8pr05cu00400.inbound.protection.outlook.com ✓ mail-dbbpr03cu00103.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

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
bouwendnederland-nl.c-v1.mx.microsoft3 1 1 803f7447cc75b208… 2 0 1 ea7a25255d111fc3… 3 1 1 54883cc5f1849331… 2 0 1 c1ad7778796d20bc… 3 1 1 cfd68bde4129c00a…Yes

Checks

  • !
    Not configured
    MTA-STS is not configured, so other mail servers fall back to unencrypted delivery when TLS fails or is stripped by an attacker. Publish a _mta-sts TXT record and a policy at https://mta-sts.<domain>/.well-known/mta-sts.txt.
    #32
  • !
    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
  • ✓ DANE on all MX hosts #36
    All 1 MX host publish DNSSEC-validated TLSA records.

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