care.de

Checked 21 October 2026, 22:06 UTC · via 8.8.8.8
✗Problems found
24 passed 7 warnings 1 failed 1 info

SPF

fail

SPF record published

Found

Record
v=spf1 include:spf.mailjet.com include:spf.protection.outlook.com include:amazonses.com include:agenturserver.de include:spfa.myconvento.com include:_spf.mlsend.com include:srv2.de include:_spf.salesforce.com include:sendgrid.net -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

pass

p=reject (_dmarc.care.de)

Found

Record
v=DMARC1; p=reject; rua=mailto:61bd9377aa664689b18def5a4583f790@dmarc-reports.cloudflare.net; fo=1; adkim=r; aspf=r;
Found at
_dmarc.care.de
External report address
mailto:61bd9377aa664689b18def5a4583f790@dmarc-reports.cloudflare.net (authorized)
TagValueMeaning
vDMARC1Version
prejectPolicy
ruamailto:61bd9377aa664689b18def5a4583f790@dmarc-reports.cloudflare.netAggregate 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:61bd9377aa664689b18def5a4583f790@dmarc-reports.cloudflare.net
  • ✓ 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, s1, s2

Found

Selectors
selector1, s1, s2
_domainkey
NOERROR
SelectorKeyFlags
selector1RSA 2048 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: 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

Signed, but no DS at parent

Found

DNSKEY records
Yes (2)
DS at parent
No
Algorithms
ECDSAP256SHA256 (13)
Key tags
2371, 34505
Signatures valid until
29 November 2026, 13:46 UTC

Checks

  • !
    Signed, but no DS at parent
    The zone is signed (DNSKEY present) but the parent has no DS record, so the chain of trust is incomplete. Publish the DS record at your registrar.
    #8
  • ✓ Signatures valid until 2026-11-29 #21
    DNSKEY signatures are valid until 2026-11-29T13:46:52Z.

MX

warn

3 mail servers

Found

PriorityHostRecordsReverse DNS
10mxa.global.inbound.cf-emailsecurity.netA 172.65.64.105no PTR
10mxb.global.inbound.cf-emailsecurity.netA 141.101.90.40no PTR
20care-de.mail.protection.outlook.comA 52.101.170.1 A 52.101.170.2 A 52.101.170.0 A 52.101.168.0 AAAA 2a01:111:f403:ca2d::1 AAAA 2a01:111:f403:ca2d::2 AAAA 2a01:111:f403:ca2d:: AAAA 2a01:111:f403:ca27::mail-fr4p281cu03101.inbound.protection.outlook.com ✓ mail-fr6p281cu00202.inbound.protection.outlook.com ✓ mail-fr5p281cu00500.inbound.protection.outlook.com ✓ mail-beup281cu00100.inbound.protection.outlook.com ✓ mail-fr4p281cu03101.inbound.protection.outlook.com ✓ mail-fr6p281cu00202.inbound.protection.outlook.com ✓ mail-fr5p281cu00500.inbound.protection.outlook.com ✓ mail-beup281cu00100.inbound.protection.outlook.com ✓

Checks

  • ✓ 3 MX records #9
    Found 3 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: mxa.global.inbound.cf-emailsecurity.net, mxb.global.inbound.cf-emailsecurity.net
    #11
  • ✓ Redundant MX hosts #12
    Found 3 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 3 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: 172.65.64.105 (mxa.global.inbound.cf-emailsecurity.net), 141.101.90.40 (mxb.global.inbound.cf-emailsecurity.net). Ask your hosting provider to set one.
    #30

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mxa.global.inbound.cf-emailsecurity.net3 1 1 e8a50fb03ed780a4… 3 1 1 66928f8426b14ef2… 3 1 1 9122be3be7bcc604… 3 1 1 96c2b0229b798135… 3 1 1 7fed38b4b0b86d8a… 3 1 1 10ba5e544c24746e… 3 1 1 ea0594ba88c82c58… 3 1 1 e2e4ff54d68bc2aa… 3 1 1 64f37496c62dd535… 3 1 1 8e4d63a1e1f68c76… 3 1 1 8dcca72bfe3c99e7… 3 1 1 a07b590f83a529f9…Yes
mxb.global.inbound.cf-emailsecurity.net3 1 1 e2e4ff54d68bc2aa… 3 1 1 ea0594ba88c82c58… 3 1 1 7fed38b4b0b86d8a… 3 1 1 64f37496c62dd535… 3 1 1 9122be3be7bcc604… 3 1 1 a07b590f83a529f9… 3 1 1 66928f8426b14ef2… 3 1 1 8dcca72bfe3c99e7… 3 1 1 8e4d63a1e1f68c76… 3 1 1 10ba5e544c24746e… 3 1 1 e8a50fb03ed780a4… 3 1 1 96c2b0229b798135…Yes
care-de.mail.protection.outlook.comnone-

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
  • !
    Not all MX hosts use DANE
    These MX hosts publish no TLSA records, so mail to them is not protected by DANE: care-de.mail.protection.outlook.com.
    #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