SurfaceMap › k › kolping.de

kolping.de

Checked 2026-10-21 23:10 UTC · first added 2026-10-21
✗Problems found Score 69 of 100

Domain & DNS

warn

22 passed 2 warn 0 failed

Areas

iRegistration iDelegation iNameservers ✓SOA !DNSSEC !Records

Problems

  • !
    Not signed
    DNSSEC · The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.
    #27
  • !
    Very low TTLs
    Records · These records have a TTL below 5m, causing extra queries and slower lookups: A (1m), MX (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1d and in the zone 12h; resolvers may use either.
    #32

Recent checks

!

Full report

Domain & DNS report for kolping.de ›

Mail

fail

26 passed 5 warn 1 failed

Areas

✗SPF !DMARC !DKIM !DNSSEC !MX !TLS iBIMI

Problems

  • ✗
    18 DNS lookups, over the limit of 10
    SPF · 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
  • !
    Policy: quarantine
    DMARC · DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.
    #4
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: mailout.kolping.de, mail3.kolping.de
    #11
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: default (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    Policy in testing mode
    TLS · 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

Recent checks

✗

Full report

Mail report for kolping.de ›