centerparcs.de

Checked 21 October 2026, 22:06 UTC · via 8.8.8.8
!Passed with warnings
23 passed 6 warnings 0 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 -all
DNS lookups
0 of 10
Void lookups
0 of 2

Checks

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

Found

Record
v=DMARC1; p=reject; rua=mailto:corporateoffice.office365-dmarc@groupepvcp.com
Found at
_dmarc.centerparcs.de
External report address
mailto:corporateoffice.office365-dmarc@groupepvcp.com (authorized)
TagValueMeaning
vDMARC1Version
prejectPolicy
ruamailto:corporateoffice.office365-dmarc@groupepvcp.comAggregate report addresses

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:corporateoffice.office365-dmarc@groupepvcp.com
  • ✓ 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: selector1, selector2

Found

Selectors
selector1, selector2
_domainkey
NXDOMAIN
SelectorKeyFlags
selector1RSA 1024 bits
selector2RSA 1024 bits

Checks

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

warn

5 mail servers

Found

PriorityHostRecordsReverse DNS
5centerparcs-de.mail.protection.outlook.comA 52.101.103.39 A 52.101.103.162 A 52.101.185.114 A 52.101.68.25 AAAA 2a01:111:f403:ca09::a AAAA 2a01:111:f403:ca21::e AAAA 2a01:111:f403:ca21::8 AAAA 2a01:111:f403:ca21::amail-miypr05cu00207.inbound.protection.outlook.com ✓ mail-miypr03cu00202.inbound.protection.outlook.com ✓ mail-zrxpr04cu00102.inbound.protection.outlook.com ✓ mail-db8pr02cu00101.inbound.protection.outlook.com ✓ mail-am7pr02cu00202.inbound.protection.outlook.com ✓ mail-matpr04cu00306.inbound.protection.outlook.com ✓ mail-matpr04cu00100.inbound.protection.outlook.com ✓ mail-maspr04cu00102.inbound.protection.outlook.com ✓
10centerparcs-de.mail.eo.outlook.comA 52.101.209.31 A 52.101.91.153 A 52.101.68.25 A 52.101.185.21 AAAA 2a01:111:f403:ca09::24 AAAA 2a01:111:f403:ca04::c AAAA 2a01:111:f403:ca04::10 AAAA 2a01:111:f403:ca3c::amail-cpjpr05cu00207.inbound.protection.outlook.com ✓ mail-matpr04cu00101.inbound.protection.outlook.com ✓ mail-db8pr02cu00101.inbound.protection.outlook.com ✓ mail-zrxpr05cu00105.inbound.protection.outlook.com ✓ mail-am6pr02cu00204.inbound.protection.outlook.com ✓ mail-db9pr02cu00204.inbound.protection.outlook.com ✓ mail-dbapr03cu00100.inbound.protection.outlook.com ✓ mail-zrxpr07cu00102.inbound.protection.outlook.com ✓
20mail.centerparcs.nlA 193.172.165.15static.kpn.net (does not resolve back)
30mx1.networking4all.com(does not resolve)
40mx2.networking4all.net(does not resolve)

Checks

  • ✓ 5 MX records #9
    Found 5 MX records for this domain.
  • !
    Hosts without IP addresses
    The following MX hosts could not be resolved to IP addresses: mx1.networking4all.com, mx2.networking4all.net
    #10
  • !
    Hosts without IPv6
    The following MX hosts could not be resolved to IPv6 addresses: mail.centerparcs.nl, mx1.networking4all.com, mx2.networking4all.net
    #11
  • ✓ Redundant MX hosts #12
    Found 5 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 5 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 does not match
    The PTR name of these addresses does not resolve back to the same address: 193.172.165.15 -> static.kpn.net.
    #30

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
centerparcs-de.mail.protection.outlook.comnone-
centerparcs-de.mail.eo.outlook.comnone-
mail.centerparcs.nlnone-
mx1.networking4all.comnone-
mx2.networking4all.netnone-

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
  • i
    Not configured
    TLS-RPT lets senders report TLS delivery problems to you. It is most useful together with MTA-STS or DANE.
    #35
  • i
    Not used
    No MX host publishes TLSA records. DANE lets senders verify your mail server's certificate through DNSSEC; it requires DNSSEC on the MX host's zone.
    #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