SurfaceMap › h › hosteurope.de

hosteurope.de

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

Domain & DNS

fail

18 passed 3 warn 1 failed

Areas

iRegistration iDelegation ✗Nameservers ✓SOA !DNSSEC !Records

Problems

  • ✗
    Nameservers not responding
    Nameservers · These addresses did not answer, so resolvers waste time on timeouts: dns.hosteurope.de (2a01:488::35): read udp [2a01:4f8:1c1c:eebf::1]:39479->[2a01:488::35]:53: i/o timeout; dns2.hosteurope.de (2a01:488::53): read udp [2a01:4f8:1c1c:eebf::1]:49906->[2a01:488::53]:53: i/o timeout.
    #14
  • !
    No EDNS
    Nameservers · These nameservers don't support EDNS(0), needed for DNSSEC and answers larger than 512 bytes: dns.hosteurope.de (80.237.128.156), dns2.hosteurope.de (80.237.136.144).
    #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 (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1d and in the zone 10m1s; resolvers may use either.
    #32

Recent checks

✗

Full report

Domain & DNS report for hosteurope.de ›

Mail

fail

22 passed 4 warn 1 failed

Areas

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

Problems

  • ✗
    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: mx0.hosteurope.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 hosteurope.de ›