rillieuxlapape.fr

Checked 22 October 2026, 05:02 UTC · via 8.8.8.8
✗Problems found
20 passed 5 warnings 1 failed 5 info

Registration

info

.fr country-code · INFORMATIQUE ON LINE · expires 2027-04-25

Found

TLD
.fr (country-code)
ICANN policies apply
no
Registrar
INFORMATIQUE ON LINE
Registered
25 April 2014
Last changed
31 May 2026
Expires
25 April 2027
Status
active
Registry nameservers
ns3.dns-iol.com, ns4.dns-iol.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-04-25 #3
    The registration is valid until 2027-04-25 (185 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

ns3.dns-iol.com, ns4.dns-iol.com

Found

Parent zone
fr
Delegation from
d.nic.fr (194.0.9.1)
NS at the parent
ns3.dns-iol.com, ns4.dns-iol.com
NS in the zone
ns3.dns-iol.com, ns4.dns-iol.com
NameserverAddressesNetwork (AS)Glue
ns3.dns-iol.com80.118.141.7AS15557 LDCOMNET - Societe Francaise Du Radiotelephone - SFR SA, FR-
ns4.dns-iol.com195.200.78.5AS41894 INFORMATIQUE-AS - INFORMATIQUE ON LINE SAS, FR-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns3.dns-iol.com, ns4.dns-iol.com.
    #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 0 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS15557 (LDCOMNET - Societe Francaise Du Radiotelephone - SFR SA, FR): 1 address; AS41894 (INFORMATIQUE-AS - INFORMATIQUE ON LINE SAS, FR): 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

fail

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns3.dns-iol.com 80.118.141.7NOERROR, 20 ms, authoritativenono / yesrefused9.5.2-RedHat-9.5.2-1.fc10
ns4.dns-iol.com 195.200.78.5NOERROR, 52 ms, authoritativenoyes / yesrefused9.18.39-0ubuntu0.22.04.7-Ubuntu

Checks

  • ✓ All respond #14
    All 2 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: ns3.dns-iol.com: "9.5.2-RedHat-9.5.2-1.fc10"; ns4.dns-iol.com: "9.18.39-0ubuntu0.22.04.7-Ubuntu". Hide or replace the version string.
    #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: ns3.dns-iol.com (80.118.141.7): dial tcp 80.118.141.7:53: i/o timeout.
    #19
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

warn

serial 2026102101 · primary ns3.dns-iol.com

Found

Primary (MNAME)
ns3.dns-iol.com
Contact (RNAME)
info.i-online.fr
Serial
2026102101
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
60 s

Serial per nameserver

NameserverSerial
ns3.dns-iol.com (80.118.141.7)2026102101
ns4.dns-iol.com (195.200.78.5)2026102101

Checks

  • ✓ Serial 2026102101 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    negative caching TTL (minimum) 1m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 3h, retry 1h, expire 7d, negative TTL 1m.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns3.dns-iol.com is one of the listed nameservers.
  • ✓ Contact info@i-online.fr #25
    The SOA RNAME info.i-online.fr means info@i-online.fr.
  • ✓ Date-based serial #26
    The serial 2026102101 follows the YYYYMMDDnn convention (2026-10-21).

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

warn

11 records at the apex

Found

Read from
80.118.141.7:53
TypeValueTTL
SOAns3.dns-iol.com. info.i-online.fr. 2026102101 10800 3600 604800 6060
NSns3.dns-iol.com.60
NSns4.dns-iol.com.60
A91.121.52.8360
MX20 vade-mx-eu-fallback02.hornetsecurity.com.60
MX10 vade-mx-fr01.hornetsecurity.com.60
MX10 vade-mx-fr02.hornetsecurity.com.60
MX20 vade-mx-eu-fallback01.hornetsecurity.com.60
TXT"MS=ms12033233"60
TXT"0hqio372x6t3UDhsdAehBmh7GM8="60
TXT"v=spf1 ip4:213.56.149.49 include:spf.protection.outlook.com include:spf.stratis.pro include:spf.cloud.vadesecure.com include:spf.hornetsecurity.com -all"60

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (1m), MX (1m), NS (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1h and in the zone 1m; resolvers may use either.
    #32
  • ✓ 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