inalco.fr

.fr country-code · GIP RENATER · expires 2026-11-19

Found

TLD

.fr (country-code)

ICANN policies apply

no

Registrar

GIP RENATER

Registered

19 November 1995

Last changed

31 December 2025

Expires

19 November 2026

Status

active

Registry nameservers

babel.inalco.fr, babelsec.inalco.fr, delta.univ-paris5.fr

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 28 days

  The registration expires on 2026-11-19. 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.

babel.inalco.fr, babelsec.inalco.fr, delta.univ-paris5.fr

Found

Parent zone

fr

Delegation from

d.nic.fr (194.0.9.1)

NS at the parent

babel.inalco.fr, babelsec.inalco.fr, delta.univ-paris5.fr

NS in the zone

babel.inalco.fr, babelsec.inalco.fr, delta.univ-paris5.fr

Checks

• ✓ 3 nameservers #6

  Delegated to babel.inalco.fr, babelsec.inalco.fr, delta.univ-paris5.fr.
• ✓ Parent and zone agree #7

  The parent delegation and the zone's NS records list the same nameservers.
• ✓ Glue present and correct #8

  Glue is published for the nameservers inside the zone: babel.inalco.fr, babelsec.inalco.fr.
• ✓ 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 3 IPv4 /24s and 0 IPv6 /48s.
• i

  All nameservers in one AS

  All nameserver addresses are announced by one network operator (AS2200 (FR-RENATER - Renater, FR): 3 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 .fr

  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

3 of 3 addresses answer authoritatively

Found

Checks

• ✓ All respond #14

  All 3 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: delta.univ-paris5.fr: "9.18.49-1~deb12u1-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.

serial 2026101301 · primary babel.inalco.fr

Found

Primary (MNAME)

babel.inalco.fr

Contact (RNAME)

dnsmaster.inalco.fr

Serial

2026101301

Refresh / retry

300 s / 3600 s

Expire

2419200 s

Negative TTL

86400 s

Serial per nameserver

Checks

• ✓ Serial 2026101301 everywhere #22

  All nameservers serve the same version of the zone.
• !

  Unusual SOA timers

  refresh 5m is outside 20m–1d; retry 1h should be shorter than refresh 5m. Current values: refresh 5m, retry 1h, expire 28d, negative TTL 1d.

  #23
• ✓ Primary is a public nameserver #24

  The primary nameserver babel.inalco.fr is one of the listed nameservers.
• ✓ Contact dnsmaster@inalco.fr #25

  The SOA RNAME dnsmaster.inalco.fr means dnsmaster@inalco.fr.
• ✓ Date-based serial #26

  The serial 2026101301 follows the YYYYMMDDnn convention (2026-10-13).

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