leipzig.de

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

SPF

pass

SPF record published

Found

Record
v=spf1 a:leipzig.de mx ip4:212.122.61.0/24 include:spf.protection.outlook.com -all
DNS lookups
3 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 3 of 10 DNS lookups #2
    SPF record needs 3 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=quarantine (_dmarc.leipzig.de)

Found

Record
v=DMARC1; p=quarantine; rua=mailto:dmarc@leipzig.de; ruf=mailto:spfdkimfail@leipzig.de; fo=1; aspf=s;
Found at
_dmarc.leipzig.de
TagValueMeaning
vDMARC1Version
pquarantinePolicy
ruamailto:dmarc@leipzig.deAggregate report addresses
rufmailto:spfdkimfail@leipzig.deFailure report addresses
aspfsSPF alignment (r = relaxed, s = strict)
fo1Failure reporting options

Checks

  • !
    Policy: quarantine
    DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.
    #4
  • ✓ 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.
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:dmarc@leipzig.de
  • ✓ Subdomain policy: quarantine #20
    Subdomains are covered by policy 'quarantine'.
  • ✓ 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

warn

1 mail server

Found

PriorityHostRecordsReverse DNS
10mailin.lecos-gmbh.deA 212.122.61.144mailin.lecos-gmbh.de ✓

Checks

  • ✓ 1 MX record #9
    Found 1 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: mailin.lecos-gmbh.de
    #11
  • !
    Single MX host, no backup
    Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • ✓ At most 5 MX records #13
    Found 1 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 1 MX address have a PTR record that resolves back to them.

TLS

fail

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

Found

MTA-STS record
v=STSv1; id=01122025;
Policy URL
https://mta-sts.leipzig.de/.well-known/mta-sts.txt
Mode
Allowed MX
Max age
0 seconds

DANE (TLSA records)

MX hostTLSADNSSEC
mailin.lecos-gmbh.denone-

Checks

  • ✓ Record published #32
    MTA-STS record found with id 01122025.
  • ✗
    Invalid policy
    Senders ignore the MTA-STS policy because of: invalid line "Policy"; version must be STSv1, got ""; mode must be enforce, testing or none, got ""; max_age is missing; no mx: lines; every MX host must be listed.
    #33
  • !
    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
  • 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