SurfaceMap › v › vetagro-sup.fr

vetagro-sup.fr

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

Domain & DNS

fail

20 passed 3 warn 3 failed

Areas

iRegistration ✗Delegation ✗Nameservers ✓SOA !DNSSEC ✓Records

Problems

  • ✗
    Nameserver names don't resolve
    Delegation · These nameservers have no A or AAAA record, so they can't be reached (lame delegation): agrodns.vas.lan.
    #9
  • ✗
    Nameservers not responding
    Nameservers · These addresses did not answer, so resolvers waste time on timeouts: agrodns.vetagro-sup.fr (194.214.164.25): read udp 46.225.38.91:37159->194.214.164.25:53: i/o timeout; curry.vetagro-sup.fr (193.55.119.71): read udp 46.225.38.91:58976->193.55.119.71:53: i/o timeout.
    #14
  • ✗
    Zone transfer allowed
    Nameservers · These nameservers send the complete zone to anyone who asks (AXFR), exposing all host names: dns.univ-lyon1.fr (134.214.100.6): 216 records; dns.univ-lyon1.fr (2001:660:5001:100::6): 216 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: agrodns.vas.lan, agrodns.vetagro-sup.fr, curry.vetagro-sup.fr. dns.univ-lyon1.fr, jaune.vetagro-sup.fr report NS agrodns.vas.lan agrodns.vetagro-sup.fr curry.vetagro-sup.fr dns.univ-lyon1.fr jaune.vetagro-sup.fr.
    #7
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: jaune.vetagro-sup.fr: "9.11.36-RedHat-9.11.36-16.el8_10.15". 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 vetagro-sup.fr ›

Mail

fail

22 passed 4 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
  • !
    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: 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 vetagro-sup.fr ›