Domain report: lelephant-larevue.fr

Registration

info

.fr country-code · OVH · expires 2033-05-24

Found

TLD: .fr (country-code)
ICANN policies apply: no
Registrar: OVH
Registered: 24 May 2012
Last changed: 25 August 2025
Expires: 24 May 2033
Status: active
Registry nameservers: dns101.ovh.net, ns101.ovh.net
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 2033-05-24 #3

The registration is valid until 2033-05-24 (2406 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

dns101.ovh.net, ns101.ovh.net

Found

Parent zone: fr
Delegation from: d.nic.fr (194.0.9.1)
NS at the parent: dns101.ovh.net, ns101.ovh.net
NS in the zone: dns101.ovh.net, ns101.ovh.net

Nameserver	Addresses	Network (AS)	Glue
dns101.ovh.net	5.196.38.125 2001:41d0:d00:fb00::2	AS16276 OVH - OVH SAS, FR AS16276 OVH - OVH SAS, FR	-
ns101.ovh.net	5.135.53.37 2001:41d0:b00:f500::2	AS16276 OVH - OVH SAS, FR AS16276 OVH - OVH SAS, FR	-

Checks

i

2 nameservers

Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: dns101.ovh.net, ns101.ovh.net.

#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 2 IPv6 /48s.
i

All nameservers in one AS

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

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

pass

4 of 4 addresses answer authoritatively

Found

Nameserver	Answer	Recursion	TCP / EDNS	AXFR	Version
dns101.ovh.net 5.196.38.125	NOERROR, 16 ms, authoritative	no	yes / yes	refused	-
dns101.ovh.net 2001:41d0:d00:fb00::2	NOERROR, 16 ms, authoritative	no	yes / yes	refused	-
ns101.ovh.net 5.135.53.37	NOERROR, 15 ms, authoritative	no	yes / yes	refused	-
ns101.ovh.net 2001:41d0:b00:f500::2	NOERROR, 16 ms, authoritative	no	yes / yes	refused	-

Checks

✓ All respond #14

All 4 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 2092625468 · primary dns101.ovh.net

Found

Primary (MNAME): dns101.ovh.net
Contact (RNAME): tech.ovh.net
Serial: 2092625468
Refresh / retry: 86400 s / 3600 s
Expire: 3600000 s
Negative TTL: 300 s

Serial per nameserver

Nameserver	Serial
dns101.ovh.net (5.196.38.125)	2092625468
dns101.ovh.net (2001:41d0:d00:fb00::2)	2092625468
ns101.ovh.net (5.135.53.37)	2092625468
ns101.ovh.net (2001:41d0:b00:f500::2)	2092625468

Checks

✓ Serial 2092625468 everywhere #22

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

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

The primary nameserver dns101.ovh.net 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 2092625468 is a Unix timestamp (2036-04-24 04:51 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: 20 November 2026

DS at the parent

Key tag	Algorithm	Digest	Matches a key
44725	RSASHA256 (8)	SHA256 5D3FFF1378068191…	yes

DNSKEY in the zone

Key tag	Role	Algorithm
12418	ZSK (256)	RSASHA256 (8)
12088	ZSK (256)	RSASHA256 (8)
44725	KSK (257)	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 44725 (SHA256).
✓ Modern algorithms #29

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

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

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

Records

warn

9 records at the apex

Found

Read from: 5.196.38.125:53

Type	Value	TTL
SOA	dns101.ovh.net. tech.ovh.net. 2092625468 86400 3600 3600000 300	300
NS	ns101.ovh.net.	300
NS	dns101.ovh.net.	300
A	37.61.245.77	60
MX	0 lelephantlarevue-fr02c.mail.protection.outlook.com.	300
TXT	"MS=ms29579171"	300
TXT	"brevo-code:bfce538d98a608806327de44eab47854"	300
TXT	"v=spf1 include:spf.mailjet.com ?all"	300
TXT	"google-site-verification=AqiMCvI22k28lr4kMcMGJPjXiOA6HGVKA4eTjgJiPkM"	300

Checks

!

Very low TTLs

These records have a TTL below 5m, causing extra queries and slower lookups: A (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1h and in the zone 5m; resolvers may use either.

#32
✓ 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