lifeline.de

Checked 21 October 2026, 23:12 UTC · via 8.8.8.8
✗Problems found
22 passed 4 warnings 1 failed 1 info

SPF

pass

SPF record published

Found

Record
v=spf1 mx a:mail.boreus.de a:mail.boreus-status.de a:custmail-out.boreus.de a:gv-web2.fmg.boreus.de include:_spf.mx.cloudflare.net include:amazonses.com include:newsletter.dcmservice.de ~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

fail

p=none (_dmarc.lifeline.de)

Found

Record
v=DMARC1; p=none; rua=mailto:postmaster@lifeline.de; ruf=mailto:postmaster@lifeline.de; fo=1
Found at
_dmarc.lifeline.de
TagValueMeaning
vDMARC1Version
pnonePolicy
ruamailto:postmaster@lifeline.deAggregate report addresses
rufmailto:postmaster@lifeline.deFailure report addresses
fo1Failure reporting options

Checks

  • ✗
    Policy: none (monitoring only)
    DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.
    #4
  • ✓ Record published #5
    DMARC record exists for this domain.
  • ✓ Valid syntax #17
    DMARC record syntax is valid.
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:postmaster@lifeline.de
  • ✓ Report addresses in own domain #29
    All report addresses are in your own organizational domain.

DKIM

warn

No keys found under the checked selectors

Found

Selectors
None found
_domainkey
NOERROR

Checks

  • !
    No key under common selectors
    The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.
    #7

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

3 mail servers

Found

PriorityHostRecordsReverse DNS
44route1.mx.cloudflare.netA 162.159.205.11 A 162.159.205.13 A 162.159.205.12 AAAA 2606:4700:f5::c AAAA 2606:4700:f5::d AAAA 2606:4700:f5::broute1.mx.cloudflare.net ✓ route1.mx.cloudflare.net ✓ route1.mx.cloudflare.net ✓ route1.mx.cloudflare.net ✓ route1.mx.cloudflare.net ✓ route1.mx.cloudflare.net ✓
96route3.mx.cloudflare.netA 162.159.205.25 A 162.159.205.24 A 162.159.205.23 AAAA 2606:4700:f5::11 AAAA 2606:4700:f5::13 AAAA 2606:4700:f5::12route3.mx.cloudflare.net ✓ route3.mx.cloudflare.net ✓ route3.mx.cloudflare.net ✓ route3.mx.cloudflare.net ✓ route3.mx.cloudflare.net ✓ route3.mx.cloudflare.net ✓
98route2.mx.cloudflare.netA 162.159.205.18 A 162.159.205.19 A 162.159.205.17 AAAA 2606:4700:f5::f AAAA 2606:4700:f5::e AAAA 2606:4700:f5::10route2.mx.cloudflare.net ✓ route2.mx.cloudflare.net ✓ route2.mx.cloudflare.net ✓ route2.mx.cloudflare.net ✓ route2.mx.cloudflare.net ✓ route2.mx.cloudflare.net ✓

Checks

  • ✓ 3 MX records #9
    Found 3 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 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.
  • ✓ Reverse DNS confirmed #30
    All 18 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
route1.mx.cloudflare.net2 1 1 59e738e674221702… 3 1 1 0f0c6c164a36f97e… 3 1 1 9be5b7d47f9eff93…Yes
route3.mx.cloudflare.net2 1 1 59e738e674221702… 3 1 1 0f0c6c164a36f97e… 3 1 1 9be5b7d47f9eff93…Yes
route2.mx.cloudflare.net2 1 1 59e738e674221702… 3 1 1 9be5b7d47f9eff93… 3 1 1 0f0c6c164a36f97e…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 3 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