SurfaceMap › u › uphf.fr

uphf.fr

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

Domain & DNS

fail

17 passed 5 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: squidpumvm.uphf.fr (195.221.189.78): read udp 46.225.38.91:40723->195.221.189.78:53: i/o timeout.
    #14
  • ✗
    Zone transfer allowed
    Nameservers · These nameservers send the complete zone to anyone who asks (AXFR), exposing all host names: pulsar.univ-valenciennes.fr (193.50.192.1): 13464 records; pulsar.uphf.fr (193.50.192.1): 13464 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: pulsar.univ-valenciennes.fr, titan.univ-valenciennes.fr; only in the zone: proxy1-rech.uphf.fr, pulsar.uphf.fr, squidpumvm.uphf.fr, titan.uphf.fr. proxy1-rech.uphf.fr, pulsar.univ-valenciennes.fr, pulsar.uphf.fr, titan.univ-valenciennes.fr, titan.uphf.fr report NS proxy1-rech.uphf.fr pulsar.uphf.fr squidpumvm.uphf.fr titan.uphf.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: proxy1-rech.uphf.fr: "9.20.21-1~deb13u1-Debian"; pulsar.univ-valenciennes.fr: "9.9.5-9+deb8u15-Debian"; pulsar.uphf.fr: "9.9.5-9+deb8u15-Debian"; titan.univ-valenciennes.fr: "9.20.23-1~deb13u1-Debian"; titan.uphf.fr: "9.20.23-1~deb13u1-Debian". Hide or replace the version string.
    #17
  • !
    Unusual SOA timers
    SOA · negative caching TTL (minimum) 2d is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 6h, retry 1h, expire 1000h, negative TTL 2d.
    #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 uphf.fr ›

Mail

warn

24 passed 5 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: mx1.relay.renater.fr, mx2.relay.renater.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 uphf.fr ›