dpunkt.de

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

SPF

pass

SPF record published

Found

Record
v=spf1 mx ip4:5.175.14.88 ip4:93.191.162.150 ip4:116.202.87.23 ip4:188.40.159.225 ip4:188.40.159.226 ip4:188.40.189.211 ip4:109.90.85.210 ip4:116.202.229.23 ip4:116.202.229.43 ip4:103.241.48.0/26 ip4:194.8.219.19/29 ip4:147.93.208.0/24 ip4:147.93.209.0/24 a:mail.xeneris.net include:_spf.pretix.eu ~all
DNS lookups
5 of 10
Void lookups
0 of 2

Checks

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

warn

p=reject (_dmarc.dpunkt.de)

Found

Record
v=DMARC1;p=reject;
Found at
_dmarc.dpunkt.de
TagValueMeaning
vDMARC1Version
prejectPolicy

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.
  • !
    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
  • ✓ Subdomain policy: reject #20
    Subdomains are covered by policy 'reject'.

DKIM

pass

Selectors: default, mail

Found

Selectors
default, mail
_domainkey
NOERROR
SelectorKeyFlags
defaultRSA 2048 bits
mailRSA 2048 bitsh=sha256

Checks

  • ✓ Keys found: default, mail #7
    DKIM keys found for this domain with selectors: default, mail
  • ✓ Strong keys #23
    DKIM keys are strong enough: default: RSA 2048 bits; mail: 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

warn

3 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 ✓

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: mx1.heinlein-support.de, mx2.heinlein-support.de, mx3.heinlein-support.de
    #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.
  • ✓ Reverse DNS confirmed #30
    All 3 MX addresss have a PTR record that resolves back to them.

TLS

fail

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mx1.heinlein-support.de3 1 1 6b0dd472d3c50d1e… 3 1 1 3fb24e3ee20fd8b0…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

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