SurfaceMap › c › chu-montpellier.fr

chu-montpellier.fr

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

Domain & DNS

fail

19 passed 4 warn 2 failed

Areas

iRegistration !Delegation ✗Nameservers !SOA !DNSSEC iRecords

Problems

  • ✗
    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:52028->194.57.163.154:53: i/o timeout.
    #14
  • ✗
    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: dns1.chu-montpellier.fr (195.83.227.126): dial tcp 195.83.227.126:53: i/o timeout; dns2.chu-montpellier.fr (195.83.227.127): dial tcp 195.83.227.127:53: i/o timeout.
    #19
  • !
    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; only in the zone: dns2.chu-montpellier.fr. dns1.chu-montpellier.fr, dns2.chu-montpellier.fr report NS dns1.chu-montpellier.fr dns2.chu-montpellier.fr.
    #7
  • !
    No IPv6
    Delegation · None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13
  • !
    Unusual SOA timers
    SOA · expire 1d is shorter than 7d; secondaries stop answering too soon when the primary is down. Current values: refresh 1h, retry 10m, expire 1d, negative TTL 1h.
    #23
  • !
    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 chu-montpellier.fr ›

Mail

warn

25 passed 4 warn 0 failed

Areas

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

Problems

  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: default (1024 bits), selector1 (1024 bits), selector2 (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 chu-montpellier.fr ›