SurfaceMap › m › msh-lse.fr

msh-lse.fr

Checked 2026-10-22 04:26 UTC · first added 2026-10-21
✗Problems found Score 69 of 100

Domain & DNS

warn

21 passed 3 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 at the parent: docsrvr.msh-lse.fr; only in the zone: docsrvr.ish-lyon.cnrs.fr, ns4.cnrs.fr. diogene.univ-lyon2.fr, docsrvr.ish-lyon.cnrs.fr, docsrvr.msh-lse.fr, ns4.cnrs.fr report NS diogene.univ-lyon2.fr docsrvr.ish-lyon.cnrs.fr ns4.cnrs.fr.
    #7
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: diogene.univ-lyon2.fr: "9.16.23-RH"; docsrvr.ish-lyon.cnrs.fr: "9.18.39-0ubuntu0.24.04.8-Ubuntu"; docsrvr.msh-lse.fr: "9.18.39-0ubuntu0.24.04.8-Ubuntu". 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 msh-lse.fr ›

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: mx1.relay.renater.fr, mx2.relay.renater.fr
    #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 msh-lse.fr ›