wetterzentrale.de

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

SPF

fail

No SPF record found

Checks

  • ✗
    No SPF record
    No SPF record was found for this domain. SPF is important for preventing email spoofing. Add an SPF record to specify which servers are authorized to send email for your domain.
    #6

DMARC

fail

p=none (_dmarc.wetterzentrale.de)

Found

Record
v=DMARC1;p=none;rua=wetterzentrale@gmail.com
Found at
_dmarc.wetterzentrale.de
External report address
wetterzentrale@gmail.com (only mailto: report addresses are supported by receivers)
TagValueMeaning
vDMARC1Version
pnonePolicy
ruawetterzentrale@gmail.comAggregate report addresses

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: wetterzentrale@gmail.com
  • !
    Unsupported report address
    Receivers only send reports to mailto: addresses: wetterzentrale@gmail.com.
    #29

DKIM

fail

No keys found under the checked selectors

Found

Selectors
None found
_domainkey
NXDOMAIN

Checks

  • ✗
    No DKIM keys published
    _domainkey.wetterzentrale.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

pass

2 mail servers

Found

PriorityHostRecordsReverse DNS
10mx1.forwardemail.netA 138.197.213.185 A 121.127.44.56 AAAA 2604:a880:2:d0::306:1 AAAA 2a02:6ea0:d71e::2mx1.forwardemail.net ✓ mx1.forwardemail.net ✓ mx1.forwardemail.net ✓ mx1.forwardemail.net ✓
20mx2.forwardemail.netA 121.127.44.59 A 104.248.224.170 AAAA 2a02:6ea0:d71e::1 AAAA 2604:a880:400:d1::cd:9001mx2.forwardemail.net ✓ mx2.forwardemail.net ✓ mx2.forwardemail.net ✓ mx2.forwardemail.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.
  • ✓ 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.
  • ✓ Reverse DNS confirmed #30
    All 8 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mx1.forwardemail.net3 1 1 5e81da1af16df20b… 3 1 1 321f694ead3a2e73…Yes
mx2.forwardemail.net3 1 1 5e81da1af16df20b… 3 1 1 321f694ead3a2e73…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