schwaebisch-gmuend.de

Checked 22 October 2026, 00:02 UTC · via 8.8.8.8
✗Problems found
20 passed 4 warnings 1 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 a mx ip4:78.46.4.219 ip4:31.25.159.178 ip4:46.229.45.31 include:spf.nl2go.com include:_spf.jpberlin.de include:_spf-eu.ionos.com include:spf.protect.kvnbw.de include:spf.brevo.com ip4:91.216.90.0/24 -all
DNS lookups
10 of 10
Void lookups
0 of 2

Checks

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

p=none (_dmarc.schwaebisch-gmuend.de)

Found

Record
v=DMARC1; p=none; rua=mailto:postmaster@schwaebisch-gmuend.de; ruf=mailto:postmaster@schwaebisch-gmuend.de; fo=1
Found at
_dmarc.schwaebisch-gmuend.de
TagValueMeaning
vDMARC1Version
pnonePolicy
ruamailto:postmaster@schwaebisch-gmuend.deAggregate report addresses
rufmailto:postmaster@schwaebisch-gmuend.deFailure report addresses
fo1Failure reporting options

Checks

  • ✗
    Policy: none (monitoring only)
    DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.
    #4
  • ✓ Record published #5
    DMARC record exists for this domain.
  • ✓ Valid syntax #17
    DMARC record syntax is valid.
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:postmaster@schwaebisch-gmuend.de
  • ✓ 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

4 mail servers

Found

PriorityHostRecordsReverse DNS
5mx6.kvnbw.deA 194.0.94.48mx6.kvnbw.de ✓
6mx7.kvnbw.deA 194.0.94.49mx7.kvnbw.de ✓
7mx8.kvnbw.deA 194.59.36.34mx8.kvnbw.de ✓
8mx9.kvnbw.deA 194.59.36.35mx9.kvnbw.de ✓

Checks

  • ✓ 4 MX records #9
    Found 4 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: mx6.kvnbw.de, mx7.kvnbw.de, mx8.kvnbw.de, mx9.kvnbw.de
    #11
  • ✓ Redundant MX hosts #12
    Found 4 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 4 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 4 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mx6.kvnbw.denone-
mx7.kvnbw.denone-
mx8.kvnbw.denone-
mx9.kvnbw.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