munzinger.de

Checked 21 October 2026, 23:31 UTC · via 8.8.8.8
!Passed with warnings
28 passed 3 warnings 0 failed 2 info

SPF

pass

SPF record published

Found

Record
v=spf1 a mx ip4:93.241.1.128/26 ip4:37.24.145.112/28 ip6:2003:de:8018::/48 include:newsmailservice.de include:protection.outlook.com ~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

warn

p=reject (_dmarc.munzinger.de)

Found

Record
v=DMARC1; p=reject; adkim=s; aspf=s;
Found at
_dmarc.munzinger.de
TagValueMeaning
vDMARC1Version
prejectPolicy
adkimsDKIM alignment (r = relaxed, s = strict)
aspfsSPF alignment (r = relaxed, s = strict)

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

Found

Selectors
default
_domainkey
NOERROR
SelectorKeyFlags
defaultRSA 2048 bitsh=sha256

Checks

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

2 mail servers

Found

PriorityHostRecordsReverse DNS
10mx0.munzinger.deA 93.241.1.139mx0.munzinger.de ✓
20mx1.munzinger.deA 93.241.1.138mx1.munzinger.de ✓

Checks

  • ✓ 2 MX records #9
    Found 2 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: mx0.munzinger.de, mx1.munzinger.de
    #11
  • ✓ Redundant MX hosts #12
    Found 2 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 2 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 2 MX addresss have a PTR record that resolves back to them.

TLS

info

MTA-STS enforce · TLS-RPT · DANE on 0 of 2 MX hosts

Found

MTA-STS record
v=STSv1; id=20260812110000Z;
Policy URL
https://mta-sts.munzinger.de/.well-known/mta-sts.txt
Mode
enforce
Allowed MX
mx0.munzinger.de, mx1.munzinger.de
Max age
86400 seconds
TLS-RPT record
v=TLSRPTv1; rua=mailto:hostmaster@munzinger.dei

DANE (TLSA records)

MX hostTLSADNSSEC
mx0.munzinger.denone-
mx1.munzinger.denone-

Checks

  • ✓ Record published #32
    MTA-STS record found with id 20260812110000Z.
  • ✓ Policy enforced #33
    The MTA-STS policy is enforced and cached for 24h0m0s.
  • ✓ All MX hosts covered #34
    Every MX host matches an mx: line of the MTA-STS policy.
  • ✓ Reports enabled #35
    TLS reports are sent to: mailto:hostmaster@munzinger.dei
  • i
    Not used
    No MX host publishes TLSA records. DANE lets senders verify your mail server's certificate through DNSSEC; it requires DNSSEC on the MX host's zone.
    #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