SurfaceMap › s › someserver.de

someserver.de

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

Domain & DNS

warn

22 passed 3 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.someserver.de: "PowerDNS Authoritative Server 4.7.3 (built Dec 8 2022 19:07:39 by root@9ef70fa1a052)"; ns3.someserver.de: "PowerDNS Authoritative Server 4.1.8 (built Mar 22 2019 11:50:40 by root@effe6ebfcade)". Hide or replace the version string.
    #17
  • !
    Serials differ
    SOA · The nameservers serve different versions of the zone: 2025020202 on ns1.someserver.de (116.202.193.223), ns1.someserver.de (2a01:4f8:241:f700:c8a4:bfff:fe09:6f56), ns3.someserver.de (94.130.46.206), ns3.someserver.de (2a01:4f8:10b:1aa2::5e82:2ece); 2026102201 on ns2.someserver.de (164.68.125.157), ns2.someserver.de (2a02:c207:3004:2982::1). This is normal for a few minutes after a change; if it lasts, zone transfers to the secondaries are failing.
    #22
  • !
    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 someserver.de ›

Mail

fail

16 passed 3 warn 2 failed

Areas

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

Problems

  • ✗
    No DMARC record
    DMARC · No DMARC record was found for this domain. DMARC is essential for preventing email spoofing. Add a DMARC record with p=reject or at least p=quarantine.
    #5
  • ✗
    No DKIM keys published
    DKIM · _domainkey.someserver.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
  • !
    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 someserver.de ›