SurfaceMap › i › iserv.de

iserv.de

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

Domain & DNS

warn

21 passed 4 warn 0 failed

Areas

iRegistration iDelegation !Nameservers !SOA !DNSSEC iRecords

Problems

  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.iserv.eu: "9.18.49-1~deb12u2-Debian"; ns2.iserv.eu: "9.18.49-1~deb12u2-Debian"; ns3.iserv.eu: "9.18.49-1~deb12u2-Debian"; ns4.iserv.eu: "9.18.49-1~deb12u2-Debian". Hide or replace the version string.
    #17
  • !
    Serials differ
    SOA · The nameservers serve different versions of the zone: 371591958 on ns1.iserv.eu (116.202.2.219), ns1.iserv.eu (2a01:4f8:c01f:42::1), ns2.iserv.eu (91.204.44.133), ns2.iserv.eu (2a03:4000:20:19b::1), ns3.iserv.eu (116.203.7.41), ns3.iserv.eu (2a01:4f8:1c0c:8111::1); 371591959 on ns4.iserv.eu (188.68.45.203), ns4.iserv.eu (2a03:4000:20:19e::1). This is normal for a few minutes after a change; if it lasts, zone transfers to the secondaries are failing.
    #22
  • !
    Unusual SOA timers
    SOA · negative caching TTL (minimum) 1m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 1d, retry 3h, expire 1000h, negative TTL 1m.
    #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 iserv.de ›

Mail

fail

17 passed 6 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
  • !
    Ends with ?all (neutral)
    SPF · SPF record uses ?all (neutral), which gives no protection against unauthorized senders. Use -all or ~all instead.
    #3
  • !
    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
  • !
    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
  • !
    Addresses without reverse DNS
    MX · These MX addresses have no PTR record, which many receivers treat as a spam signal: 217.13.72.70 (iserv.iserv.eu), 2a01:4f8:c2c:4863::1 (offline.iserv.eu). Ask your hosting provider to set one.
    #30
  • !
    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 iserv.de ›