woerden.nl

Checked 22 October 2026, 17:20 UTC · via 8.8.8.8
!Passed with warnings
23 passed 8 warnings 0 failed 1 info

SPF

warn

SPF record published

Found

Record
v=spf1 ip4:167.89.49.67 ip4:77.74.49.8 include:spf.protection.outlook.com include:_spf.sc.nines.nl include:spf.eprov.nl include:spf.simgroephosting.nl ip4:213.208.232.101 ip6:2001:4cb8:59c:1::25 ip4:194.53.72.252 ip4:91.230.244.106 ip4:54.228.64.14 ip4:54.75.202.170 ip4:84.241.182.106 ip6:2001:1690:2:416::167 ip4:185.136.64.128/27 ip4:185.136.65.128/27 ip4:176.74.239.242 ip4:213.208.232.101 ip6:2A07:CB84:3075:912:10:10:159:25 ip6:2A07:CB81:3711:815:10:10:160:25 ip4:54.240.91.164 ip4:54.240.91.162 ip4:69.169.231.93 ip4:54.240.91.163 ip4:69.169.231.92 ip4:31.149.18.110 ip4:37.200.85.0/24 ip6:2a07:5200::/29 ip4:178.22.83.175 ip4:185.46.182.1 ip4:185.46.182.200/29 ip4:185.46.182.208/31 ip4:176.74.239.242 ip4:213.208.232.101 ip4:194.53.72.4 ip4:194.53.72.10 ip4:194.53.72.252 ip6:2001:4cb8:59c:1::25 ip6:2A07:CB84:3075:912:10:10:159:25 ~all
DNS lookups
4 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 4 of 10 DNS lookups #2
    SPF record needs 4 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.
  • !
    Broad IP ranges
    These ranges authorize tens of thousands of addresses or more: ip6:2a07:5200::/29. Check that you really own and send from all of them.
    #27

DMARC

warn

p=quarantine (_dmarc.woerden.nl)

Found

Record
v=DMARC1; p=quarantine
Found at
_dmarc.woerden.nl
TagValueMeaning
vDMARC1Version
pquarantinePolicy

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

warn

Selectors: mail, k1, selector2

Found

Selectors
mail, k1, selector2
_domainkey
NOERROR
SelectorKeyFlags
mailRSA 1024 bits
k1RSA 1024 bits
selector2RSA 2048 bits

Checks

  • ✓ Keys found: mail, k1, selector2 #7
    DKIM keys found for this domain with selectors: mail, k1, selector2
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: mail (1024 bits), k1 (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 (2)
DS at parent
Yes
Algorithms
ECDSAP256SHA256 (13)
Key tags
24138, 61440
Signatures valid until
29 October 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 expire in 151h0m0s
    DNSKEY signatures expire at 2026-10-29T00:00:00Z (in 151h0m0s). Check that re-signing works.
    #21

MX

warn

1 mail server

Found

PriorityHostRecordsReverse DNS
10woerden-nl.g-v1.mx.microsoftA 52.101.103.39 A 52.101.68.10 A 52.101.91.162 A 52.101.91.21 AAAA 2a01:111:f403:ca48::a AAAA 2a01:111:f403:ca48::e AAAA 2a01:111:f403:ca04::b AAAA 2a01:111:f403:ca04::amail-miypr05cu00207.inbound.protection.outlook.com ✓ mail-dbbpr03cu00102.inbound.protection.outlook.com ✓ mail-matpr04cu00302.inbound.protection.outlook.com ✓ mail-matpr05cu00105.inbound.protection.outlook.com ✓ mail-miypr02cu00202.inbound.protection.outlook.com ✓ mail-miypr03cu00206.inbound.protection.outlook.com ✓ mail-dbbpr03cu00103.inbound.protection.outlook.com ✓ mail-du0pr03cu00102.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 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 1 of 1 MX hosts

Found

DANE (TLSA records)

MX hostTLSADNSSEC
woerden-nl.g-v1.mx.microsoft3 1 1 803f7447cc75b208… 3 1 1 cfd68bde4129c00a… 2 0 1 ea7a25255d111fc3… 2 0 1 c1ad7778796d20bc… 3 1 1 54883cc5f1849331…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