wichelen.be

Checked 22 October 2026, 07:30 UTC · via 8.8.8.8
!Passed with warnings
25 passed 6 warnings 0 failed 1 info

SPF

pass

SPF record published

Found

Record
v=spf1 a:spf.wichelen.be include:spf.protection.outlook.com include:smtproutes.com include:spf.lcp.be include:oclcspf3.oclc.org include:recreatex.be -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

warn

p=quarantine (_dmarc.wichelen.be)

Found

Record
v=DMARC1;p=quarantine;pct=50;rua=mailto:dmarc@wichelen.be;ruf=mailto:dmarc@wichelen.be;fo=1;
Found at
_dmarc.wichelen.be
TagValueMeaning
vDMARC1Version
pquarantinePolicy
pct50Percentage of mail the policy applies to
ruamailto:dmarc@wichelen.beAggregate report addresses
rufmailto:dmarc@wichelen.beFailure report addresses
fo1Failure reporting options

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 50% of mail
    DMARC policy only applies to 50% of failing mail (pct=50). Raise pct to 100 once you are confident in your setup.
    #18
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:dmarc@wichelen.be
  • ✓ Subdomain policy: quarantine #20
    Subdomains are covered by policy 'quarantine'.
  • ✓ Report addresses in own domain #29
    All report addresses are in your own organizational domain.

DKIM

warn

Selectors: selector1, s1, s2

Found

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

Checks

  • ✓ Keys found: selector1, s1, s2 #7
    DKIM keys found for this domain with selectors: selector1, s1, s2
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: selector1 (1024 bits), 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

warn

Not signed

Found

DNSKEY records
No (0)
DS at parent
No

Checks

  • !
    Not enabled
    DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8

MX

pass

4 mail servers

Found

PriorityHostRecordsReverse DNS
10mx1.mtaroutes.comA 154.59.104.23 AAAA 2001:978:2:2c::137:100fe2-r3-in.ams14.l.antispamcloud.com ✓ fe2-r3-in.ams14.l.antispamcloud.com ✓
20mx2.mtaroutes.comA 149.13.75.27 AAAA 2001:978:2:7::162:100fe1-r3-in.fra02.l.antispamcloud.com ✓ fe1-r3-in.fra02.l.antispamcloud.com ✓
30mx3.mtaroutes.comA 154.59.104.23 AAAA 2001:978:2:2c::137:100fe2-r3-in.ams14.l.antispamcloud.com ✓ fe2-r3-in.ams14.l.antispamcloud.com ✓
40mx4.mtaroutes.comA 154.59.193.124 AAAA 2001:978:2:6::f:124fe3-r3-in.du01.l.antispamcloud.com ✓ fe3-r3-in.du01.l.antispamcloud.com ✓

Checks

  • ✓ 4 MX records #9
    Found 4 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 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 8 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mx1.mtaroutes.com3 1 1 a10ec56f992e0e0c…Yes
mx2.mtaroutes.com3 1 1 a10ec56f992e0e0c…Yes
mx3.mtaroutes.com3 1 1 a10ec56f992e0e0c…Yes
mx4.mtaroutes.com3 1 1 a10ec56f992e0e0c…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 4 MX hosts 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