hartstichting.nl

Checked 21 October 2026, 21:21 UTC · via 8.8.8.8
!Passed with warnings
25 passed 5 warnings 0 failed 4 info

SPF

warn

SPF record published

Found

Record
v=spf1 redirect=_sph2khs0q.sdmarc.net
DNS lookups
4 of 10
Void lookups
0 of 2
Problem
include:_sph2khs0q2.sdmarc.net could not be resolved: DNS query for _sph2khs0q2.sdmarc.net failed: read udp 46.225.38.91:33797->8.8.8.8:53: i/o timeout

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • !
    4 of 10 DNS lookups, with problems
    SPF record needs 4 DNS lookups (limit is 10). Problems found: include:_sph2khs0q2.sdmarc.net could not be resolved: DNS query for _sph2khs0q2.sdmarc.net failed: read udp 46.225.38.91:33797->8.8.8.8:53: i/o timeout.
    #2
  • i
    Delegated via redirect
    SPF record has no 'all' mechanism but redirects to _sph2khs0q.sdmarc.net, whose policy applies.
    #3
  • ✓ 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

pass

p=reject (_dmarc.hartstichting.nl)

Found

Record
v=DMARC1; p=reject; ri=604800; rua=mailto:a.ph2khs0q@sdmarc.net; adkim=r; aspf=r
Found at
_dmarc.hartstichting.nl
External report address
mailto:a.ph2khs0q@sdmarc.net (authorized)
TagValueMeaning
vDMARC1Version
prejectPolicy
ruamailto:a.ph2khs0q@sdmarc.netAggregate report addresses
adkimrDKIM alignment (r = relaxed, s = strict)
aspfrSPF alignment (r = relaxed, s = strict)
ri604800Report interval (seconds)

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:a.ph2khs0q@sdmarc.net
  • ✓ Subdomain policy: reject #20
    Subdomains are covered by policy 'reject'.
  • ✓ External report addresses authorized #29
    Report addresses in other domains have published their authorization.

DKIM

warn

Selectors: mail, selector2, s1, s2

Found

Selectors
mail, selector2, s1, s2
_domainkey
NOERROR
SelectorKeyFlags
mailRSA 1024 bits
selector2RSA 2048 bits
s1RSA 2048 bits
s2RSA 2048 bits

Checks

  • ✓ Keys found: mail, selector2, s1, s2 #7
    DKIM keys found for this domain with selectors: mail, selector2, s1, s2
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: mail (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

info

DNS query for hartstichting.nl failed: read udp 46.225.38.91:38199->8.8.8.8:53: i/o timeout

Checks

  • i
    Could not be checked
    The DNSSEC lookup failed, so this could not be checked: DNS query for hartstichting.nl failed: read udp 46.225.38.91:38199->8.8.8.8:53: i/o timeout
    #8

MX

warn

1 mail server

Found

PriorityHostRecordsReverse DNS
0hartstichting-nl.mail.protection.outlook.comA 52.101.103.137 A 52.101.209.153 A 52.101.103.39 A 52.101.68.27 AAAA 2a01:111:f403:ca09::20 AAAA 2a01:111:f403:ca09::22 AAAA 2a01:111:f403:ca21::8 AAAA 2a01:111:f403:ca3c::8mail-miypr02cu00101.inbound.protection.outlook.com ✓ lookup failed mail-miypr05cu00207.inbound.protection.outlook.com (does not resolve back) mail-db7pr03cu00503.inbound.protection.outlook.com ✓ lookup failed mail-am7pr02cu00302.inbound.protection.outlook.com ✓ mail-matpr04cu00100.inbound.protection.outlook.com ✓ mail-zrxpr05cu00100.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 does not match
    The PTR name of these addresses does not resolve back to the same address: 52.101.103.39 -> mail-miypr05cu00207.inbound.protection.outlook.com.
    #30

TLS

warn

MTA-STS testing · TLS-RPT · DANE on 0 of 1 MX hosts (lookup failed for 1)

Found

MTA-STS record
v=STSv1; id=1719249992
Policy URL
https://mta-sts.hartstichting.nl/.well-known/mta-sts.txt
Mode
testing
Allowed MX
hartstichting-nl.mail.protection.outlook.com
Max age
604800 seconds
TLS-RPT record
v=TLSRPTv1; rua=mailto:reports@sendmarc.net

DANE (TLSA records)

MX hostTLSADNSSEC
hartstichting-nl.mail.protection.outlook.comDNS query for _25._tcp.hartstichting-nl.mail.protection.outlook.com failed: read udp 46.225.38.91:59796->8.8.8.8:53: i/o timeout-

Checks

  • ✓ Record published #32
    MTA-STS record found with id 1719249992.
  • !
    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:reports@sendmarc.net
  • i
    Could not be checked
    The TLSA lookup failed for: hartstichting-nl.mail.protection.outlook.com (DNS query for _25._tcp.hartstichting-nl.mail.protection.outlook.com failed: read udp 46.225.38.91:59796->8.8.8.8:53: i/o timeout).
    #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