teachizy.fr

Checked 22 October 2026, 05:24 UTC · via 8.8.8.8
!Passed with warnings
23 passed 2 warnings 0 failed 6 info

Registration

info

.fr country-code · SCALEWAY · expires 2027-03-26

Found

TLD
.fr (country-code)
ICANN policies apply
no
Registrar
SCALEWAY
Registered
26 March 2020
Last changed
3 June 2026
Expires
26 March 2027
Status
client transfer prohibited
Registry nameservers
ashley.ns.cloudflare.com, rayden.ns.cloudflare.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-03-26 #3
    The registration is valid until 2027-03-26 (155 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

ashley.ns.cloudflare.com, rayden.ns.cloudflare.com

Found

Parent zone
fr
Delegation from
d.nic.fr (194.0.9.1)
NS at the parent
ashley.ns.cloudflare.com, rayden.ns.cloudflare.com
NS in the zone
ashley.ns.cloudflare.com, rayden.ns.cloudflare.com
NameserverAddressesNetwork (AS)Glue
ashley.ns.cloudflare.com173.245.58.71 172.64.32.71 108.162.192.71 2606:4700:50::adf5:3a47 2803:f800:50::6ca2:c047 2a06:98c1:50::ac40:2047AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US-
rayden.ns.cloudflare.com108.162.195.163 162.159.44.163 172.64.35.163 2803:f800:50::6ca2:c3a3 2a06:98c1:50::ac40:23a3 2606:4700:58::a29f:2ca3AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ashley.ns.cloudflare.com, rayden.ns.cloudflare.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 6 IPv4 /24s and 4 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS13335 (CLOUDFLARENET - Cloudflare, Inc., US): 12 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
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

warn

12 of 12 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ashley.ns.cloudflare.com 173.245.58.71NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
ashley.ns.cloudflare.com 172.64.32.71NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
ashley.ns.cloudflare.com 108.162.192.71NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
ashley.ns.cloudflare.com 2606:4700:50::adf5:3a47NOERROR, 18 ms, authoritativenoyes / yesrefused2026.10.2
ashley.ns.cloudflare.com 2803:f800:50::6ca2:c047NOERROR, 18 ms, authoritativenoyes / yesrefused2026.10.2
ashley.ns.cloudflare.com 2a06:98c1:50::ac40:2047NOERROR, 18 ms, authoritativenoyes / yesrefused2026.10.2
rayden.ns.cloudflare.com 108.162.195.163NOERROR, 13 ms, authoritativenoyes / yesrefused2026.10.2
rayden.ns.cloudflare.com 162.159.44.163NOERROR, 34 ms, authoritativenoyes / yesrefused2026.10.2
rayden.ns.cloudflare.com 172.64.35.163NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
rayden.ns.cloudflare.com 2803:f800:50::6ca2:c3a3NOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.2
rayden.ns.cloudflare.com 2a06:98c1:50::ac40:23a3NOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.2
rayden.ns.cloudflare.com 2606:4700:58::a29f:2ca3NOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.2

Checks

  • ✓ All respond #14
    All 12 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: ashley.ns.cloudflare.com: "2026.10.2"; rayden.ns.cloudflare.com: "2026.10.2". 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 2418016710 · primary ashley.ns.cloudflare.com

Found

Primary (MNAME)
ashley.ns.cloudflare.com
Contact (RNAME)
dns.cloudflare.com
Serial
2418016710
Refresh / retry
10000 s / 2400 s
Expire
604800 s
Negative TTL
1800 s

Serial per nameserver

NameserverSerial
ashley.ns.cloudflare.com (173.245.58.71)2418016710
ashley.ns.cloudflare.com (172.64.32.71)2418016710
ashley.ns.cloudflare.com (108.162.192.71)2418016710
ashley.ns.cloudflare.com (2606:4700:50::adf5:3a47)2418016710
ashley.ns.cloudflare.com (2803:f800:50::6ca2:c047)2418016710
ashley.ns.cloudflare.com (2a06:98c1:50::ac40:2047)2418016710
rayden.ns.cloudflare.com (108.162.195.163)2418016710
rayden.ns.cloudflare.com (162.159.44.163)2418016710
rayden.ns.cloudflare.com (172.64.35.163)2418016710
rayden.ns.cloudflare.com (2803:f800:50::6ca2:c3a3)2418016710
rayden.ns.cloudflare.com (2a06:98c1:50::ac40:23a3)2418016710
rayden.ns.cloudflare.com (2606:4700:58::a29f:2ca3)2418016710

Checks

  • ✓ Serial 2418016710 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 2h46m40s, retry 40m, expire 7d, negative TTL 30m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ashley.ns.cloudflare.com is one of the listed nameservers.
  • ✓ Contact dns@cloudflare.com #25
    The SOA RNAME dns.cloudflare.com means dns@cloudflare.com.
  • ✓ Timestamp serial #26
    The serial 2418016710 is a Unix timestamp (2046-08-16 07:18 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
173.245.58.71:53
TypeValueTTL
SOAashley.ns.cloudflare.com. dns.cloudflare.com. 2418016710 10000 2400 604800 18001800
NSashley.ns.cloudflare.com.86400
NSrayden.ns.cloudflare.com.86400
A109.234.167.12300
MX0 mail.teachizy.fr.300
TXT"Sendinblue-code:6a0b0a275765b7806f31d917b76bfad3"300
TXT"google-site-verification=_eRYnS4afzIwyxfpLqz3bPFeo-FZ4sOrXVeGyhnyb9o"300
TXT"v=spf1 ip4:109.234.165.31 ip4:109.234.160.71 ip4:109.234.162.106 include:spf.sendinblue.com include:spf.jabatus.fr ~all"300

Checks

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