ville-meulan.fr

Checked 22 October 2026, 05:50 UTC · via 8.8.8.8
✗Problems found
24 passed 3 warnings 2 failed 2 info

Registration

info

.fr country-code · OVH · expires 2028-10-27

Found

TLD
.fr (country-code)
ICANN policies apply
no
Registrar
OVH
Registered
25 February 2004
Last changed
29 September 2026
Expires
27 October 2028
Status
client transfer prohibited, client delete prohibited
Registry nameservers
dns112.ovh.net, ns1.bdm.microsoftonline.com, ns112.ovh.net, ns2.bdm.microsoftonline.com, ns3.bdm.microsoftonline.com, ns4.bdm.microsoftonline.com
RDAP server
https://rdap.nic.fr/

Checks

  • i
    .fr is a country-code TLD (ccTLD)
    Country-code TLD: governed by its local registry under national policy, not by an ICANN contract. Registrar accreditation, dispute resolution and RDAP/WHOIS rules are set by the registry.
    #1
  • ✓ TLD delegated and signed #2
    .fr is delegated in the root zone and DNSSEC-signed.
  • ✓ Expires on 2028-10-27 #3
    The registration is valid until 2028-10-27 (736 days).
  • ✓ Transfer locked #4
    Registry status: client transfer prohibited, client delete prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

warn

dns112.ovh.net, ns1.bdm.microsoftonline.com, ns112.ovh.net, ns2.bdm.microsoftonline.com, ns3.bdm.microsoftonline.com, ns4.bdm.microsoftonline.com

Found

Parent zone
fr
Delegation from
d.nic.fr (194.0.9.1)
NS at the parent
dns112.ovh.net, ns1.bdm.microsoftonline.com, ns112.ovh.net, ns2.bdm.microsoftonline.com, ns3.bdm.microsoftonline.com, ns4.bdm.microsoftonline.com
NS in the zone
dns112.ovh.net, ns112.ovh.net
NameserverAddressesNetwork (AS)Glue
dns112.ovh.net5.196.45.209 2001:41d0:d01:600::2AS16276 OVH - OVH SAS, FR AS16276 OVH - OVH SAS, FR-
ns1.bdm.microsoftonline.com (parent only)13.107.236.208 2603:1061:0:700::d0AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-
ns112.ovh.net5.135.80.109 2001:41d0:b01::2AS16276 OVH - OVH SAS, FR AS16276 OVH - OVH SAS, FR-
ns2.bdm.microsoftonline.com (parent only)150.171.21.208 2620:1ec:8ec:700::d0AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-
ns3.bdm.microsoftonline.com (parent only)204.14.183.208 2a01:111:4000:700::d0AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-
ns4.bdm.microsoftonline.com (parent only)208.84.5.208 2620:1ec:bda:700::d0AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-

Checks

  • ✓ 6 nameservers #6
    Delegated to dns112.ovh.net, ns1.bdm.microsoftonline.com, ns112.ovh.net, ns2.bdm.microsoftonline.com, ns3.bdm.microsoftonline.com, ns4.bdm.microsoftonline.com.
  • !
    NS sets differ
    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
  • ✓ No glue needed #8
    All nameservers are outside the zone, so no glue records are needed.
  • ✓ All names resolve #9
    Every nameserver name has an address and is not an alias.
  • ✓ Nameservers in different networks #10
    The nameservers are spread over 6 IPv4 /24s and 6 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS16276 (OVH - OVH SAS, FR): 4 addresses; AS8075 (MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US): 8 addresses.
  • ✓ Nameserver names under 2 TLDs #12
    Nameserver names use the TLDs .com, .net.
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

fail

4 of 12 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
dns112.ovh.net 5.196.45.209NOERROR, 18 ms, authoritativenoyes / yesrefused-
dns112.ovh.net 2001:41d0:d01:600::2NOERROR, 17 ms, authoritativenoyes / yesrefused-
ns1.bdm.microsoftonline.com 13.107.236.208REFUSED, 6 ms, NOT authoritativenono / yesrefused-
ns1.bdm.microsoftonline.com 2603:1061:0:700::d0REFUSED, 7 ms, NOT authoritativenono / yesrefused-
ns112.ovh.net 5.135.80.109NOERROR, 15 ms, authoritativenoyes / yesrefused-
ns112.ovh.net 2001:41d0:b01::2NOERROR, 15 ms, authoritativenoyes / yesrefused-
ns2.bdm.microsoftonline.com 150.171.21.208REFUSED, 4 ms, NOT authoritativenono / yesrefused-
ns2.bdm.microsoftonline.com 2620:1ec:8ec:700::d0REFUSED, 6 ms, NOT authoritativenono / yesrefused-
ns3.bdm.microsoftonline.com 204.14.183.208REFUSED, 7 ms, NOT authoritativenono / yesrefused-
ns3.bdm.microsoftonline.com 2a01:111:4000:700::d0REFUSED, 6 ms, NOT authoritativenono / yesrefused-
ns4.bdm.microsoftonline.com 208.84.5.208REFUSED, 9 ms, NOT authoritativenono / yesrefusedKnot DNS 3.1.2.1770717641.d6b376aff
ns4.bdm.microsoftonline.com 2620:1ec:bda:700::d0REFUSED, 9 ms, NOT authoritativenono / yesrefused-

Checks

  • ✓ All respond #14
    All 12 nameserver addresses answered.
  • ✗
    Lame delegation
    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 recursion #16
    The nameservers do not answer recursive queries for other domains.
  • !
    Software version disclosed
    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
  • ✓ Zone transfers refused #18
    No nameserver allows a zone transfer to the public.
  • ✗
    No DNS over TCP
    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
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

pass

serial 2025083001 · primary dns112.ovh.net

Found

Primary (MNAME)
dns112.ovh.net
Contact (RNAME)
tech.ovh.net
Serial
2025083001
Refresh / retry
86400 s / 3600 s
Expire
3600000 s
Negative TTL
300 s

Serial per nameserver

NameserverSerial
dns112.ovh.net (5.196.45.209)2025083001
dns112.ovh.net (2001:41d0:d01:600::2)2025083001
ns112.ovh.net (5.135.80.109)2025083001
ns112.ovh.net (2001:41d0:b01::2)2025083001

Checks

  • ✓ Serial 2025083001 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1d, retry 1h, expire 1000h, negative TTL 5m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver dns112.ovh.net is one of the listed nameservers.
  • ✓ Contact tech@ovh.net #25
    The SOA RNAME tech.ovh.net means tech@ovh.net.
  • ✓ Date-based serial #26
    The serial 2025083001 follows the YYYYMMDDnn convention (2025-08-30).

DNSSEC

warn

Not signed

Found

Validated by resolver
no

Checks

  • !
    Not signed
    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

Records

info

9 records at the apex

Found

Read from
5.196.45.209:53
TypeValueTTL
SOAdns112.ovh.net. tech.ovh.net. 2025083001 86400 3600 3600000 3003600
NSns112.ovh.net.3600
NSdns112.ovh.net.3600
A92.112.192.683600
MX0 villemeulan-fr01c.mail.protection.outlook.com.3600
TXT"v=spf1 include:mx.ovh.com a include:spf.protection.outlook.com -all"3600
TXT"MS=ms86270707"3600
TXT"1|www.ville-meulan.fr"3600
TXT"brevo-code:03ef01ca01df45029fae24c0e3b3dcb0"3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 1h, MX 1h, NS 1h.
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • ✓ No wildcard #34
    Names that don't exist return NXDOMAIN.
  • i
    No CAA records
    Without CAA records any certificate authority may issue certificates for this domain. A CAA record limits issuance to the CAs you use.
    #35