SurfaceMap › i › ipsl.fr

ipsl.fr

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

Domain & DNS

fail

23 passed 2 warn 1 failed

Areas

iRegistration iDelegation ✗Nameservers ✓SOA !DNSSEC iRecords

Problems

  • ✗
    Zone transfer allowed
    Nameservers · These nameservers send the complete zone to anyone who asks (AXFR), exposing all host names: balsa.ipsl.fr (194.254.40.1): 345 records; balsa.ipsl.fr (2001:660:3023:1::1): 345 records. Restrict zone transfers to your secondary servers.
    #18
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: dns.ipsl.jussieu.fr: "9.8.2rc1-RedHat-9.8.2-0.68.rc1.el6_10.8"; hermes.cnrs-gif.fr: "9.20.29-1~deb13u1-Debian". 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 ipsl.fr ›

Mail

fail

17 passed 6 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, mxa.relay.renater.fr, mxb.relay.renater.fr, mxc.relay.renater.fr, mxd.relay.renater.fr
    #11
  • !
    More than 5 MX records
    MX · Found 6 MX records, which is more than the recommended maximum of 5. Too many MX records may indicate a misconfiguration.
    #13
  • !
    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 ipsl.fr ›