manteslajolie.fr

.fr country-code · NAMEBAY · expires 2026-11-17

Found

TLD

.fr (country-code)

ICANN policies apply

no

Registrar

NAMEBAY

Registered

9 February 2007

Last changed

17 September 2025

Expires

17 November 2026

Status

active

Registry nameservers

ns1.over-link.net, ns2.over-link.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 26 days

  The registration expires on 2026-11-17. 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.over-link.net, ns2.over-link.net

Found

Parent zone

fr

Delegation from

d.nic.fr (194.0.9.1)

NS at the parent

ns1.over-link.net, ns2.over-link.net

NS in the zone

ns1.over-link.net, ns2.over-link.net

Checks

• i

  2 nameservers

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

  #6
• ✓ Parent and zone agree #7

  The parent delegation and the zone's NS records list the same nameservers.
• ✓ 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 2 IPv4 /24s and 0 IPv6 /48s.
• i

  All nameservers in one AS

  All nameserver addresses are announced by one network operator (AS48426 (OVER-LINK - _OVER-LINK_ s.a.s., FR): 2 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.

  #11
• 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
• !

  No IPv6

  None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.

  #13

2 of 2 addresses answer authoritatively

Found

Checks

• ✓ All respond #14

  All 2 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: ns1.over-link.net: "9.11.5-P4-5.1+deb10u11-Debian"; ns2.over-link.net: "9.9.5-9+deb8u19-Debian". 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.

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