SurfaceMap › o › oeko.de

oeko.de

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

Domain & DNS

warn

21 passed 4 warn 0 failed

Areas

iRegistration !Delegation !Nameservers !SOA !DNSSEC iRecords

Problems

  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only in the zone: dns-b2.oeko.de, dns-da1.oeko.de. dns-b2.oeko.de, dns-da1.oeko.de, ns2.oeko.de, pns.dtag.de, secondary006.dtag.net report NS dns-b2.oeko.de dns-da1.oeko.de ns2.oeko.de pns.dtag.de secondary006.dtag.net.
    #7
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: dns-b2.oeko.de: "9.18.49-1~deb12u2-Debian"; dns-da1.oeko.de: "9.18.49-1~deb12u2-Debian"; ns2.oeko.de: "9.18.49-1~deb12u2-Debian". Hide or replace the version string.
    #17
  • !
    Unusual SOA timers
    SOA · retry 1h should be shorter than refresh 1h. Current values: refresh 1h, retry 1h, expire 28d, negative TTL 2h.
    #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 oeko.de ›

Mail

fail

20 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
  • !
    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
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: mxgateda.oeko.de, mxgateb.oeko.de, mxgatefr.oeko.de
    #11
  • !
    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 oeko.de ›