SurfaceMap › b › boerse-frankfurt.de

boerse-frankfurt.de

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

Domain & DNS

fail

23 passed 2 warn 1 failed

Areas

iRegistration ✓Delegation ✗Nameservers !SOA !DNSSEC iRecords

Problems

  • ✗
    Nameservers not responding
    Nameservers · These addresses did not answer, so resolvers waste time on timeouts: a.dbgdns.lu (2a03:98c0:14:2504::1111:12): read udp [2a01:4f8:1c1c:eebf::1]:45594->[2a03:98c0:14:2504::1111:12]:53: i/o timeout; b.dbgdns.de (2a03:98c0:14:2504::2222:44): read udp [2a01:4f8:1c1c:eebf::1]:54527->[2a03:98c0:14:2504::2222:44]:53: i/o timeout.
    #14
  • !
    Unusual SOA timers
    SOA · negative caching TTL (minimum) 3m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 4h, retry 1h, expire 14d, negative TTL 3m.
    #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

Recent checks

✗

Full report

Domain & DNS report for boerse-frankfurt.de ›

Mail

fail

21 passed 5 warn 1 failed

Areas

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

Problems

  • ✗
    No DKIM keys published
    DKIM · _domainkey.boerse-frankfurt.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 IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: mail16.deutsche-boerse.com, mail17.deutsche-boerse.com, mail14.clearstream.com, mail15.clearstream.com
    #11
  • !
    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
  • !
    Report address not authorized
    DMARC · These report addresses are in another domain that has not agreed to receive your reports, so receivers will not send them: mailto:email.security@clearstream.com (needs boerse-frankfurt.de._report._dmarc.clearstream.com). Ask the report provider to publish the record, or check the address.
    #29
  • !
    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 boerse-frankfurt.de ›