werkzoeken.nl

Checked 22 October 2026, 17:11 UTC · via 8.8.8.8
!Passed with warnings
29 passed 4 warnings 0 failed

SPF

pass

SPF record published

Found

Record
v=spf1 ip6:2a11:4881:1:2ef::1 ip4:178.251.232.134 ip4:159.183.170.89 ip4:149.72.45.219 include:_spf.google.com include:sendgrid.net ~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=quarantine (_dmarc.werkzoeken.nl)

Found

Record
v=DMARC1; p=quarantine; pct=100;
Found at
_dmarc.werkzoeken.nl
TagValueMeaning
vDMARC1Version
pquarantinePolicy
pct100Percentage of mail the policy applies to

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.
  • !
    No aggregate reports (rua)
    DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...
    #19
  • ✓ Subdomain policy: quarantine #20
    Subdomains are covered by policy 'quarantine'.

DKIM

pass

Selectors: google, s1, s2

Found

Selectors
google, s1, s2
_domainkey
NOERROR
SelectorKeyFlags
googleRSA 2048 bits
s1RSA 2048 bits
s2RSA 2048 bits

Checks

  • ✓ Keys found: google, s1, s2 #7
    DKIM keys found for this domain with selectors: google, s1, s2
  • ✓ Strong keys #23
    DKIM keys are strong enough: google: RSA 2048 bits; s1: RSA 2048 bits; s2: RSA 2048 bits.
  • ✓ 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
2371, 34505
Signatures valid until
18 December 2026, 12:04 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-12-18 #21
    DNSKEY signatures are valid until 2026-12-18T12:04:54Z.

MX

pass

2 mail servers

Found

PriorityHostRecordsReverse DNS
10mx1.mijn.hostA 5.254.117.212 A 5.254.117.163 AAAA 2a03:5180:7:2:6a9:cee6:d12a:1 AAAA 2a03:5180:7:2:84c:3c00:38fc:1mx1.mijn.host ✓ mx1.mijn.host ✓ mx1.mijn.host ✓ mx1.mijn.host ✓
20mx2.mijn.hostA 5.254.117.213 A 5.254.117.162 AAAA 2a03:5180:7:2:40c:b98a:6b6d:1 AAAA 2a03:5180:7:2:878:5f5a:930f:1mx2.mijn.host ✓ mx2.mijn.host ✓ mx2.mijn.host ✓ mx2.mijn.host ✓

Checks

  • ✓ 2 MX records #9
    Found 2 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.
  • ✓ Redundant MX hosts #12
    Found 2 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 2 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 2 of 2 MX hosts

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mx1.mijn.host2 1 1 6bd9212ce649c659… 3 1 1 ac551042c5329d7c… 2 1 1 e1ae9c3de848ece1…Yes
mx2.mijn.host2 1 1 6bd9212ce649c659… 3 1 1 ac551042c5329d7c… 2 1 1 e1ae9c3de848ece1…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 2 MX hosts publish DNSSEC-validated TLSA records.

BIMI

pass

https://bimi.entrust.net/werkzoeken.nl/logo.svg

Found

Record
v=BIMI1;l=https://bimi.entrust.net/werkzoeken.nl/logo.svg;a=https://bimi.entrust.net/werkzoeken.nl/certchain.pem
Found at
default._bimi.werkzoeken.nl
Logo
https://bimi.entrust.net/werkzoeken.nl/logo.svg
Certificate
https://bimi.entrust.net/werkzoeken.nl/certchain.pem

Checks

  • ✓ Logo and certificate published #38
    BIMI logo: https://bimi.entrust.net/werkzoeken.nl/logo.svg; certificate: https://bimi.entrust.net/werkzoeken.nl/certchain.pem
  • ✓ DMARC meets BIMI requirements #39
    DMARC is enforced on all mail, as BIMI requires.