ordre-infirmiers.fr

Checked 22 October 2026, 04:40 UTC · via 8.8.8.8
iAll checks passed
28 passed 0 warnings 0 failed 7 info

Registration

info

.fr country-code · OVH · expires 2026-11-24

Found

TLD
.fr (country-code)
ICANN policies apply
no
Registrar
OVH
Registered
16 June 2009
Last changed
31 December 2025
Expires
24 November 2026
Status
active
Registry nameservers
dns110.ovh.net, ns110.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 2026-11-24 #3
    The registration is valid until 2026-11-24 (33 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

dns110.ovh.net, ns110.ovh.net

Found

Parent zone
fr
Delegation from
d.nic.fr (194.0.9.1)
NS at the parent
dns110.ovh.net, ns110.ovh.net
NS in the zone
dns110.ovh.net, ns110.ovh.net
NameserverAddressesNetwork (AS)Glue
dns110.ovh.net5.196.44.1 2001:41d0:d01:400::2AS16276 OVH - OVH SAS, FR AS16276 OVH - OVH SAS, FR-
ns110.ovh.net5.135.78.233 2001:41d0:b00:fe00::2AS16276 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: dns110.ovh.net, ns110.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

NameserverAnswerRecursionTCP / EDNSAXFRVersion
dns110.ovh.net 5.196.44.1NOERROR, 17 ms, authoritativenoyes / yesrefused-
dns110.ovh.net 2001:41d0:d01:400::2NOERROR, 17 ms, authoritativenoyes / yesrefused-
ns110.ovh.net 5.135.78.233NOERROR, 15 ms, authoritativenoyes / yesrefused-
ns110.ovh.net 2001:41d0:b00:fe00::2NOERROR, 15 ms, authoritativenoyes / yesrefused-

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 2092055572 · primary dns110.ovh.net

Found

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

Serial per nameserver

NameserverSerial
dns110.ovh.net (5.196.44.1)2092055572
dns110.ovh.net (2001:41d0:d01:400::2)2092055572
ns110.ovh.net (5.135.78.233)2092055572
ns110.ovh.net (2001:41d0:b00:fe00::2)2092055572

Checks

  • ✓ Serial 2092055572 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 dns110.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 2092055572 is a Unix timestamp (2036-04-17 14:32 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
14 November 2026

DS at the parent

Key tagAlgorithmDigestMatches a key
57050RSASHA256 (8)SHA256 28CF21AF878FFD17…yes

DNSKEY in the zone

Key tagRoleAlgorithm
57050KSK (257)RSASHA256 (8)
45039ZSK (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 57050 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: RSASHA256 (8).
  • ✓ Signatures valid until 2026-11-14 #30
    The earliest DNSKEY/SOA signature expires at 2026-11-14 08:12 UTC.
  • ✓ NSEC3 as recommended #31
    The zone uses NSEC3 with 0 iterations and no salt (RFC 9276).

Records

info

16 records at the apex

Found

Read from
5.196.44.1:53
TypeValueTTL
SOAdns110.ovh.net. tech.ovh.net. 2092055572 86400 3600 3600000 3003600
NSdns110.ovh.net.3600
NSns110.ovh.net.3600
MX1 ordreinfirmiers-fr01c.mail.protection.outlook.com.3600
TXT"/BtWNJJcV8CUEJLfzBzXByOhus+XXAAd3l6k1uMDcI0="3600
TXT"detectify-verification=ad72f253557344cebfb6a67cb0007d01"3600
TXT"_globalsign-domain-verification=2egfYRdTPzvc-0RDU-k52T88_Q8r0WYpiCWrG9OoPA"3600
TXT"xWUxoCfCkUS0jnAWNnsoiXZ1BfU="3600
TXT"d365mktkey=5p8m9p60hyrlsmlx7xzmoqe3d"3600
TXT"uuirKKfLcJ7MlLImqAM/iKhmqzR12E49X+TWoEyNJ4k="3600
TXT"v=spf1 include:spf.protection.outlook.com ip4:162.19.58.32 -all"3600
TXT"d365mktkey=6f5344rnav8iyks3rh34e8x4r"3600
TXT"QiCR29f/UZJeXkKtWbLAZipiNfSFRryQLoNDGLQlmyg="3600
TXT"detectify-verification=99a5dd4b5eea9e27dc8a1367d0816adb"3600
TXT"facebook-domain-verification=q5q6oth1y267bvih4hgsxo80580s5j"3600
TXT"_globalsign-domain-verification=-FGtH3gUrkzFZ2d4_-hlr_tVyXEK1mJHu01DZg1dWI"3600

Checks

  • ✓ TTLs within range #32
    TTLs: 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