fmsh.fr

Checked 22 October 2026, 03:04 UTC · via 8.8.8.8
✗Problems found
21 passed 4 warnings 1 failed 5 info

Registration

info

.fr country-code · GIP RENATER · expires 2027-04-14

Found

TLD
.fr (country-code)
ICANN policies apply
no
Registrar
GIP RENATER
Registered
14 April 2008
Last changed
31 May 2026
Expires
14 April 2027
Status
active
Registry nameservers
alize.msh-paris.fr, alize4.cid.msh-paris.fr, kirova.pmsh.msh-paris.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 on 2027-04-14 #3
    The registration is valid until 2027-04-14 (174 days).
  • 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.

Delegation

warn

alize.msh-paris.fr, alize4.cid.msh-paris.fr, kirova.pmsh.msh-paris.fr

Found

Parent zone
fr
Delegation from
d.nic.fr (194.0.9.1)
NS at the parent
alize.msh-paris.fr, alize4.cid.msh-paris.fr, kirova.pmsh.msh-paris.fr
NS in the zone
alize.msh-paris.fr, alize4.cid.msh-paris.fr, kirova.pmsh.msh-paris.fr
NameserverAddressesNetwork (AS)Glue
alize.msh-paris.fr195.221.170.194AS2200 FR-RENATER - Renater, FR195.221.170.194
alize4.cid.msh-paris.fr193.49.20.221AS2200 FR-RENATER - Renater, FR193.49.20.221
kirova.pmsh.msh-paris.fr193.51.121.231AS2200 FR-RENATER - Renater, FR193.51.121.231

Checks

  • ✓ 3 nameservers #6
    Delegated to alize.msh-paris.fr, alize4.cid.msh-paris.fr, kirova.pmsh.msh-paris.fr.
  • ✓ 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 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

Nameservers

fail

2 of 3 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
alize.msh-paris.fr 195.221.170.194NOERROR, 35 ms, authoritativenoyes / yesrefused9.10.6-P1
alize4.cid.msh-paris.fr 193.49.20.221no responsenono / no--
kirova.pmsh.msh-paris.fr 193.51.121.231NOERROR, 27 ms, authoritativenoyes / yesrefused9.10.3-P4

Checks

  • ✗
    Nameservers not responding
    These addresses did not answer, so resolvers waste time on timeouts: alize4.cid.msh-paris.fr (193.49.20.221): read udp 46.225.38.91:43665->193.49.20.221:53: read: connection refused.
    #14
  • ✓ 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: alize.msh-paris.fr: "9.10.6-P1"; kirova.pmsh.msh-paris.fr: "9.10.3-P4". 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.

SOA

pass

serial 2026082500 · primary alize.msh-paris.fr

Found

Primary (MNAME)
alize.msh-paris.fr
Contact (RNAME)
svpdns.fmsh.fr
Serial
2026082500
Refresh / retry
86400 s / 7200 s
Expire
3600000 s
Negative TTL
300 s

Serial per nameserver

NameserverSerial
alize.msh-paris.fr (195.221.170.194)2026082500
kirova.pmsh.msh-paris.fr (193.51.121.231)2026082500

Checks

  • ✓ Serial 2026082500 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1d, retry 2h, expire 1000h, negative TTL 5m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver alize.msh-paris.fr is one of the listed nameservers.
  • ✓ Contact svpdns@fmsh.fr #25
    The SOA RNAME svpdns.fmsh.fr means svpdns@fmsh.fr.
  • ✓ Date-based serial #26
    The serial 2026082500 follows the YYYYMMDDnn convention (2026-08-25).

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

warn

6 records at the apex

Found

Read from
195.221.170.194:53
TypeValueTTL
SOAalize.msh-paris.fr. svpdns.fmsh.fr. 2026082500 86400 7200 3600000 3001209600
NSalize.msh-paris.fr.1209600
NSkirova.pmsh.msh-paris.fr.1209600
NSalize4.cid.msh-paris.fr.1209600
MX500 pmg.cid.msh-paris.fr.1209600
MX100 merak.msh-paris.fr.1209600

Checks

  • !
    Very high TTLs
    These records have a TTL above 7d, so changes take very long to reach everyone: MX (14d), NS (14d). The NS TTL at the parent is 1h and in the zone 14d; resolvers may use either.
    #32
  • ✓ 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