SurfaceMap › k › ksc.de

ksc.de

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

Domain & DNS

warn

22 passed 3 warn 0 failed

Areas

iRegistration ✓Delegation ✓Nameservers !SOA !DNSSEC !Records

Problems

  • !
    Unusual SOA timers
    SOA · refresh 6m is outside 20m–1d; expire 6m is shorter than 7d; secondaries stop answering too soon when the primary is down; expire 6m must be longer than refresh + retry. Current values: refresh 6m, retry 3m, expire 6m, negative TTL 6m.
    #23
  • !
    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). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1d and in the zone 6m; resolvers may use either.
    #32

Recent checks

!

Full report

Domain & DNS report for ksc.de ›

Mail

fail

17 passed 5 warn 2 failed

Areas

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

Problems

  • ✗
    17 DNS lookups, over the limit of 10
    SPF · SPF record needs 17 DNS lookups (including nested includes), more than the limit of 10. Receivers will return a permerror; reduce includes or flatten the record.
    #2
  • ✗
    Policy: none (monitoring only)
    DMARC · DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.
    #4
  • !
    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
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    No aggregate reports (rua)
    DMARC · DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...
    #19
  • !
    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 ksc.de ›