SurfaceMap › f › fes.de

fes.de

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

Domain & DNS

fail

17 passed 2 warn 2 failed

Areas

iRegistration !Delegation ✗Nameservers ✓SOA !DNSSEC iRecords

Problems

  • ✗
    Lame delegation
    Nameservers · These nameservers don't answer authoritatively for the zone, so resolvers ignore them: pns.dtag.de (194.25.0.125): REFUSED, authoritative=false; pns.dtag.de (2003:40:8000::100): REFUSED, authoritative=false.
    #15
  • ✗
    No DNS over TCP
    Nameservers · DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: pns.dtag.de (194.25.0.125): ; pns.dtag.de (2003:40:8000::100): .
    #19
  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only in the zone: pns.dtag.de. ns.fes.de, ns2.fes.de report NS ns.fes.de ns2.fes.de pns.dtag.de.
    #7
  • !
    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 fes.de ›

Mail

warn

20 passed 6 warn 0 failed

Areas

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

Problems

  • !
    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: mail1.fes.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
  • !
    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
  • !
    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 fes.de ›