SurfaceMap › l › ls2n.fr

ls2n.fr

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

Domain & DNS

fail

20 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: vps-unicaen.unicaen.fr (51.210.107.144): REFUSED, authoritative=false; vps-unicaen.unicaen.fr (2001:41d0:304:200::14df): 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: vps-unicaen.unicaen.fr (51.210.107.144): ; vps-unicaen.unicaen.fr (2001:41d0:304:200::14df): .
    #19
  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only in the zone: ipam-dns2-fr.univ-nantes.fr, vps-unicaen.unicaen.fr. dns1.univ-nantes.fr, dns2.univ-nantes.fr, ipam-dns2-fr.univ-nantes.fr report NS dns1.univ-nantes.fr dns2.univ-nantes.fr ipam-dns2-fr.univ-nantes.fr vps-unicaen.unicaen.fr.
    #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 ls2n.fr ›

Mail

fail

21 passed 5 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
  • !
    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
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: mail (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    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 ls2n.fr ›