waterlandvanfriesland.nl

Checked 22 October 2026, 17:11 UTC · via 8.8.8.8
✗Problems found
22 passed 6 warnings 1 failed 1 info

SPF

pass

SPF record published

Found

Record
v=spf1 ip4:146.177.19.34 include:_web01.qdcspf.nl include:spf.tribecrm.nl include:spf.dc.accent.nl include:freedom.nl include:amazonses.com ~all
DNS lookups
9 of 10
Void lookups
0 of 2

Checks

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

Found

Record
v=DMARC1; p=none; sp=none;
Found at
_dmarc.waterlandvanfriesland.nl
TagValueMeaning
vDMARC1Version
pnonePolicy
spnoneSubdomain policy

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.
  • !
    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

DKIM

warn

Selectors: s1, s2

Found

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

Checks

  • ✓ Keys found: s1, s2 #7
    DKIM keys found for this domain with selectors: s1, s2
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: 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
60443
Signatures valid until
5 November 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-11-05 #21
    DNSKEY signatures are valid until 2026-11-05T00:00:00Z.

MX

warn

4 mail servers

Found

PriorityHostRecordsReverse DNS
20mxfw1.qdc.nlA 92.63.171.198 A 92.63.169.48se01-vrs.route25.eu ✓ se02-vrs.route25.eu ✓
30mxfw2.qdc.nlA 185.109.217.137 A 92.63.172.180se03-vrs.route25.eu ✓ se04-vrs.route25.eu ✓
40mxfw3.qdc.nlA 92.63.171.198 A 92.63.169.48se01-vrs.route25.eu ✓ se02-vrs.route25.eu ✓
70mx.soverin.netA 185.233.34.143 A 185.233.34.15 AAAA 2a10:de80:1:4091:b9e9:22f:0:1 AAAA 2a10:de80:1:4092:b9e9:228f:0:1mx.soverin.net ✓ mx.soverin.net ✓ mx.soverin.net ✓ mx.soverin.net ✓

Checks

  • ✓ 4 MX records #9
    Found 4 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: mxfw1.qdc.nl, mxfw2.qdc.nl, mxfw3.qdc.nl
    #11
  • ✓ Redundant MX hosts #12
    Found 4 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 4 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 10 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mxfw1.qdc.nlnone-
mxfw2.qdc.nlnone-
mxfw3.qdc.nlnone-
mx.soverin.net3 1 1 a6eb48052b5a83aa…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
  • !
    Not all MX hosts use DANE
    These MX hosts publish no TLSA records, so mail to them is not protected by DANE: mxfw1.qdc.nl, mxfw2.qdc.nl, mxfw3.qdc.nl.
    #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