mopo.de

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

SPF

pass

SPF record published

Found

Record
v=spf1 mx ip4:213.128.128.0/19 ip4:62.201.160.0/19 ip4:87.253.191.2 ip4:87.253.191.3 ip4:134.119.225.33 ip6:2a00:ea8:810e:10::44 ip6:2a00:ea8:810e:10::40 include:spf1.mopo.de include:spf2.mopo.de include:spf3.mopo.de include:spf4.mopo.de include:amazonses.com -all
DNS lookups
9 of 10
Void lookups
0 of 2

Checks

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

Found

Record
v=DMARC1;p=quarantine;pct=35;rua=mailto:support@mopo.de
Found at
_dmarc.mopo.de
TagValueMeaning
vDMARC1Version
pquarantinePolicy
pct35Percentage of mail the policy applies to
ruamailto:support@mopo.deAggregate report addresses

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 35% of mail
    DMARC policy only applies to 35% of failing mail (pct=35). Raise pct to 100 once you are confident in your setup.
    #18
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:support@mopo.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

Selectors: mail, k1, selector1

Found

Selectors
mail, k1, selector1
_domainkey
NOERROR
SelectorKeyFlags
mailRSA 1024 bits
k1RSA 1024 bits
selector1RSA 2048 bits

Checks

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

2 mail servers

Found

PriorityHostRecordsReverse DNS
10mail-gw.hmopo.deA 87.253.191.2 AAAA 2a00:ea8:810e:10::44mail-gw.hmopo.de ✓ mail-gw.hmopo.de ✓
90mail-relay.hmopo.deA 46.114.131.252dynamic-046-114-131-252.46.114.pool.telefonica.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: mail-relay.hmopo.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 3 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
mail-gw.hmopo.denone-
mail-relay.hmopo.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

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