ramsaygds.fr

Checked 22 October 2026, 04:57 UTC · via 8.8.8.8
!Passed with warnings
21 passed 3 warnings 0 failed 7 info

Registration

info

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

Found

TLD
.fr (country-code)
ICANN policies apply
no
Registrar
OVH
Registered
11 June 2015
Last changed
10 May 2026
Expires
11 June 2027
Status
active
Registry nameservers
ns01.ramsaysante.fr, ns02.ramsaysante.fr
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-06-11 #3
    The registration is valid until 2027-06-11 (232 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

ns01.ramsaysante.fr, ns02.ramsaysante.fr

Found

Parent zone
fr
Delegation from
d.nic.fr (194.0.9.1)
NS at the parent
ns01.ramsaysante.fr, ns02.ramsaysante.fr
NS in the zone
ns01.ramsaysante.fr, ns02.ramsaysante.fr
NameserverAddressesNetwork (AS)Glue
ns01.ramsaysante.fr91.213.180.68AS29104 THALESGROUP-AS - Thales Services Numeriques SAS, FR91.213.180.68
ns02.ramsaysante.fr91.213.180.69AS29104 THALESGROUP-AS - Thales Services Numeriques SAS, FR91.213.180.69

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns01.ramsaysante.fr, ns02.ramsaysante.fr.
    #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 one network
    all IPv4 addresses are in 91.213.180.0/24. A single network failure takes all nameservers down; RFC 2182 recommends topologically separate networks (anycast setups are an exception).
    #10
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS29104 (THALESGROUP-AS - Thales Services Numeriques 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 .fr
    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

info

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns01.ramsaysante.fr 91.213.180.68NOERROR, 14 ms, authoritativenoyes / yesrefusednot that much to say here ;) !
ns02.ramsaysante.fr 91.213.180.69NOERROR, 14 ms, authoritativenoyes / yesrefusednot that much to say here ;) !

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.
  • i
    Identifying string disclosed
    These nameservers answer version queries with a string that is not a version number: ns01.ramsaysante.fr: "not that much to say here ;) !"; ns02.ramsaysante.fr: "not that much to say here ;) !".
    #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 2026092901 · primary ns01.ramsaysante.fr

Found

Primary (MNAME)
ns01.ramsaysante.fr
Contact (RNAME)
ien-dsi-exploitation.ramsaygds.fr
Serial
2026092901
Refresh / retry
1800 s / 900 s
Expire
1209600 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns01.ramsaysante.fr (91.213.180.68)2026092901
ns02.ramsaysante.fr (91.213.180.69)2026092901

Checks

  • ✓ Serial 2026092901 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 30m, retry 15m, expire 14d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns01.ramsaysante.fr is one of the listed nameservers.
  • ✓ Contact ien-dsi-exploitation@ramsaygds.fr #25
    The SOA RNAME ien-dsi-exploitation.ramsaygds.fr means ien-dsi-exploitation@ramsaygds.fr.
  • ✓ Date-based serial #26
    The serial 2026092901 follows the YYYYMMDDnn convention (2026-09-29).

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
91.213.180.68:53
TypeValueTTL
SOAns01.ramsaysante.fr. ien-dsi-exploitation.ramsaygds.fr. 2026092901 1800 900 1209600 36003600
NSns02.ramsaysante.fr.3600
NSns01.ramsaysante.fr.3600
A62.240.227.1243600
MX10 ramsaygds-fr.mail.protection.outlook.com.300
TXT"hsrwcsj83cymlkc78sbl15pjwd3s0f41"3600
TXT"google-site-verification=czHpmpstx9r3oeXeIP4bXr0IUCr3rrNVqJSvgTSTMlI"3600
TXT"MS=ms54821623"3600
TXT"v=spf1 ip4:91.213.180.104 ip4:91.213.180.105 include:spf.protection.outlook.com" " a:cgds.typhon.net a:mail.grita.fr include:spf.mailjet.com include:_spf.sidetrade.net include:spf.postal.sensiwave.com include:_spf.salesforce.com include:oktaemail.ramsaysante.fr -all"3600
TXT"7Zb47QdM0eF9jWtyZlzhHUEJ24c="3600

Checks

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