wassenaar.nl

Checked 22 October 2026, 17:11 UTC · via 8.8.8.8
!Passed with warnings
25 passed 7 warnings 0 failed 1 info

SPF

pass

SPF record published

Found

Record
v=spf1 ip4:20.103.184.18 ip4:212.178.211.6 ip4:212.178.211.15 ip4:212.178.211.16 include:_spf.zorgmail.nl include:spf.protection.outlook.com ip4:83.217.77.34 ip4:31.223.171.250 ip4:78.108.130.89 include:spf.eprov.nl include:spf.topdesk.net include:spf.simgroephosting.nl include:spf.pinkprivate.cloud ip4:194.13.163.7 ip4:194.53.14.66 ip4:69.169.224.0/20 include:spfklant.pinkroccade.nl -all
DNS lookups
8 of 10
Void lookups
0 of 2

Checks

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

pass

p=reject (_dmarc.wassenaar.nl)

Found

Record
v=DMARC1; p=reject; pct=100; rua=mailto:dmarc_report@wassenaar.nl,mailto:rapportages@dmarc.ibdgemeenten.nl; ruf=mailto:dmarc_report@wassenaar.nl; fo=1; adkim=r; aspf=r
Found at
_dmarc.wassenaar.nl
External report address
mailto:rapportages@dmarc.ibdgemeenten.nl (authorized)
TagValueMeaning
vDMARC1Version
prejectPolicy
pct100Percentage of mail the policy applies to
ruamailto:dmarc_report@wassenaar.nl,mailto:rapportages@dmarc.ibdgemeenten.nlAggregate report addresses
rufmailto:dmarc_report@wassenaar.nlFailure report addresses
adkimrDKIM alignment (r = relaxed, s = strict)
aspfrSPF alignment (r = relaxed, s = strict)
fo1Failure reporting options

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:dmarc_report@wassenaar.nl, mailto:rapportages@dmarc.ibdgemeenten.nl
  • ✓ 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

Found

Selectors
mail, selector2
_domainkey
NOERROR
SelectorKeyFlags
mailRSA 2048 bitstest mode (t=y)
selector2RSA 1024 bits

Checks

  • ✓ Keys found: mail, selector2 #7
    DKIM keys found for this domain with selectors: mail, selector2
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: selector2 (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    Key in test mode
    These keys have t=y, so receivers treat DKIM failures as a test: mail. Remove t=y once DKIM works.
    #24

DNSSEC

pass

Signed, DS published at parent

Found

DNSKEY records
Yes (2)
DS at parent
Yes
Algorithms
RSASHA256 (8)
Key tags
49081, 11332
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

1 mail server

Found

PriorityHostRecordsReverse DNS
10wsn-mail.wassenaar.nlA 20.103.184.16no PTR

Checks

  • ✓ 1 MX record #9
    Found 1 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: wsn-mail.wassenaar.nl
    #11
  • !
    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.
  • !
    Addresses without reverse DNS
    These MX addresses have no PTR record, which many receivers treat as a spam signal: 20.103.184.16 (wsn-mail.wassenaar.nl). Ask your hosting provider to set one.
    #30

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
wsn-mail.wassenaar.nl3 0 1 ec854e551fc4b5fc… 3 0 1 ed125a46725025f1…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