SurfaceMap › u › u-paris10.fr

u-paris10.fr

Checked 2026-10-22 05:33 UTC · first added 2026-10-21
✗Problems found Score 57 of 100

Domain & DNS

fail

22 passed 4 warn 1 failed

Areas

iRegistration !Delegation ✗Nameservers ✓SOA !DNSSEC iRecords

Problems

  • ✗
    Zone transfer allowed
    Nameservers · These nameservers send the complete zone to anyone who asks (AXFR), exposing all host names: ns1.univ-poitiers.fr (195.220.223.111): 9132 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 at the parent: remus.u-paris10.fr, romulus.u-paris10.fr, thetis.univ-poitiers.fr; only in the zone: ns1.univ-poitiers.fr, remus.parisnanterre.fr, romulus.parisnanterre.fr. dns.ipsl.jussieu.fr, ns1.univ-poitiers.fr, remus.parisnanterre.fr, remus.u-paris10.fr, romulus.parisnanterre.fr, romulus.u-paris10.fr, thetis.univ-poitiers.fr report NS dns.ipsl.jussieu.fr ns1.univ-poitiers.fr remus.parisnanterre.fr romulus.parisnanterre.fr.
    #7
  • !
    No IPv6
    Delegation · None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13
  • !
    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"; remus.parisnanterre.fr: "9.8.2rc1-RedHat-9.8.2-0.68.rc1.el6_10.8"; remus.u-paris10.fr: "9.8.2rc1-RedHat-9.8.2-0.68.rc1.el6_10.8"; romulus.parisnanterre.fr: "9.8.2rc1-RedHat-9.8.2-0.68.rc1.el6_10.8"; romulus.u-paris10.fr: "9.8.2rc1-RedHat-9.8.2-0.68.rc1.el6_10.8". 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 u-paris10.fr ›

Mail

warn

22 passed 7 warn 0 failed

Areas

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

Problems

  • !
    Policy: quarantine
    DMARC · DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.
    #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: smtpinpp.u-paris10.fr
    #11
  • !
    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), google (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    Report address not authorized
    DMARC · These report addresses are in another domain that has not agreed to receive your reports, so receivers will not send them: mailto:postmaster@parisnanterre.fr (needs u-paris10.fr._report._dmarc.parisnanterre.fr). Ask the report provider to publish the record, or check the address.
    #29
  • !
    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 u-paris10.fr ›