hr.nl

Checked 22 October 2026, 13:51 UTC · via 8.8.8.8
✗Problems found
26 passed 6 warnings 2 failed

SPF

pass

SPF record published

Found

Record
v=spf1 ip4:10.1.44.0/24 ip4:10.11.12.0/23 ip4:104.47.0.0/17 ip4:13.127.80.230 ip4:13.54.0.137 ip4:13.54.3.158 ip4:13.54.44.75 ip4:13.54.69.230 ip4:13.74.56.125 ip4:13.79.21.104 ip4:13.88.226.191 ip4:13.94.232.90 ip4:132.174.100.127 ip4:145.24.0.0/16 ip4:145.255.128.0/21 ip4:15.206.47.138 ip4:168.63.28.84 ip4:172.172.139.18 ip4:178.162.177.161 ip4:178.21.19.52 ip4:178.21.19.65 ip4:18.156.115.231 ip4:18.156.139.5 ip4:18.156.146.215 ip4:18.156.56.232 ip4:18.196.171.132 include:spf1.hr.nl ~all
DNS lookups
7 of 10
Void lookups
0 of 2

Checks

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

fail

p=none (_dmarc.hr.nl)

Found

Record
v=DMARC1; p=none; rua=mailto:dmarc-reports@hr.nl; ruf=mailto:dmarc-reports@hr.nl; fo=s
Found at
_dmarc.hr.nl
TagValueMeaning
vDMARC1Version
pnonePolicy
ruamailto:dmarc-reports@hr.nlAggregate report addresses
rufmailto:dmarc-reports@hr.nlFailure report addresses
fosFailure reporting options

Checks

  • ✗
    Policy: none (monitoring only)
    DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.
    #4
  • ✓ Record published #5
    DMARC record exists for this domain.
  • ✓ Valid syntax #17
    DMARC record syntax is valid.
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:dmarc-reports@hr.nl
  • ✓ Report addresses in own domain #29
    All report addresses are in your own organizational domain.

DKIM

warn

Selectors: mail, selector2, s1, s2

Found

Selectors
mail, selector2, s1, s2
_domainkey
NOERROR
SelectorKeyFlags
mailRSA 1024 bits
selector2RSA 1024 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), selector2 (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

warn

Signed, DS published at parent

Found

DNSKEY records
Yes (3)
DS at parent
Yes
Algorithms
RSASHA256 (8)
Key tags
18084, 36580, 6451
Signatures valid until
26 October 2026, 05:11 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 expire in 87h0m0s
    DNSKEY signatures expire at 2026-10-26T05:11:57Z (in 87h0m0s). Check that re-signing works.
    #21

MX

warn

6 mail servers

Found

PriorityHostRecordsReverse DNS
100suffix01.hro.nlA 145.24.129.232suffix01.hro.nl ✓
100suffix02.hro.nlA 145.24.129.233suffix02.hro.nl ✓
100suffix03.hro.nlA 145.24.129.234suffix03.hro.nl ✓
100suffix04.hro.nlA 145.24.129.235suffix04.hro.nl ✓
100suffix05.hro.nlA 145.24.129.236suffix05.hro.nl ✓
100suffix06.hro.nlA 145.24.129.237suffix06.hro.nl ✓

Checks

  • ✓ 6 MX records #9
    Found 6 MX records for this domain.
  • ✓ All hosts resolve #10
    All MX records resolve to valid IP addresses.
  • !
    Hosts without IPv6
    The following MX hosts could not be resolved to IPv6 addresses: suffix01.hro.nl, suffix02.hro.nl, suffix03.hro.nl, suffix04.hro.nl, suffix05.hro.nl, suffix06.hro.nl
    #11
  • ✓ Redundant MX hosts #12
    Found 6 MX records, which provides redundancy for email delivery.
  • !
    More than 5 MX records
    Found 6 MX records, which is more than the recommended maximum of 5. Too many MX records may indicate a misconfiguration.
    #13
  • ✓ 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 6 MX addresss have a PTR record that resolves back to them.

TLS

warn

MTA-STS testing · TLS-RPT · DANE on 6 of 6 MX hosts

Found

MTA-STS record
v=STSv1; id=20180627T010101;
Policy URL
https://mta-sts.hr.nl/.well-known/mta-sts.txt
Mode
testing
Allowed MX
suffix01.hro.nl, suffix02.hro.nl, suffix03.hro.nl, suffix04.hro.nl, suffix05.hro.nl, suffix06.hro.nl
Max age
86400 seconds
TLS-RPT record
v=TLSRPTv1; rua=mailto:smtp-tls-reports@hr.nl

DANE (TLSA records)

MX hostTLSADNSSEC
suffix01.hro.nl3 1 1 31f6d6ca3b85a853…Yes
suffix02.hro.nl3 1 1 31f6d6ca3b85a853…Yes
suffix03.hro.nl3 1 1 31f6d6ca3b85a853…Yes
suffix04.hro.nl3 1 1 31f6d6ca3b85a853…Yes
suffix05.hro.nl3 1 1 31f6d6ca3b85a853…Yes
suffix06.hro.nl3 1 1 31f6d6ca3b85a853…Yes

Checks

  • ✓ Record published #32
    MTA-STS record found with id 20180627T010101.
  • !
    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:smtp-tls-reports@hr.nl
  • ✓ DANE on all MX hosts #36
    All 6 MX hosts publish DNSSEC-validated TLSA records.

BIMI

fail

https://cdn.hr.nl/logo.svg

Found

Record
v=BIMI1; l=https://cdn.hr.nl/logo.svg;
Found at
default._bimi.hr.nl
Logo
https://cdn.hr.nl/logo.svg

Checks

  • !
    No certificate (a=)
    The logo is published without a Verified Mark Certificate. Gmail and Apple Mail only show BIMI logos with a VMC or CMC; Yahoo shows it without one.
    #38
  • ✗
    DMARC not strict enough for BIMI
    Mail clients will not show the logo. BIMI requires DMARC p=quarantine or p=reject (now p=none), a subdomain policy other than sp=none.
    #39