SurfaceMap › f › fit-for-travel.de

fit-for-travel.de

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

Domain & DNS

warn

19 passed 3 warn 0 failed

Areas

iRegistration iDelegation !Nameservers iSOA !DNSSEC !Records

Problems

  • !
    No EDNS
    Nameservers · These nameservers don't support EDNS(0), needed for DNSSEC and answers larger than 512 bytes: c1-160.akashield.net (92.123.94.160), c1-160.akashield.net (2600:14c0:6::a0), c2-160.akashield.net (92.123.95.160), c2-160.akashield.net (2600:14c0:7::a0).
    #20
  • !
    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 (20s), AAAA (20s), NS (2m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1d and in the zone 2m; resolvers may use either.
    #32

Recent checks

!

Full report

Domain & DNS report for fit-for-travel.de ›

Mail

fail

12 passed 5 warn 2 failed

Areas

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

Problems

  • ✗
    No SPF record
    SPF · No SPF record was found for this domain. SPF is important for preventing email spoofing. Add an SPF record to specify which servers are authorized to send email for your domain.
    #6
  • ✗
    No DKIM keys published
    DKIM · _domainkey.fit-for-travel.de does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.
    #7
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Hosts without IP addresses
    MX · The following MX hosts could not be resolved to IP addresses: zimbra.xmachina.de
    #10
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: zimbra.xmachina.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 fit-for-travel.de ›