horoscope.fr

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

Registration

info

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

Found

TLD
.fr (country-code)
ICANN policies apply
no
Registrar
TELEMAQUE
Registered
12 April 2000
Last changed
1 June 2026
Expires
12 April 2027
Status
active
Registry nameservers
fay.ns.cloudflare.com, jihoon.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-04-12 #3
    The registration is valid until 2027-04-12 (172 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

info

fay.ns.cloudflare.com, jihoon.ns.cloudflare.com

Found

Parent zone
fr
Delegation from
d.nic.fr (194.0.9.1)
NS at the parent
fay.ns.cloudflare.com, jihoon.ns.cloudflare.com
NS in the zone
fay.ns.cloudflare.com, jihoon.ns.cloudflare.com
NameserverAddressesNetwork (AS)Glue
fay.ns.cloudflare.com173.245.58.115 108.162.192.115 172.64.32.115 2a06:98c1:50::ac40:2073 2606:4700:50::adf5:3a73 2803:f800:50::6ca2:c073AS13335 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-
jihoon.ns.cloudflare.com108.162.195.233 172.64.35.233 162.159.44.233 2a06:98c1:50::ac40:23e9 2606:4700:58::a29f:2ce9 2803:f800:50::6ca2:c3e9AS13335 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: fay.ns.cloudflare.com, jihoon.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
fay.ns.cloudflare.com 173.245.58.115NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
fay.ns.cloudflare.com 108.162.192.115NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
fay.ns.cloudflare.com 172.64.32.115NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
fay.ns.cloudflare.com 2a06:98c1:50::ac40:2073NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
fay.ns.cloudflare.com 2606:4700:50::adf5:3a73NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
fay.ns.cloudflare.com 2803:f800:50::6ca2:c073NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
jihoon.ns.cloudflare.com 108.162.195.233NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
jihoon.ns.cloudflare.com 172.64.35.233NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
jihoon.ns.cloudflare.com 162.159.44.233NOERROR, 32 ms, authoritativenoyes / yesrefused2026.10.2
jihoon.ns.cloudflare.com 2a06:98c1:50::ac40:23e9NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
jihoon.ns.cloudflare.com 2606:4700:58::a29f:2ce9NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
jihoon.ns.cloudflare.com 2803:f800:50::6ca2:c3e9NOERROR, 15 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: fay.ns.cloudflare.com: "2026.10.2"; jihoon.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 2416064699 · primary fay.ns.cloudflare.com

Found

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

Serial per nameserver

NameserverSerial
fay.ns.cloudflare.com (173.245.58.115)2416064699
fay.ns.cloudflare.com (108.162.192.115)2416064699
fay.ns.cloudflare.com (172.64.32.115)2416064699
fay.ns.cloudflare.com (2a06:98c1:50::ac40:2073)2416064699
fay.ns.cloudflare.com (2606:4700:50::adf5:3a73)2416064699
fay.ns.cloudflare.com (2803:f800:50::6ca2:c073)2416064699
jihoon.ns.cloudflare.com (108.162.195.233)2416064699
jihoon.ns.cloudflare.com (172.64.35.233)2416064699
jihoon.ns.cloudflare.com (162.159.44.233)2416064699
jihoon.ns.cloudflare.com (2a06:98c1:50::ac40:23e9)2416064699
jihoon.ns.cloudflare.com (2606:4700:58::a29f:2ce9)2416064699
jihoon.ns.cloudflare.com (2803:f800:50::6ca2:c3e9)2416064699

Checks

  • ✓ Serial 2416064699 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 fay.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 2416064699 is a Unix timestamp (2046-07-24 17:04 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

10 records at the apex

Found

Read from
173.245.58.115:53
TypeValueTTL
SOAfay.ns.cloudflare.com. dns.cloudflare.com. 2416064699 10000 2400 604800 18001800
NSfay.ns.cloudflare.com.86400
NSjihoon.ns.cloudflare.com.86400
A35.195.72.144300
MX0 smtp.telemaque.fr.300
TXT"dattak-defense-verification=968c9904-d369-4739-b3bf-a1abf24f456e"300
TXT"google-site-verification=K1YME5oF2K5xLQSLCKBUPlgxNW6Qt05UfHusgn0S2To"300
TXT"google-site-verification=bI4wUzO0cf-QS4_Mds6RNPyDApuUL9-EZGFIeF5vJBY"300
TXT"google-site-verification=jtWMBcxqcb-HQUT9SjU8dGU8UCAgEdkPbXHycInirgE"300
TXT"v=spf1 ip4:212.234.169.0/24 ip4:81.255.133.40/29 ip4:91.209.191.0/24 a mx ip4:91.209.191.90 mx:mailer.telemaque.fr include:_spf.google.com ~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.
  • ✓ 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