globalsecuritymag.fr

Checked 22 October 2026, 03:14 UTC · via 8.8.8.8
!Passed with warnings
25 passed 2 warnings 0 failed 4 info

Registration

info

.fr country-code · SCALEWAY · expires 2027-06-30

Found

TLD
.fr (country-code)
ICANN policies apply
no
Registrar
SCALEWAY
Registered
7 June 2007
Last changed
3 June 2026
Expires
30 June 2027
Status
client transfer prohibited
Registry nameservers
ns1.octopuce.fr, ns2.octopuce.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-06-30 #3
    The registration is valid until 2027-06-30 (251 days).
  • ✓ Transfer locked #4
    Registry status: client transfer prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

info

ns1.octopuce.fr, ns2.octopuce.net

Found

Parent zone
fr
Delegation from
d.nic.fr (194.0.9.1)
NS at the parent
ns1.octopuce.fr, ns2.octopuce.net
NS in the zone
ns1.octopuce.fr, ns2.octopuce.net
NameserverAddressesNetwork (AS)Glue
ns1.octopuce.fr91.194.60.99 2001:67c:288::99AS28855 OCTOPUCE-AS - Octopuce s.a.r.l., FR AS28855 OCTOPUCE-AS - Octopuce s.a.r.l., FR91.194.60.99 2001:67c:288::99
ns2.octopuce.net185.215.171.28 2a00:99a0:f000::28AS210770 OCTOPUCE-LYON - Octopuce s.a.r.l., FR AS210770 OCTOPUCE-LYON - Octopuce s.a.r.l., FR-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.octopuce.fr, ns2.octopuce.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 2 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS210770 (OCTOPUCE-LYON - Octopuce s.a.r.l., FR): 2 addresses; AS28855 (OCTOPUCE-AS - Octopuce s.a.r.l., FR): 2 addresses.
  • ✓ Nameserver names under 2 TLDs #12
    Nameserver names use the TLDs .fr, .net.
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

warn

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.octopuce.fr 91.194.60.99NOERROR, 15 ms, authoritativenoyes / yesrefusedBIND
ns1.octopuce.fr 2001:67c:288::99NOERROR, 14 ms, authoritativenoyes / yesrefusedBIND
ns2.octopuce.net 185.215.171.28NOERROR, 23 ms, authoritativenoyes / yesrefused9.18.49-1~deb12u2-Debian
ns2.octopuce.net 2a00:99a0:f000::28NOERROR, 22 ms, authoritativenoyes / yesrefused9.18.49-1~deb12u2-Debian

Checks

  • ✓ All respond #14
    All 4 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: ns2.octopuce.net: "9.18.49-1~deb12u2-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.

SOA

info

serial 2024052715 · primary simpubweb1.octopuce.fr

Found

Primary (MNAME)
simpubweb1.octopuce.fr
Contact (RNAME)
root.simpubweb1.octopuce.fr
Serial
2024052715
Refresh / retry
21600 s / 3600 s
Expire
1209600 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns1.octopuce.fr (91.194.60.99)2024052715
ns1.octopuce.fr (2001:67c:288::99)2024052715
ns2.octopuce.net (185.215.171.28)2024052715
ns2.octopuce.net (2a00:99a0:f000::28)2024052715

Checks

  • ✓ Serial 2024052715 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 6h, retry 1h, expire 14d, negative TTL 1d.
  • i
    Hidden master
    The primary nameserver simpubweb1.octopuce.fr is not listed as a nameserver: a hidden master that only feeds the public secondaries. That is a common setup; make sure it is not reachable for zone transfers from outside.
    #24
  • ✓ Contact root@simpubweb1.octopuce.fr #25
    The SOA RNAME root.simpubweb1.octopuce.fr means root@simpubweb1.octopuce.fr.
  • ✓ Date-based serial #26
    The serial 2024052715 follows the YYYYMMDDnn convention (2024-05-27).

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

9 records at the apex

Found

Read from
91.194.60.99:53
TypeValueTTL
SOAsimpubweb1.octopuce.fr. root.simpubweb1.octopuce.fr. 2024052715 21600 3600 1209600 8640086400
NSns2.octopuce.net.86400
NSns1.octopuce.fr.86400
A91.194.60.1286400
MX5 simpubweb1.octopuce.fr.86400
TXT"google-site-verification=JgX5Jv2hrEIRERMcB1Ronp9Ginju1E6ikRD_PzNt2Ys"86400
TXT"v=spf1 v=spf1 a mx include:spf.octopuce.fr ~al"86400
TXT"google-site-verification=nMi3kZDAUC3CTMl8BMWlDNzikH5EiR4q5U_xSRmj4gI"86400
TXT"google-site-verification=j9zBoiFyIje19GZf3ungvq47pKrtU3DWxwD20vDlAjo"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.
  • ✓ 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