epernay.fr

Checked 22 October 2026, 02:46 UTC · via 8.8.8.8
!Passed with warnings
25 passed 1 warning 0 failed 5 info

Registration

info

.fr country-code · HEXANET SAS · expires 2027-09-14

Found

TLD
.fr (country-code)
ICANN policies apply
no
Registrar
HEXANET SAS
Registered
27 November 2001
Last changed
14 September 2026
Expires
14 September 2027
Status
active, auto renew period
Registry nameservers
ns3.hexanet.fr, ns4.hexanet.fr, ns5.hexanet.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-09-14 #3
    The registration is valid until 2027-09-14 (327 days).
  • i
    No transfer lock
    The domain has no transfer lock (status: active, auto renew period). 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

info

ns3.hexanet.fr, ns4.hexanet.fr, ns5.hexanet.fr

Found

Parent zone
fr
Delegation from
d.nic.fr (194.0.9.1)
NS at the parent
ns3.hexanet.fr, ns4.hexanet.fr, ns5.hexanet.fr
NS in the zone
ns3.hexanet.fr, ns4.hexanet.fr, ns5.hexanet.fr
NameserverAddressesNetwork (AS)Glue
ns3.hexanet.fr81.23.32.176 2a00:fc8:0:5:81:23:32:176AS34863 HEXANET - HEXANET SAS, FR AS34863 HEXANET - HEXANET SAS, FR81.23.32.176 2a00:fc8:0:5:81:23:32:176
ns4.hexanet.fr81.23.32.177 2a00:fc8:0:5:81:23:32:177AS34863 HEXANET - HEXANET SAS, FR AS34863 HEXANET - HEXANET SAS, FR81.23.32.177 2a00:fc8:0:5:81:23:32:177
ns5.hexanet.fr92.243.21.110 2001:4b98:dc0:45:216:3eff:fe6d:44edAS203476 GANDI-AS-2 - GANDI SAS, FR AS29169 GANDI-AS - GANDI SAS, FR92.243.21.110 2001:4b98:dc0:45:216:3eff:fe6d:44ed

Checks

  • ✓ 3 nameservers #6
    Delegated to ns3.hexanet.fr, ns4.hexanet.fr, ns5.hexanet.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 2 IPv4 /24s and 2 IPv6 /48s.
  • ✓ 3 autonomous systems #11
    The nameservers are spread over: AS203476 (GANDI-AS-2 - GANDI SAS, FR): 1 address; AS29169 (GANDI-AS - GANDI SAS, FR): 1 address; AS34863 (HEXANET - HEXANET SAS, FR): 4 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
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

pass

6 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns3.hexanet.fr 81.23.32.176NOERROR, 15 ms, authoritativenoyes / yesrefused-
ns3.hexanet.fr 2a00:fc8:0:5:81:23:32:176NOERROR, 16 ms, authoritativenoyes / yesrefused-
ns4.hexanet.fr 81.23.32.177NOERROR, 15 ms, authoritativenoyes / yesrefused-
ns4.hexanet.fr 2a00:fc8:0:5:81:23:32:177NOERROR, 16 ms, authoritativenoyes / yesrefused-
ns5.hexanet.fr 92.243.21.110NOERROR, 20 ms, authoritativenoyes / yesrefused-
ns5.hexanet.fr 2001:4b98:dc0:45:216:3eff:fe6d:44edNOERROR, 19 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 1783495201 · primary ns3.hexanet.fr

Found

Primary (MNAME)
ns3.hexanet.fr
Contact (RNAME)
postmaster.hexanet.fr
Serial
1783495201
Refresh / retry
28800 s / 7200 s
Expire
604800 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns3.hexanet.fr (81.23.32.176)1783495201
ns3.hexanet.fr (2a00:fc8:0:5:81:23:32:176)1783495201
ns4.hexanet.fr (81.23.32.177)1783495201
ns4.hexanet.fr (2a00:fc8:0:5:81:23:32:177)1783495201
ns5.hexanet.fr (92.243.21.110)1783495201
ns5.hexanet.fr (2001:4b98:dc0:45:216:3eff:fe6d:44ed)1783495201

Checks

  • ✓ Serial 1783495201 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 8h, retry 2h, expire 7d, negative TTL 1d.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns3.hexanet.fr is one of the listed nameservers.
  • ✓ Contact postmaster@hexanet.fr #25
    The SOA RNAME postmaster.hexanet.fr means postmaster@hexanet.fr.
  • ✓ Timestamp serial #26
    The serial 1783495201 is a Unix timestamp (2026-07-08 07:20 UTC).

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

8 records at the apex

Found

Read from
81.23.32.176:53
TypeValueTTL
SOAns3.hexanet.fr. postmaster.hexanet.fr. 1783495201 28800 7200 604800 864003600
NSns4.hexanet.fr.3600
NSns5.hexanet.fr.3600
NSns3.hexanet.fr.3600
A145.239.185.693600
MX0 mx.hexanet.fr.3600
MX0 mx2.hexanet.fr.3600
TXT"v=spf1 ip4:81.23.38.62 include:spf.hexanet.fr ~all"3600

Checks

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