mecklenburg-vorpommern.de

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

SPF

pass

SPF record published

Found

Record
v=spf1 include:_spf.dvz-mv.de ip4:85.13.149.179/32 -all
DNS lookups
1 of 10
Void lookups
0 of 2

Checks

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

No DMARC record found

Checks

  • ✗
    No DMARC record
    No DMARC record was found for this domain. DMARC is essential for preventing email spoofing. Add a DMARC record with p=reject or at least p=quarantine.
    #5

DKIM

fail

No keys found under the checked selectors

Found

Selectors
None found
_domainkey
NXDOMAIN

Checks

  • ✗
    No DKIM keys published
    _domainkey.mecklenburg-vorpommern.de does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.
    #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

2 mail servers

Found

PriorityHostRecordsReverse DNS
10mx03.mvnet.deA 85.208.248.81 AAAA 2a02:1006:c000:0:194:25:109:19mx03.mvnet.de ✓ no PTR
10mx04.mvnet.deA 85.208.250.82 AAAA 2a02:1006:c000:0:194:25:109:20mx04.mvnet.de ✓ no PTR

Checks

  • ✓ 2 MX records #9
    Found 2 MX records for this domain.
  • ✓ All hosts resolve #10
    All MX records resolve to valid IP addresses.
  • ✓ All hosts have IPv6 #11
    All MX records resolve to IPv6 addresses.
  • ✓ 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.
  • !
    Addresses without reverse DNS
    These MX addresses have no PTR record, which many receivers treat as a spam signal: 2a02:1006:c000:0:194:25:109:19 (mx03.mvnet.de), 2a02:1006:c000:0:194:25:109:20 (mx04.mvnet.de). Ask your hosting provider to set one.
    #30

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mx03.mvnet.de3 0 1 63947a05cfac69ee…Yes
mx04.mvnet.de3 0 1 08e03bf18bf95916…Yes

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
  • ✓ DANE on all MX hosts #36
    All 2 MX hosts publish DNSSEC-validated TLSA records.

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