westcordhotels.nl

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

SPF

fail

SPF record published

Found

Record
v=spf1 ip4:151.193.18.41 ip4:151.193.20.41 ip4:151.193.21.23 ip4:151.193.19.230 ip4:35.192.181.145 ip4:35.222.49.21 ip4:34.132.184.222 ip4:34.69.44.134 ip4:35.223.170.93 ip4:34.86.254.203 ip4:34.85.182.168 ip4:34.145.244.232 ip4:34.150.215.45 ip4:35.245.27.80 mx ip4:80.73.129.142 ip4:80.73.132.105 ip4:193.138.250.92 ip4:84.241.182.106 ip6:2001:1690:2:416::167 include:amazonses.com include:spf.ecbase.nl include:mailgun.org include:spf.protection.outlook.com include:spf.mtaroutes.com ~all
DNS lookups
12 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✗
    12 DNS lookups, over the limit of 10
    SPF record needs 12 DNS lookups (including nested includes), more than the limit of 10. Receivers will return a permerror; reduce includes or flatten the record.
    #2
  • ✓ 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.westcordhotels.nl)

Found

Record
v=DMARC1; p=quarantine; pct=100; rua=mailto:dmarc@westcordhotels.onmicrosoft.com; ruf=mailto:dmarc@westcordhotels.onmicrosoft.com; sp=quarantine; fo=0
Found at
_dmarc.westcordhotels.nl
External report address
mailto:dmarc@westcordhotels.onmicrosoft.com (not authorized)
TagValueMeaning
vDMARC1Version
pquarantinePolicy
spquarantineSubdomain policy
pct100Percentage of mail the policy applies to
ruamailto:dmarc@westcordhotels.onmicrosoft.comAggregate report addresses
rufmailto:dmarc@westcordhotels.onmicrosoft.comFailure report addresses
fo0Failure 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 100% of mail #18
    DMARC policy applies to all failing mail.
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:dmarc@westcordhotels.onmicrosoft.com
  • ✓ Subdomain policy: quarantine #20
    Subdomains are covered by policy 'quarantine'.
  • !
    Report address not authorized
    These report addresses are in another domain that has not agreed to receive your reports, so receivers will not send them: mailto:dmarc@westcordhotels.onmicrosoft.com (needs westcordhotels.nl._report._dmarc.westcordhotels.onmicrosoft.com). Ask the report provider to publish the record, or check the address.
    #29

DKIM

pass

Selectors: selector1, s1, s2

Found

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

Checks

  • ✓ Keys found: selector1, s1, s2 #7
    DKIM keys found for this domain with selectors: selector1, s1, s2
  • ✓ Strong keys #23
    DKIM keys are strong enough: selector1: 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

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-eu.mtaroutes.comA 149.13.75.27 AAAA 2001:978:2:2c::137:100fe1-r3-in.fra02.l.antispamcloud.com ✓ fe2-r3-in.ams14.l.antispamcloud.com ✓
20mx2-eu.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-eu.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-eu.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-eu.mtaroutes.com3 1 1 a10ec56f992e0e0c…Yes
mx2-eu.mtaroutes.com3 1 1 a10ec56f992e0e0c…Yes
mx3-eu.mtaroutes.com3 1 1 a10ec56f992e0e0c…Yes
mx4-eu.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