Domain report: clio.fr

Registration

info

.fr country-code · OVH · expires 2027-11-26

Found

TLD: .fr (country-code)
ICANN policies apply: no
Registrar: OVH
Registered: 7 November 1996
Last changed: 6 November 2025
Expires: 26 November 2027
Status: active
Registry nameservers: dns200.anycast.me, ns200.anycast.me
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-11-26 #3

The registration is valid until 2027-11-26 (400 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

dns200.anycast.me, ns200.anycast.me

Found

Parent zone: fr
Delegation from: d.nic.fr (194.0.9.1)
NS at the parent: dns200.anycast.me, ns200.anycast.me
NS in the zone: dns200.anycast.me, ns200.anycast.me

Nameserver	Addresses	Network (AS)	Glue
dns200.anycast.me	46.105.206.200	AS16276 OVH - OVH SAS, FR	-
ns200.anycast.me	46.105.207.200	AS16276 OVH - OVH SAS, FR	-

Checks

i

2 nameservers

Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: dns200.anycast.me, ns200.anycast.me.

#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.
i

All nameservers in one AS

All nameserver addresses are announced by one network operator (AS16276 (OVH - OVH SAS, FR): 2 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 .me

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

pass

2 of 2 addresses answer authoritatively

Found

Nameserver	Answer	Recursion	TCP / EDNS	AXFR	Version
dns200.anycast.me 46.105.206.200	NOERROR, 6 ms, authoritative	no	yes / yes	refused	-
ns200.anycast.me 46.105.207.200	NOERROR, 6 ms, authoritative	no	yes / yes	refused	-

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.
✓ No version disclosed #17

The nameservers don't reveal their software version.
✓ 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 2092476083 · primary dns200.anycast.me

Found

Primary (MNAME): dns200.anycast.me
Contact (RNAME): tech.ovh.net
Serial: 2092476083
Refresh / retry: 86400 s / 3600 s
Expire: 3600000 s
Negative TTL: 86400 s

Serial per nameserver

Nameserver	Serial
dns200.anycast.me (46.105.206.200)	2092476083
ns200.anycast.me (46.105.207.200)	2092476083

Checks

✓ Serial 2092476083 everywhere #22

All nameservers serve the same version of the zone.
✓ Timers within recommendations #23

SOA refresh 1d, retry 1h, expire 1000h, negative TTL 1d.
✓ Primary is a public nameserver #24

The primary nameserver dns200.anycast.me is one of the listed nameservers.
✓ Contact tech@ovh.net #25

The SOA RNAME tech.ovh.net means tech@ovh.net.
✓ Timestamp serial #26

The serial 2092476083 is a Unix timestamp (2036-04-22 11:21 UTC).

DNSSEC

pass

Signed, DS published at parent

Found

Validated by resolver: yes
Denial of existence: NSEC3
NSEC3: 0 iterations, 0-byte salt
Signatures valid until: 19 November 2026

DS at the parent

Key tag	Algorithm	Digest	Matches a key
37490	RSASHA256 (8)	SHA256 DFA99A7F74949E9E…	yes

DNSKEY in the zone

Key tag	Role	Algorithm
37490	KSK (257)	RSASHA256 (8)
33448	ZSK (256)	RSASHA256 (8)

Checks

✓ Signed and validated #27

The zone is signed, the parent publishes a DS record, and the resolver validates the answers.
✓ DS matches a key #28

The DS record at the parent matches a key in the zone: key tag 37490 (SHA256).
✓ Modern algorithms #29

Key algorithms: RSASHA256 (8).
✓ Signatures valid until 2026-11-19 #30

The earliest DNSKEY/SOA signature expires at 2026-11-19 05:01 UTC.
✓ NSEC3 as recommended #31

The zone uses NSEC3 with 0 iterations and no salt (RFC 9276).

Records

info

7 records at the apex

Found

Read from: 46.105.206.200:53

Type	Value	TTL
SOA	dns200.anycast.me. tech.ovh.net. 2092476083 86400 3600 3600000 86400	3600
NS	dns200.anycast.me.	3600
NS	ns200.anycast.me.	3600
A	51.68.93.23	3600
MX	1 clio-fr.mail.protection.outlook.com.	3600
TXT	"v=spf1 a mx ip4:51.15.216.106 ip4:212.47.236.178 ip4:62.210.101.111/32 ip4:178.32.13.132 ip4:51.210.184.159 ip4:51.68.93.23 ip4:51.159.77.182 ip4:51.158.120.160 ip4:163.172.161.106 ip4:163.172.188.17 ip4:212.47.254.83 ip4:51.15.238.18 " "ip4:163.172.189.74 ip4:163.172.133.124 ip4:51.15.250.209 ip4:51.15.224.142 ip4:51.15.216.39 ip4:51.15.206.242 ip4:163.172.128.17 ip4:163.172.171.211 ip4:51.15.192.170 ip4:163.172.176.114 ip4:163.172.153.230 ip4:212.47.226.222 ip4:51.15.200.113 " "ip4:212.47.227.227 ip4:163.172.188.17 include:spf.protection.outlook.com include:spf-relai.relai-smtp.net -all"	600
TXT	"google-site-verification=zck5EYCa2DSamh0xvN6zxnsC8nF6hrpPgumxfapAy54"	600

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.
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