rhein-zeitung.de

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

SPF

pass

SPF record published

Found

Record
v=spf1 ip4:185.132.224.0/24 include:mail.ktk.de include:spf1.spf.speedkom.net -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.rhein-zeitung.de)

Found

Record
v=DMARC1; p=quarantine; pct=100; rua=mailto:helpdesk@rhein-zeitung.net; ruf=mailto:helpdesk@rhein-zeitung.net; adkim=s; aspf=r
Found at
_dmarc.rhein-zeitung.de
External report address
mailto:helpdesk@rhein-zeitung.net (not authorized)
TagValueMeaning
vDMARC1Version
pquarantinePolicy
pct100Percentage of mail the policy applies to
ruamailto:helpdesk@rhein-zeitung.netAggregate report addresses
rufmailto:helpdesk@rhein-zeitung.netFailure report addresses
adkimsDKIM alignment (r = relaxed, s = strict)
aspfrSPF alignment (r = relaxed, s = strict)

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 100% of mail #18
    DMARC policy applies to all failing mail.
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:helpdesk@rhein-zeitung.net
  • ✓ Subdomain policy: quarantine #20
    Subdomains are covered by policy 'quarantine'.
  • !
    Report address not authorized
    These report addresses are in another domain that has not agreed to receive your reports, so receivers will not send them: mailto:helpdesk@rhein-zeitung.net (needs rhein-zeitung.de._report._dmarc.rhein-zeitung.net). Ask the report provider to publish the record, or check the address.
    #29

DKIM

fail

No keys found under the checked selectors

Found

Selectors
None found
_domainkey
NXDOMAIN

Checks

  • ✗
    No DKIM keys published
    _domainkey.rhein-zeitung.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
30mx-a.ktk.deA 82.115.96.242 AAAA 2a02:1628:0:c004::242mx-a.ktk.de ✓ mx-a.ktk.de ✓
30mx-b.ktk.deA 82.115.96.243 AAAA 2a02:1628:0:c004::243mx-b.ktk.de ✓ mx-b.ktk.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.
  • ✓ 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 4 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
mx-a.ktk.denone-
mx-b.ktk.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