SurfaceMap › f › fidor.de

fidor.de

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

Domain & DNS

warn

19 passed 3 warn 0 failed

Areas

iRegistration !Delegation !Nameservers ✓SOA !DNSSEC iRecords

Problems

  • !
    Nameservers in one network
    Delegation · all IPv4 addresses are in 212.223.44.0/24; all IPv6 addresses are in 2a02:708::/48. A single network failure takes all nameservers down; RFC 2182 recommends topologically separate networks (anycast setups are an exception).
    #10
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns11.nameserver.de: "PowerDNS Authoritative Server 4.7.3"; ns12.nameserver.de: "PowerDNS Authoritative Server 4.7.3". Hide or replace the version string.
    #17
  • !
    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 fidor.de ›

Mail

fail

0 passed 3 warn 2 failed

Areas

✗SPF ✗DMARC !DKIM !DNSSEC !MX 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 SPF record
    SPF · No SPF record was found for this domain. SPF is important for preventing email spoofing. Add an SPF record to specify which servers are authorized to send email for your domain.
    #6
  • !
    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
  • !
    Not protected against spoofing
    MX · The domain publishes a null MX. If it does not send mail, publish SPF "v=spf1 -all" and DMARC p=reject so nobody can send mail as this domain.
    #28

Recent checks

✗

Full report

Mail report for fidor.de ›