SurfaceMap › i › inserm.fr

inserm.fr

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

Domain & DNS

fail

22 passed 2 warn 2 failed

Areas

iRegistration ✗Delegation ✗Nameservers ✓SOA !DNSSEC ✓Records

Problems

  • ✗
    Nameserver names don't resolve
    Delegation · These nameservers have no A or AAAA record, so they can't be reached (lame delegation): ns1.genoscope.cns.fr.
    #9
  • ✗
    Nameservers not responding
    Nameservers · These addresses did not answer, so resolvers waste time on timeouts: dns.lyon.inserm.fr (194.57.163.154): read udp 46.225.38.91:53723->194.57.163.154:53: i/o timeout.
    #14
  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: dns.lyon.inserm.fr, ns1.genoscope.cns.fr; only in the zone: ns3.inserm.fr. ns1.inserm.fr, ns2.inserm.fr, ns3.inserm.fr report NS ns1.inserm.fr ns2.inserm.fr ns3.inserm.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 inserm.fr ›

Mail

fail

22 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
  • !
    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: ins-par6-b11-fml1.inserm.fr, ins-mly-a317-fml1.inserm.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 inserm.fr ›