wismar.de

Checked 22 October 2026, 01:01 UTC · via 8.8.8.8
!Passed with warnings
23 passed 8 warnings 0 failed 1 info

SPF

pass

SPF record published

Found

Record
v=spf1 include:_spf.dvz-mv.de include:mail.advantic.de -all
DNS lookups
2 of 10
Void lookups
0 of 2

Checks

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

Found

Record
v=DMARC1; p=quarantine; rua=mailto:edv@wismar.de; ruf=mailto:edv@wismar.de; fo=1; pct=1; sp=none
Found at
_dmarc.wismar.de
TagValueMeaning
vDMARC1Version
pquarantinePolicy
spnoneSubdomain policy
pct1Percentage of mail the policy applies to
ruamailto:edv@wismar.deAggregate report addresses
rufmailto:edv@wismar.deFailure report addresses
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 1% of mail
    DMARC policy only applies to 1% of failing mail (pct=1). Raise pct to 100 once you are confident in your setup.
    #18
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:edv@wismar.de
  • !
    Subdomains unprotected (sp=none)
    DMARC subdomain policy is sp=none, so spoofed mail from subdomains is not blocked. Consider sp=quarantine or sp=reject.
    #20
  • ✓ Report addresses in own domain #29
    All report addresses are in your own organizational domain.

DKIM

warn

Selectors: dkim

Found

Selectors
dkim
_domainkey
NOERROR
SelectorKeyFlags
dkimRSA 1024 bits

Checks

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