kolping.de

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

SPF

fail

SPF record published

Found

Record
v=spf1 mx include:spf.protection.outlook.com include:_spf.jpberlin.de ip4:93.89.4.172 a:shop02.rackspeed-cloud.de a:shop03.rackspeed-cloud.de a:dedi5573.your-server.de include:oracleindustry.com include:_spf.zimpel.de ~all
DNS lookups
18 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✗
    18 DNS lookups, over the limit of 10
    SPF record needs 18 DNS lookups (including nested includes), more than the limit of 10. Receivers will return a permerror; reduce includes or flatten the record.
    #2
  • ✓ 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.kolping.de)

Found

Record
v=DMARC1; p=quarantine; pct=100; rua=mailto:68fee730@in.mailhardener.com; aspf=r; adkim=r; ruf=mailto:68fee730@in.mailhardener.com
Found at
_dmarc.kolping.de
External report address
mailto:68fee730@in.mailhardener.com (authorized)
TagValueMeaning
vDMARC1Version
pquarantinePolicy
pct100Percentage of mail the policy applies to
ruamailto:68fee730@in.mailhardener.comAggregate report addresses
rufmailto:68fee730@in.mailhardener.comFailure report addresses
adkimrDKIM 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:68fee730@in.mailhardener.com
  • ✓ Subdomain policy: quarantine #20
    Subdomains are covered by policy 'quarantine'.
  • ✓ External report addresses authorized #29
    Report addresses in other domains have published their authorization.

DKIM

warn

Selectors: default, selector1

Found

Selectors
default, selector1
_domainkey
NOERROR
SelectorKeyFlags
defaultRSA 1024 bits
selector1RSA 2048 bits

Checks

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

3 mail servers

Found

PriorityHostRecordsReverse DNS
10kolping-de.mail.protection.outlook.comA 52.101.68.29 A 52.101.185.114 A 52.101.68.25 A 52.101.73.155 AAAA 2a01:111:f403:ca48::a AAAA 2a01:111:f403:ca21::a AAAA 2a01:111:f403:ca3c::6 AAAA 2a01:111:f403:ca21::email-dbapr03cu00105.inbound.protection.outlook.com ✓ mail-zrxpr04cu00102.inbound.protection.outlook.com ✓ mail-db8pr02cu00101.inbound.protection.outlook.com ✓ mail-am7pr02cu00203.inbound.protection.outlook.com ✓ mail-miypr02cu00202.inbound.protection.outlook.com ✓ mail-maspr04cu00102.inbound.protection.outlook.com ✓ mail-zrxpr04cu00106.inbound.protection.outlook.com ✓ mail-matpr04cu00306.inbound.protection.outlook.com ✓
20mailout.kolping.deA 84.245.141.137mailout.kolping.de ✓
50mail3.kolping.deA 62.112.72.54mail3.kolping.de ✓

Checks

  • ✓ 3 MX records #9
    Found 3 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: mailout.kolping.de, mail3.kolping.de
    #11
  • ✓ Redundant MX hosts #12
    Found 3 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 3 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 10 MX addresss have a PTR record that resolves back to them.

TLS

warn

MTA-STS testing · TLS-RPT · DANE on 0 of 3 MX hosts

Found

MTA-STS record
v=STSv1; id=20260923150653
Policy URL
https://mta-sts.kolping.de/.well-known/mta-sts.txt
Mode
testing
Allowed MX
kolping-de.mail.protection.outlook.com, mailout.kolping.de, mail3.kolping.de
Max age
1209600 seconds
TLS-RPT record
v=TLSRPTv1; rua=mailto:68fee730@in.mailhardener.com

DANE (TLSA records)

MX hostTLSADNSSEC
kolping-de.mail.protection.outlook.comnone-
mailout.kolping.denone-
mail3.kolping.denone-

Checks

  • ✓ Record published #32
    MTA-STS record found with id 20260923150653.
  • !
    Policy in testing mode
    With mode: testing, senders only report TLS problems (via TLS-RPT) and still deliver without TLS. Switch to mode: enforce once reports are clean.
    #33
  • ✓ All MX hosts covered #34
    Every MX host matches an mx: line of the MTA-STS policy.
  • ✓ Reports enabled #35
    TLS reports are sent to: mailto:68fee730@in.mailhardener.com
  • 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