moemax.de

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

SPF

pass

SPF record published

Found

Record
v=spf1 include:_spf0162.ppsmtp.net include:_spfxxxlutz.xxxlutz.at ip4:20.52.210.253 ip4:20.52.138.252 ~all
DNS lookups
4 of 10
Void lookups
0 of 2

Checks

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

pass

p=reject (_dmarc.moemax.de)

Found

Record
v=DMARC1; p=reject; rua=mailto:5a7b235c98ba708@rep.dmarcanalyzer.com; ruf=mailto:5a7b235c98ba708@for.dmarcanalyzer.com; fo=1;
Found at
_dmarc.moemax.de
External report address
mailto:5a7b235c98ba708@rep.dmarcanalyzer.com (authorized)
External report address
mailto:5a7b235c98ba708@for.dmarcanalyzer.com (authorized)
TagValueMeaning
vDMARC1Version
prejectPolicy
ruamailto:5a7b235c98ba708@rep.dmarcanalyzer.comAggregate report addresses
rufmailto:5a7b235c98ba708@for.dmarcanalyzer.comFailure report addresses
fo1Failure reporting options

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.
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:5a7b235c98ba708@rep.dmarcanalyzer.com
  • ✓ Subdomain policy: reject #20
    Subdomains are covered by policy 'reject'.
  • ✓ External report addresses authorized #29
    Report addresses in other domains have published their authorization.

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

pass

Signed, DS published at parent

Found

DNSKEY records
Yes (2)
DS at parent
Yes
Algorithms
ECDSAP256SHA256 (13)
Key tags
2371, 34505
Signatures valid until
18 December 2026, 13:01 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 valid until 2026-12-18 #21
    DNSKEY signatures are valid until 2026-12-18T13:01:19Z.

MX

warn

2 mail servers

Found

PriorityHostRecordsReverse DNS
10mx0162.ppsmtp.comA 130.61.134.46 A 130.61.134.44 A 130.61.134.47pp2006.ppsmtp.net ✓ pp0162.ppsmtp.net ✓ pp2048.ppsmtp.net ✓
10mx0162.ppsmtp.deA 130.61.134.46 A 130.61.134.44 A 130.61.134.47pp2006.ppsmtp.net ✓ pp0162.ppsmtp.net ✓ pp2048.ppsmtp.net ✓

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: mx0162.ppsmtp.com, mx0162.ppsmtp.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 6 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mx0162.ppsmtp.comnone-
mx0162.ppsmtp.denone-

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
  • i
    Not configured
    TLS-RPT lets senders report TLS delivery problems to you. It is most useful together with MTA-STS or DANE.
    #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

pass

https://bimi.entrust.net/moemax.at/logo.svg

Found

Record
v=BIMI1;l=https://bimi.entrust.net/moemax.at/logo.svg;a=https://bimi.entrust.net/moemax.at/certchain.pem
Found at
default._bimi.moemax.de
Logo
https://bimi.entrust.net/moemax.at/logo.svg
Certificate
https://bimi.entrust.net/moemax.at/certchain.pem

Checks

  • ✓ Logo and certificate published #38
    BIMI logo: https://bimi.entrust.net/moemax.at/logo.svg; certificate: https://bimi.entrust.net/moemax.at/certchain.pem
  • ✓ DMARC meets BIMI requirements #39
    DMARC is enforced on all mail, as BIMI requires.