franceplus.fr

Checked 22 October 2026, 03:08 UTC · via 8.8.8.8
✗Problems found
18 passed 2 warnings 3 failed 8 info

Registration

info

.fr country-code · OVH · expires 2027-03-09

Found

TLD
.fr (country-code)
ICANN policies apply
no
Registrar
OVH
Registered
9 March 2007
Last changed
30 April 2026
Expires
9 March 2027
Status
active
Registry nameservers
ns3172249.ip-51-210-32.eu, sdns2.ovh.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 on 2027-03-09 #3
    The registration is valid until 2027-03-09 (138 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

ns3172249.ip-51-210-32.eu, sdns2.ovh.net

Found

Parent zone
fr
Delegation from
d.nic.fr (194.0.9.1)
NS at the parent
ns3172249.ip-51-210-32.eu, sdns2.ovh.net
NS in the zone
ns3136290.ip-51-75-243.eu, sdns2.ovh.net
NameserverAddressesNetwork (AS)Glue
ns3136290.ip-51-75-243.eu (zone only)51.75.243.133AS16276 OVH - OVH SAS, FR-
ns3172249.ip-51-210-32.eu (parent only)51.210.32.166AS16276 OVH - OVH SAS, FR-
sdns2.ovh.net213.251.188.141 2001:41d0:1:4a8d::1AS16276 OVH - OVH SAS, FR AS16276 OVH - OVH SAS, FR-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns3172249.ip-51-210-32.eu, sdns2.ovh.net.
    #6
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only at the parent: ns3172249.ip-51-210-32.eu; only in the zone: ns3136290.ip-51-75-243.eu. ns3172249.ip-51-210-32.eu report NS ns3136290.ip-51-75-243.eu sdns2.ovh.net.
    #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 1 IPv6 /48.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS16276 (OVH - OVH SAS, FR): 4 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.
    #11
  • ✓ Nameserver names under 2 TLDs #12
    Nameserver names use the TLDs .eu, .net.
  • i
    Partly IPv6
    These nameservers have no IPv6 address: ns3136290.ip-51-75-243.eu, ns3172249.ip-51-210-32.eu.
    #13

Nameservers

fail

1 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns3136290.ip-51-75-243.eu 51.75.243.133no responsenono / no--
ns3172249.ip-51-210-32.eu 51.210.32.166NOERROR, 16 ms, authoritativenoyes / yesrefusednone
sdns2.ovh.net 213.251.188.141REFUSED, 18 ms, NOT authoritativenono / yesrefused-
sdns2.ovh.net 2001:41d0:1:4a8d::1REFUSED, 17 ms, NOT authoritativenono / yesrefused-

Checks

  • ✗
    Nameservers not responding
    These addresses did not answer, so resolvers waste time on timeouts: ns3136290.ip-51-75-243.eu (51.75.243.133): read udp 46.225.38.91:33134->51.75.243.133:53: read: connection refused.
    #14
  • ✗
    Lame delegation
    These nameservers don't answer authoritatively for the zone, so resolvers ignore them: sdns2.ovh.net (213.251.188.141): REFUSED, authoritative=false; sdns2.ovh.net (2001:41d0:1:4a8d::1): REFUSED, authoritative=false.
    #15
  • ✓ No recursion #16
    The nameservers do not answer recursive queries for other domains.
  • i
    Identifying string disclosed
    These nameservers answer version queries with a string that is not a version number: ns3172249.ip-51-210-32.eu: "none".
    #17
  • ✓ Zone transfers refused #18
    No nameserver allows a zone transfer to the public.
  • ✗
    No DNS over TCP
    DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: sdns2.ovh.net (213.251.188.141): ; sdns2.ovh.net (2001:41d0:1:4a8d::1): .
    #19
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

pass

serial 2024022204 · primary sdns2.ovh.net

Found

Primary (MNAME)
sdns2.ovh.net
Contact (RNAME)
direction.dewinter.ch
Serial
2024022204
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
10800 s

Checks

  • ✓ Serial 2024022204 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 7d, negative TTL 3h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver sdns2.ovh.net is one of the listed nameservers.
  • ✓ Contact direction@dewinter.ch #25
    The SOA RNAME direction.dewinter.ch means direction@dewinter.ch.
  • ✓ Date-based serial #26
    The serial 2024022204 follows the YYYYMMDDnn convention (2024-02-22).

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

6 records at the apex

Found

Read from
51.210.32.166:53
TypeValueTTL
SOAsdns2.ovh.net. direction.dewinter.ch. 2024022204 10800 3600 604800 1080086400
NSsdns2.ovh.net.86400
NSns3136290.ip-51-75-243.eu.86400
A51.210.32.16686400
MX10 mail.franceplus.fr.86400
TXT"google-site-verification=UADaplwPDgLHIaBQZz6L89Rd_i3t3c6UqmP_6WdZmI8"86400

Checks

  • ✓ TTLs within range #32
    TTLs: A 1d, MX 1d, 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