SurfaceMap › d › dzif.de

dzif.de

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

Domain & DNS

fail

21 passed 2 warn 1 failed

Areas

iRegistration iDelegation ✗Nameservers iSOA !DNSSEC iRecords

Problems

  • ✗
    Nameservers not responding
    Nameservers · These addresses did not answer, so resolvers waste time on timeouts: ns1.idmkd.uni-frankfurt.de (2001:a38:1001:1480:141:2:148:30): read udp [2a01:4f8:1c1c:eebf::1]:44303->[2001:a38:1001:1480:141:2:148:30]:53: i/o timeout.
    #14
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.idmkd.uni-frankfurt.de: "Knot DNS 3.4.6"; ns2.idmcd.eu: "Knot DNS 3.4.6"; ns3.idmcd.de: "Knot DNS 3.4.6"; ns4.idmkd.uni-frankfurt.de: "Knot DNS 3.4.6". 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

Recent checks

✗

Full report

Domain & DNS report for dzif.de ›

Mail

fail

21 passed 4 warn 2 failed

Areas

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

Problems

  • ✗
    13 DNS lookups, over the limit of 10
    SPF · SPF record needs 13 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
  • !
    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: mx01.outlook.dehosted.net, mx02.outlook.dehosted.net
    #11
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: mail (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    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 dzif.de ›