cheneliege.fr

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

Registration

info

.fr country-code · Realtime Register B.V. · expires 2027-01-12

Found

TLD
.fr (country-code)
ICANN policies apply
no
Registrar
Realtime Register B.V.
Registered
12 January 2018
Last changed
19 February 2026
Expires
12 January 2027
Status
client transfer prohibited
Registry nameservers
ns1.ex2.com, ns2.ex2.com, ns3.ex2.com
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-01-12 #3
    The registration is valid until 2027-01-12 (82 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

warn

ns1.ex2.com, ns2.ex2.com, ns3.ex2.com

Found

Parent zone
fr
Delegation from
d.nic.fr (194.0.9.1)
NS at the parent
ns1.ex2.com, ns2.ex2.com, ns3.ex2.com
NS in the zone
ns1.ex2.com, ns2.ex2.com, ns3.ex2.com
NameserverAddressesNetwork (AS)Glue
ns1.ex2.com141.94.247.250AS16276 OVH - OVH SAS, FR-
ns2.ex2.com116.203.251.62AS24940 HETZNER-AS - Hetzner Online GmbH, DE-
ns3.ex2.com51.161.108.51AS16276 OVH - OVH SAS, FR-

Checks

  • ✓ 3 nameservers #6
    Delegated to ns1.ex2.com, ns2.ex2.com, ns3.ex2.com.
  • ✓ 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.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS16276 (OVH - OVH SAS, FR): 2 addresses; AS24940 (HETZNER-AS - Hetzner Online GmbH, DE): 1 address.
  • i
    All nameserver names under .com
    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

warn

3 of 3 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.ex2.com 141.94.247.250NOERROR, 18 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 5.1.4 (built Aug 10 2026 00:00:00 by root@bh-centos-9.dev.cpanel.net)
ns2.ex2.com 116.203.251.62NOERROR, 5 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 5.1.4 (built Aug 10 2026 00:00:00 by root@bh-centos-9.dev.cpanel.net)
ns3.ex2.com 51.161.108.51NOERROR, 96 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 5.1.4 (built Aug 10 2026 00:00:00 by root@bh-centos-9.dev.cpanel.net)

Checks

  • ✓ All respond #14
    All 3 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: ns1.ex2.com: "PowerDNS Authoritative Server 5.1.4 (built Aug 10 2026 00:00:00 by root@bh-centos-9.dev.cpanel.net)"; ns2.ex2.com: "PowerDNS Authoritative Server 5.1.4 (built Aug 10 2026 00:00:00 by root@bh-centos-9.dev.cpanel.net)"; ns3.ex2.com: "PowerDNS Authoritative Server 5.1.4 (built Aug 10 2026 00:00:00 by root@bh-centos-9.dev.cpanel.net)". 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 2026082801 · primary ns1.ex2.com

Found

Primary (MNAME)
ns1.ex2.com
Contact (RNAME)
support.ex2.com
Serial
2026082801
Refresh / retry
3600 s / 1800 s
Expire
1209600 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns1.ex2.com (141.94.247.250)2026082801
ns2.ex2.com (116.203.251.62)2026082801
ns3.ex2.com (51.161.108.51)2026082801

Checks

  • ✓ Serial 2026082801 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1h, retry 30m, expire 14d, negative TTL 1d.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.ex2.com is one of the listed nameservers.
  • ✓ Contact support@ex2.com #25
    The SOA RNAME support.ex2.com means support@ex2.com.
  • ✓ Date-based serial #26
    The serial 2026082801 follows the YYYYMMDDnn convention (2026-08-28).

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

7 records at the apex

Found

Read from
141.94.247.250:53
TypeValueTTL
SOAns1.ex2.com. support.ex2.com. 2026082801 3600 1800 1209600 8640086400
NSns1.ex2.com.86400
NSns2.ex2.com.86400
NSns3.ex2.com.86400
A91.134.44.22614400
MX0 cheneliege.fr.14400
TXT"v=spf1 ip4:91.134.44.226 ip4:146.59.152.203 ip4:193.70.45.74 +a +mx +ip4:176.31.230.45 ~all"14400

Checks

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