SurfaceMap › i › in2p3.fr

in2p3.fr

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

Domain & DNS

fail

24 passed 3 warn 1 failed

Areas

iRegistration !Delegation ✗Nameservers ✓SOA !DNSSEC ✓Records

Problems

  • ✗
    Zone transfer allowed
    Nameservers · These nameservers send the complete zone to anyone who asks (AXFR), exposing all host names: adminlinuxs.ijclab.in2p3.fr (134.158.88.78): 42534 records; adminlinuxs.ijclab.in2p3.fr (2001:660:3024:101:134:158:79:78): 42534 records. Restrict zone transfers to your secondary servers.
    #18
  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only in the zone: adminlinuxs.ijclab.in2p3.fr. adminlinuxs.ijclab.in2p3.fr, ccpntc3.in2p3.fr, ccpnvx.in2p3.fr, dns.ens-lyon.fr, ext-dns-2.cern.ch, ns2.nic.fr report NS adminlinuxs.ijclab.in2p3.fr ccpntc3.in2p3.fr ccpnvx.in2p3.fr dns.ens-lyon.fr ext-dns-2.cern.ch ns2.nic.fr.
    #7
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: adminlinuxs.ijclab.in2p3.fr: "9.11.4-P2-RedHat-9.11.4-26.P2.el7_9.4"; dns.ens-lyon.fr: "9.18.49-1~deb12u2-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 in2p3.fr ›

Mail

fail

19 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
  • !
    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.in2p3.fr, mx2.in2p3.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 in2p3.fr ›