sparkasse.de

Checked 22 October 2026, 00:23 UTC · via 8.8.8.8
✗Problems found
22 passed 5 warnings 2 failed 1 info

SPF

pass

SPF record published

Found

Record
v=spf1 mx include:spf.mail.s-web.de include:_spf.jpberlin.de include:spf.protection.outlook.com include:_spf.pixelpark.eu -all
DNS lookups
6 of 10
Void lookups
0 of 2

Checks

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

Found

Record
v=DMARC1; p=none
Found at
_dmarc.sparkasse.de
TagValueMeaning
vDMARC1Version
pnonePolicy

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.
  • !
    No aggregate reports (rua)
    DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...
    #19

DKIM

pass

Selectors: selector1

Found

Selectors
selector1
_domainkey
NOERROR
SelectorKeyFlags
selector1RSA 2048 bits

Checks

  • ✓ Keys found: selector1 #7
    DKIM keys found for this domain with selectors: selector1
  • ✓ Strong keys #23
    DKIM keys are strong enough: selector1: RSA 2048 bits.
  • ✓ No problematic flags #24
    No keys in test mode, revoked, or limited to SHA-1.

DNSSEC

warn

Signed, DS published at parent

Found

DNSKEY records
Yes (3)
DS at parent
Yes
Algorithms
RSASHA256 (8)
Key tags
10218, 54770, 54531
Signatures valid until
25 October 2026, 05:02 UTC

Checks

  • ✓ Signed, DS published at parent #8
    DNSSEC is enabled for this domain (DNSKEY and DS present), providing additional security for DNS lookups.
  • !
    Signatures expire in 77h0m0s
    DNSKEY signatures expire at 2026-10-25T05:02:18Z (in 77h0m0s). Check that re-signing works.
    #21

MX

warn

4 mail servers

Found

PriorityHostRecordsReverse DNS
10mx1.heinlein-support.deA 91.198.250.10mx1.heinlein-support.de ✓
10mx2.heinlein-support.deA 91.198.250.20mx2.heinlein-support.de ✓
20mx3.heinlein-support.deA 91.198.250.30mx3.heinlein-support.de ✓
300sparkasse-de.mail.protection.outlook.comA 52.101.73.126 A 52.101.209.31 A 52.101.68.21 A 52.101.185.24mail-am8pr83cu00106.inbound.protection.outlook.com ✓ mail-cpjpr05cu00207.inbound.protection.outlook.com ✓ mail-db4pr02cu00205.inbound.protection.outlook.com ✓ mail-zrxpr07cu00100.inbound.protection.outlook.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.
  • !
    Hosts without IPv6
    The following MX hosts could not be resolved to IPv6 addresses: mx1.heinlein-support.de, mx2.heinlein-support.de, mx3.heinlein-support.de, sparkasse-de.mail.protection.outlook.com
    #11
  • ✓ 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 7 MX addresss have a PTR record that resolves back to them.

TLS

fail

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mx1.heinlein-support.de3 1 1 3fb24e3ee20fd8b0… 3 1 1 6b0dd472d3c50d1e…No
mx2.heinlein-support.de3 1 1 6b0dd472d3c50d1e… 3 1 1 aab8e6df5d0fcf32…No
mx3.heinlein-support.de3 1 1 6b0dd472d3c50d1e… 3 1 1 c36a0b082b3354e3…No
sparkasse-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
  • ✗
    TLSA records not DNSSEC-validated
    These MX hosts publish TLSA records that the resolver could not validate with DNSSEC, so senders ignore them or, if validation fails, may refuse delivery: mx1.heinlein-support.de, mx2.heinlein-support.de, mx3.heinlein-support.de.
    #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