loroux-bottereau.fr

Checked 22 October 2026, 04:06 UTC · via 8.8.8.8
✗Problems found
21 passed 4 warnings 1 failed 5 info

Registration

info

.fr country-code · OVH · expires 2027-04-12

Found

TLD
.fr (country-code)
ICANN policies apply
no
Registrar
OVH
Registered
24 May 2004
Last changed
31 May 2026
Expires
12 April 2027
Status
client transfer prohibited, client delete prohibited
Registry nameservers
dns1.ayaline.com, dns2.ayaline.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-12 #3
    The registration is valid until 2027-04-12 (172 days).
  • ✓ Transfer locked #4
    Registry status: client transfer prohibited, client delete prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

warn

dns1.ayaline.com, dns2.ayaline.com

Found

Parent zone
fr
Delegation from
d.nic.fr (194.0.9.1)
NS at the parent
dns1.ayaline.com, dns2.ayaline.com
NS in the zone
carib.lnet.fr, dns1.ayaline.com, dns2.ayaline.com
NameserverAddressesNetwork (AS)Glue
carib.lnet.fr (zone only)149.202.252.190AS16276 OVH - OVH SAS, FR-
dns1.ayaline.com51.91.182.49AS16276 OVH - OVH SAS, FR-
dns2.ayaline.com149.202.252.190AS16276 OVH - OVH SAS, FR-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: dns1.ayaline.com, dns2.ayaline.com.
    #6
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only in the zone: carib.lnet.fr. dns1.ayaline.com report NS carib.lnet.fr dns1.ayaline.com dns2.ayaline.com.
    #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 2 IPv4 /24s and 0 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS16276 (OVH - OVH SAS, FR): 3 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.
    #11
  • 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

1 of 3 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
carib.lnet.fr 149.202.252.190no responsenono / no--
dns1.ayaline.com 51.91.182.49NOERROR, 15 ms, authoritativenoyes / yesrefused9.20.18-1~deb13u1-Debian
dns2.ayaline.com 149.202.252.190no responsenono / no--

Checks

  • ✗
    Nameservers not responding
    These addresses did not answer, so resolvers waste time on timeouts: carib.lnet.fr (149.202.252.190): read udp 46.225.38.91:34312->149.202.252.190:53: i/o timeout; dns2.ayaline.com (149.202.252.190): read udp 46.225.38.91:40220->149.202.252.190:53: i/o timeout.
    #14
  • ✓ 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: dns1.ayaline.com: "9.20.18-1~deb13u1-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

pass

serial 2026092803 · primary dns1.ayaline.com

Found

Primary (MNAME)
dns1.ayaline.com
Contact (RNAME)
admin.ayaline.com
Serial
2026092803
Refresh / retry
3600 s / 1800 s
Expire
1209600 s
Negative TTL
86400 s

Checks

  • ✓ Serial 2026092803 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 dns1.ayaline.com is one of the listed nameservers.
  • ✓ Contact admin@ayaline.com #25
    The SOA RNAME admin.ayaline.com means admin@ayaline.com.
  • ✓ Date-based serial #26
    The serial 2026092803 follows the YYYYMMDDnn convention (2026-09-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

10 records at the apex

Found

Read from
51.91.182.49:53
TypeValueTTL
SOAdns1.ayaline.com. admin.ayaline.com. 2026092803 3600 1800 1209600 864003600
NSdns2.ayaline.com.3600
NSdns1.ayaline.com.3600
NScarib.lnet.fr.3600
A109.234.166.1023600
MX10 lorouxbottereau-fr01e.mail.protection.outlook.com.3600
TXT"brevo-code:39cc4dde1429293c53607f6f1133214e"3600
TXT"MS=ms43444257"3600
TXT"v=DMARC1; p=none"3600
TXT"v=spf1 include:spf.protection.outlook.com ip4:90.102.104.249 ip4:193.248.171.61 include:spf.mailjet.com -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.
  • ✓ 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