SurfaceMap › k › kiel-sailing-city.de

kiel-sailing-city.de

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

Domain & DNS

warn

19 passed 3 warn 0 failed

Areas

iRegistration iDelegation !Nameservers ✓SOA !DNSSEC !Records

Problems

  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.addix.de: "PowerDNS Authoritative Server 4.1.14"; ns2.addix.de: "PowerDNS Authoritative Server 4.1.14". Hide or replace the version string.
    #17
  • !
    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), NS (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1d and in the zone 1m; resolvers may use either.
    #32

Recent checks

!

Full report

Domain & DNS report for kiel-sailing-city.de ›

Mail

fail

21 passed 5 warn 1 failed

Areas

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

Problems

  • ✗
    11 DNS lookups, over the limit of 10
    SPF · SPF record needs 11 DNS lookups (including nested includes), more than the limit of 10. Receivers will return a permerror; reduce includes or flatten the record.
    #2
  • !
    No key under common selectors
    DKIM · The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.
    #7
  • !
    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: mail.kiel-sailing-city.de
    #11
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    Not configured
    TLS · 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

Recent checks

✗

Full report

Mail report for kiel-sailing-city.de ›