deutsches-spionagemuseum.de

Checked 21 October 2026, 22:13 UTC · via 8.8.8.8
✗Problems found
21 passed 6 warnings 2 failed 1 info

SPF

pass

SPF record published

Found

Record
v=spf1 mx include:_spf.jpberlin.de include:_spf.zonezero.de include:spf.crsend.com ~all
DNS lookups
8 of 10
Void lookups
0 of 2

Checks

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

Found

Record
v=DMARC1; p=none; rua=mailto:rua@dmarc.brevo.com,dmarc+deutsches-spionagemuseum.de@zzml.de; ruf=mailto:dmarc-forensics+deutsches-spionagemuseum.de@zzml.de
Found at
_dmarc.deutsches-spionagemuseum.de
External report address
mailto:rua@dmarc.brevo.com (authorized)
External report address
dmarc+deutsches-spionagemuseum.de@zzml.de (only mailto: report addresses are supported by receivers)
External report address
mailto:dmarc-forensics+deutsches-spionagemuseum.de@zzml.de (not authorized)
TagValueMeaning
vDMARC1Version
pnonePolicy
ruamailto:rua@dmarc.brevo.com,dmarc+deutsches-spionagemuseum.de@zzml.deAggregate report addresses
rufmailto:dmarc-forensics+deutsches-spionagemuseum.de@zzml.deFailure report addresses

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:rua@dmarc.brevo.com, dmarc+deutsches-spionagemuseum.de@zzml.de
  • !
    Report address not authorized
    These report addresses are in another domain that has not agreed to receive your reports, so receivers will not send them: mailto:dmarc-forensics+deutsches-spionagemuseum.de@zzml.de (needs deutsches-spionagemuseum.de._report._dmarc.zzml.de). Ask the report provider to publish the record, or check the address.
    #29

DKIM

warn

Selectors: mail

Found

Selectors
mail
_domainkey
NOERROR
SelectorKeyFlags
mailRSA 1024 bits

Checks

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

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 ✓
50mx-n.heinlein-support.deA 91.198.250.17mx-n.mailbox.org ✓

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, mx-n.heinlein-support.de
    #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 4 MX addresss have a PTR record that resolves back to them.

TLS

fail

no MTA-STS · no TLS-RPT · DANE on 4 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
mx-n.heinlein-support.de3 1 1 6b0dd472d3c50d1e… 3 1 1 3fb24e3ee20fd8b0…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, mx-n.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