ville-lempdes.fr

Checked 22 October 2026, 05:48 UTC · via 8.8.8.8
!Passed with warnings
23 passed 3 warnings 0 failed 5 info

Registration

info

.fr country-code · OVH · expires 2026-12-23

Found

TLD
.fr (country-code)
ICANN policies apply
no
Registrar
OVH
Registered
22 August 1999
Last changed
31 January 2026
Expires
23 December 2026
Status
active
Registry nameservers
ns1.web4all.fr, ns2.web4all.fr, ns3.web4all.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 2026-12-23 #3
    The registration is valid until 2026-12-23 (62 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

ns1.web4all.fr, ns2.web4all.fr, ns3.web4all.fr

Found

Parent zone
fr
Delegation from
d.nic.fr (194.0.9.1)
NS at the parent
ns1.web4all.fr, ns2.web4all.fr, ns3.web4all.fr
NS in the zone
ns1.yulpa.io, ns2.yulpa.io, ns3.yulpa.io
NameserverAddressesNetwork (AS)Glue
ns1.web4all.fr (parent only)185.49.20.10AS197492 INEONET-AS - ALSATIS SERVICES SAS, FR-
ns1.yulpa.io (zone only)185.49.20.10AS197492 INEONET-AS - ALSATIS SERVICES SAS, FR-
ns2.web4all.fr (parent only)91.220.248.154AS197492 INEONET-AS - ALSATIS SERVICES SAS, FR-
ns2.yulpa.io (zone only)91.220.248.154AS197492 INEONET-AS - ALSATIS SERVICES SAS, FR-
ns3.web4all.fr (parent only)92.243.4.24AS203476 GANDI-AS-2 - GANDI SAS, FR-
ns3.yulpa.io (zone only)92.243.4.24AS203476 GANDI-AS-2 - GANDI SAS, FR-

Checks

  • ✓ 3 nameservers #6
    Delegated to ns1.web4all.fr, ns2.web4all.fr, ns3.web4all.fr.
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only at the parent: ns1.web4all.fr, ns2.web4all.fr, ns3.web4all.fr; only in the zone: ns1.yulpa.io, ns2.yulpa.io, ns3.yulpa.io. ns1.web4all.fr, ns1.yulpa.io, ns2.web4all.fr, ns2.yulpa.io, ns3.web4all.fr, ns3.yulpa.io report NS ns1.yulpa.io ns2.yulpa.io ns3.yulpa.io.
    #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 3 IPv4 /24s and 0 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS197492 (INEONET-AS - ALSATIS SERVICES SAS, FR): 4 addresses; AS203476 (GANDI-AS-2 - GANDI SAS, FR): 2 addresses.
  • 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

pass

6 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.web4all.fr 185.49.20.10NOERROR, 22 ms, authoritativenoyes / yesrefused-
ns1.yulpa.io 185.49.20.10NOERROR, 22 ms, authoritativenoyes / yesrefused-
ns2.web4all.fr 91.220.248.154NOERROR, 24 ms, authoritativenoyes / yesrefused-
ns2.yulpa.io 91.220.248.154NOERROR, 25 ms, authoritativenoyes / yesrefused-
ns3.web4all.fr 92.243.4.24NOERROR, 24 ms, authoritativenoyes / yesrefused-
ns3.yulpa.io 92.243.4.24NOERROR, 24 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 6 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.
  • ✓ No version disclosed #17
    The nameservers don't reveal their software version.
  • ✓ 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 2026100500 · primary ns1.yulpa.io

Found

Primary (MNAME)
ns1.yulpa.io
Contact (RNAME)
zonecheck.yulpa.io
Serial
2026100500
Refresh / retry
14400 s / 3600 s
Expire
1209600 s
Negative TTL
900 s

Serial per nameserver

NameserverSerial
ns1.web4all.fr (185.49.20.10)2026100500
ns1.yulpa.io (185.49.20.10)2026100500
ns2.web4all.fr (91.220.248.154)2026100500
ns2.yulpa.io (91.220.248.154)2026100500
ns3.web4all.fr (92.243.4.24)2026100500
ns3.yulpa.io (92.243.4.24)2026100500

Checks

  • ✓ Serial 2026100500 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 4h, retry 1h, expire 14d, negative TTL 15m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.yulpa.io is one of the listed nameservers.
  • ✓ Contact zonecheck@yulpa.io #25
    The SOA RNAME zonecheck.yulpa.io means zonecheck@yulpa.io.
  • ✓ Date-based serial #26
    The serial 2026100500 follows the YYYYMMDDnn convention (2026-10-05).

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

10 records at the apex

Found

Read from
185.49.20.10:53
TypeValueTTL
SOAns1.yulpa.io. zonecheck.yulpa.io. 2026100500 14400 3600 1209600 9007200
NSns1.yulpa.io.86400
NSns3.yulpa.io.86400
NSns2.yulpa.io.86400
A54.36.91.627200
AAAA2001:41d0:301::277200
MX20 mx20.yulpa.io.7200
MX10 mx10.yulpa.io.7200
MX30 mx30.yulpa.io.7200
TXT"v=spf1 include:spf.yulpa.io ip4:194.158.98.48 -all"7200

Checks

  • ✓ TTLs within range #32
    TTLs: A 2h, AAAA 2h, MX 2h, NS 1d. The NS TTL at the parent is 1h and in the zone 1d; resolvers may use either.
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • i
    Wildcard record
    A random name under the zone resolves, so there is a wildcard (*) record. Typos and non-existent hosts resolve too, which can confuse mail and certificate checks.
    #34
  • 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