SurfaceMap › v › ville-meulan.fr

ville-meulan.fr

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

Domain & DNS

fail

24 passed 3 warn 2 failed

Areas

iRegistration !Delegation ✗Nameservers ✓SOA !DNSSEC iRecords

Problems

  • ✗
    Lame delegation
    Nameservers · These nameservers don't answer authoritatively for the zone, so resolvers ignore them: ns1.bdm.microsoftonline.com (13.107.236.208): REFUSED, authoritative=false; ns1.bdm.microsoftonline.com (2603:1061:0:700::d0): REFUSED, authoritative=false; ns2.bdm.microsoftonline.com (150.171.21.208): REFUSED, authoritative=false; ns2.bdm.microsoftonline.com (2620:1ec:8ec:700::d0): REFUSED, authoritative=false; ns3.bdm.microsoftonline.com (204.14.183.208): REFUSED, authoritative=false; ns3.bdm.microsoftonline.com (2a01:111:4000:700::d0): REFUSED, authoritative=false; ns4.bdm.microsoftonline.com (208.84.5.208): REFUSED, authoritative=false; ns4.bdm.microsoftonline.com (2620:1ec:bda:700::d0): REFUSED, authoritative=false.
    #15
  • ✗
    No DNS over TCP
    Nameservers · DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: ns1.bdm.microsoftonline.com (13.107.236.208): ; ns1.bdm.microsoftonline.com (2603:1061:0:700::d0): ; ns2.bdm.microsoftonline.com (150.171.21.208): ; ns2.bdm.microsoftonline.com (2620:1ec:8ec:700::d0): ; ns3.bdm.microsoftonline.com (204.14.183.208): ; ns3.bdm.microsoftonline.com (2a01:111:4000:700::d0): ; ns4.bdm.microsoftonline.com (208.84.5.208): ; ns4.bdm.microsoftonline.com (2620:1ec:bda:700::d0): .
    #19
  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com, ns3.bdm.microsoftonline.com, ns4.bdm.microsoftonline.com. dns112.ovh.net, ns112.ovh.net report NS dns112.ovh.net ns112.ovh.net.
    #7
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns4.bdm.microsoftonline.com: "Knot DNS 3.1.2.1770717641.d6b376aff". 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 ville-meulan.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 ville-meulan.fr ›