ville-paimpol.fr

.fr country-code · OVH · expires 2026-11-06

Found

TLD

.fr (country-code)

ICANN policies apply

no

Registrar

OVH

Registered

20 June 2000

Last changed

31 December 2025

Expires

6 November 2026

Status

active

Registry nameservers

ns1.creasrv.net, ns2.creasrv.net

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 in 15 days

  The registration expires on 2026-11-06. Make sure it is renewed.

  #3
• i

  No transfer lock

  The domain has no transfer lock (status: active). A registrar lock protects against unauthorized transfers.

  #4
• ✓ Registry and delegation match #5

  The nameservers registered at the registry are the ones published in DNS.

ns1.creasrv.net, ns2.creasrv.net

Found

Parent zone

fr

Delegation from

d.nic.fr (194.0.9.1)

NS at the parent

ns1.creasrv.net, ns2.creasrv.net

NS in the zone

ns1.bdm.microsoftonline.com, ns1.creasrv.net, ns2.bdm.microsoftonline.com, ns2.creasrv.net, ns3.bdm.microsoftonline.com, ns4.bdm.microsoftonline.com

Checks

• i

  2 nameservers

  Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.creasrv.net, ns2.creasrv.net.

  #6
• !

  NS sets differ

  The nameservers at the parent and in the zone should be the same. Only in the zone: ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com, ns3.bdm.microsoftonline.com, ns4.bdm.microsoftonline.com. ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com, ns3.bdm.microsoftonline.com, ns4.bdm.microsoftonline.com report NS ns1.bdm.microsoftonline.com ns2.bdm.microsoftonline.com ns3.bdm.microsoftonline.com ns4.bdm.microsoftonline.com. ns1.creasrv.net, ns2.creasrv.net report NS ns1.bdm.microsoftonline.com ns1.creasrv.net ns2.bdm.microsoftonline.com ns2.creasrv.net ns3.bdm.microsoftonline.com ns4.bdm.microsoftonline.com.

  #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 4 IPv6 /48s.
• ✓ 2 autonomous systems #11

  The nameservers are spread over: AS16276 (OVH - OVH SAS, FR): 2 addresses; AS8075 (MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US): 8 addresses.
• i

  All nameserver names under .net

  All nameserver names are under one TLD, so a problem with that TLD also makes the nameservers unreachable. Some operators use names under two TLDs for extra resilience.

  #12
• i

  Partly IPv6

  These nameservers have no IPv6 address: ns1.creasrv.net, ns2.creasrv.net.

  #13

10 of 10 addresses answer authoritatively

Found

Checks

• ✓ All respond #14

  All 10 nameserver addresses answered.
• ✓ All authoritative #15

  Every responding nameserver answers authoritatively for the zone.
• ✓ 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.
• ✓ TCP supported #19

  All nameservers answer over TCP.
• ✓ EDNS supported #20

  All nameservers support EDNS(0).
• ✓ Public addresses #21

  All nameserver addresses are publicly routable.

serial 1 · primary ns1.bdm.microsoftonline.com

Found

Primary (MNAME)

ns1.bdm.microsoftonline.com

Contact (RNAME)

azuredns-hostmaster.microsoft.com

Serial

1

Refresh / retry

3600 s / 300 s

Expire

2419200 s

Negative TTL

300 s

Serial per nameserver

Checks

• !

  Serials differ

  The nameservers serve different versions of the zone: 1 on 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); 2026060400 on ns1.creasrv.net (37.59.244.1), ns2.creasrv.net (5.135.243.225). This is normal for a few minutes after a change; if it lasts, zone transfers to the secondaries are failing.

  #22
• ✓ Timers within recommendations #23

  SOA refresh 1h, retry 5m, expire 28d, negative TTL 5m.
• ✓ Primary is a public nameserver #24

  The primary nameserver ns1.bdm.microsoftonline.com is one of the listed nameservers.
• ✓ Contact azuredns-hostmaster@microsoft.com #25

  The SOA RNAME azuredns-hostmaster.microsoft.com means azuredns-hostmaster@microsoft.com.
• ✓ Counter serial #26

  The serial 1 is a plain counter.

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