publicsenat.fr

Checked 22 October 2026, 04:55 UTC · via 8.8.8.8
!Passed with warnings
20 passed 3 warnings 0 failed 8 info

Registration

info

.fr country-code · OVH · expires 2027-07-24

Found

TLD
.fr (country-code)
ICANN policies apply
no
Registrar
OVH
Registered
1 October 2000
Last changed
31 August 2026
Expires
24 July 2027
Status
active
Registry nameservers
ns1.typhon.net, ns2.typhon.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 2027-07-24 #3
    The registration is valid until 2027-07-24 (275 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

ns1.typhon.net, ns2.typhon.net

Found

Parent zone
fr
Delegation from
d.nic.fr (194.0.9.1)
NS at the parent
ns1.typhon.net, ns2.typhon.net
NS in the zone
ns0.clara.net, ns1.claranet.com, ns2.clara.net
NameserverAddressesNetwork (AS)Glue
ns0.clara.net (zone only)185.77.72.10 2001:67c:1088::10AS8426 CLARANET-AS - Claranet Limited, GB AS8426 CLARANET-AS - Claranet Limited, GB-
ns1.claranet.com (zone only)185.77.72.51 2001:67c:1088::51AS8426 CLARANET-AS - Claranet Limited, GB AS8426 CLARANET-AS - Claranet Limited, GB-
ns1.typhon.net (parent only)185.77.72.17AS8426 CLARANET-AS - Claranet Limited, GB-
ns2.clara.net (zone only)195.245.201.35 2001:a88:0:fffa::3AS8426 CLARANET-AS - Claranet Limited, GB AS8426 CLARANET-AS - Claranet Limited, GB-
ns2.typhon.net (parent only)185.77.72.18AS8426 CLARANET-AS - Claranet Limited, GB-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.typhon.net, ns2.typhon.net.
    #6
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only at the parent: ns1.typhon.net, ns2.typhon.net; only in the zone: ns0.clara.net, ns1.claranet.com, ns2.clara.net. ns0.clara.net, ns1.claranet.com, ns1.typhon.net, ns2.clara.net, ns2.typhon.net report NS ns0.clara.net ns1.claranet.com ns2.clara.net.
    #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 2 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS8426 (CLARANET-AS - Claranet Limited, GB): 8 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
  • i
    Partly IPv6
    These nameservers have no IPv6 address: ns1.typhon.net, ns2.typhon.net.
    #13

Nameservers

pass

8 of 8 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns0.clara.net 185.77.72.10NOERROR, 3 ms, authoritativenoyes / yesrefused-
ns0.clara.net 2001:67c:1088::10NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns1.claranet.com 185.77.72.51NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns1.claranet.com 2001:67c:1088::51NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns1.typhon.net 185.77.72.17NOERROR, 3 ms, authoritativenoyes / yesrefused-
ns2.clara.net 195.245.201.35NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns2.clara.net 2001:a88:0:fffa::3NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns2.typhon.net 185.77.72.18NOERROR, 3 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 8 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

warn

serial 2026040110 · primary ns0.clara.net

Found

Primary (MNAME)
ns0.clara.net
Contact (RNAME)
hostmaster.clara.net
Serial
2026040110
Refresh / retry
172800 s / 3600 s
Expire
1728000 s
Negative TTL
172800 s

Serial per nameserver

NameserverSerial
ns0.clara.net (185.77.72.10)2026040110
ns0.clara.net (2001:67c:1088::10)2026040110
ns1.claranet.com (185.77.72.51)2026040110
ns1.claranet.com (2001:67c:1088::51)2026040110
ns1.typhon.net (185.77.72.17)2026040110
ns2.clara.net (195.245.201.35)2026040110
ns2.clara.net (2001:a88:0:fffa::3)2026040110
ns2.typhon.net (185.77.72.18)2026040110

Checks

  • ✓ Serial 2026040110 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    refresh 2d is outside 20m–1d; negative caching TTL (minimum) 2d is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 2d, retry 1h, expire 20d, negative TTL 2d.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns0.clara.net is one of the listed nameservers.
  • ✓ Contact hostmaster@clara.net #25
    The SOA RNAME hostmaster.clara.net means hostmaster@clara.net.
  • ✓ Date-based serial #26
    The serial 2026040110 follows the YYYYMMDDnn convention (2026-04-01).

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
185.77.72.10:53
TypeValueTTL
SOAns0.clara.net. hostmaster.clara.net. 2026040110 172800 3600 1728000 1728003600
NSns1.claranet.com.600
NSns2.clara.net.600
NSns0.clara.net.600
A79.99.39.90300
MX10 publicsenat.mail.protection.outlook.com.600
TXT"ZOOM_verify_wRzgtSfUTImrgRraYyIOMQ"600
TXT"v=spf1 include:spf.mailjet.com ip4:213.41.17.178 include:spf.protection.outlook.com include:spf.eu.exclaimer.net ?all"600
TXT"google-site-verification=tWt9aob8GLLKPdlxuCmUc95Nb0myQoCrKMnyzNiV-GY"600
TXT"facebook-domain-verification=72quuzoqv2a7yyzuqjawt3uv09shm0"600

Checks

  • ✓ TTLs within range #32
    TTLs: A 5m, MX 10m, NS 10m. The NS TTL at the parent is 1h and in the zone 10m; 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