data-dock.fr

Checked 22 October 2026, 02:30 UTC · via 8.8.8.8
✗Problems found
21 passed 1 warning 1 failed 8 info

Registration

fail

.fr country-code · OVH · expires 2026-10-27

Found

TLD
.fr (country-code)
ICANN policies apply
no
Registrar
OVH
Registered
27 October 2016
Last changed
5 January 2026
Expires
27 October 2026
Status
active
Registry nameservers
pns1.cloudns.net, pns2.cloudns.net, pns3.cloudns.net, pns4.cloudns.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 in 5 days
    The registration expires on 2026-10-27. Renew it now or enable auto-renewal.
    #3
  • 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

pns1.cloudns.net, pns2.cloudns.net, pns3.cloudns.net, pns4.cloudns.net

Found

Parent zone
fr
Delegation from
d.nic.fr (194.0.9.1)
NS at the parent
pns1.cloudns.net, pns2.cloudns.net, pns3.cloudns.net, pns4.cloudns.net
NS in the zone
pns1.cloudns.net, pns2.cloudns.net, pns3.cloudns.net, pns4.cloudns.net
NameserverAddressesNetwork (AS)Glue
pns1.cloudns.net185.136.96.111 2a06:fb00:1::1:111AS203391 CLOUDNSNET - Cloud DNS Ltd, BG AS203391 CLOUDNSNET - Cloud DNS Ltd, BG-
pns2.cloudns.net185.136.97.111 2a06:fb00:1::2:111AS203391 CLOUDNSNET - Cloud DNS Ltd, BG AS203391 CLOUDNSNET - Cloud DNS Ltd, BG-
pns3.cloudns.net185.136.98.111 2a06:fb00:1::3:111AS203391 CLOUDNSNET - Cloud DNS Ltd, BG AS203391 CLOUDNSNET - Cloud DNS Ltd, BG-
pns4.cloudns.net185.136.99.111 2a06:fb00:1::4:111AS203391 CLOUDNSNET - Cloud DNS Ltd, BG AS203391 CLOUDNSNET - Cloud DNS Ltd, BG-

Checks

  • ✓ 4 nameservers #6
    Delegated to pns1.cloudns.net, pns2.cloudns.net, pns3.cloudns.net, pns4.cloudns.net.
  • ✓ 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.
  • i
    One address family in one network
    all IPv6 addresses are in 2a06:fb00:1::/48, while the other address family is spread over several networks.
    #10
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS203391 (CLOUDNSNET - Cloud DNS Ltd, BG): 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
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

info

8 of 8 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
pns1.cloudns.net 185.136.96.111NOERROR, 5 ms, authoritativenoyes / yesrefusedde3-8
pns1.cloudns.net 2a06:fb00:1::1:111NOERROR, 5 ms, authoritativenoyes / yesrefusedde3-8
pns2.cloudns.net 185.136.97.111NOERROR, 4 ms, authoritativenoyes / yesrefusedde3-8
pns2.cloudns.net 2a06:fb00:1::2:111NOERROR, 4 ms, authoritativenoyes / yesrefusedde3-8
pns3.cloudns.net 185.136.98.111NOERROR, 5 ms, authoritativenoyes / yesrefusedde3-8
pns3.cloudns.net 2a06:fb00:1::3:111NOERROR, 4 ms, authoritativenoyes / yesrefusedde3-8
pns4.cloudns.net 185.136.99.111NOERROR, 4 ms, authoritativenoyes / yesrefusedde3-8
pns4.cloudns.net 2a06:fb00:1::4:111NOERROR, 4 ms, authoritativenoyes / yesrefusedde3-8

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.
  • i
    Identifying string disclosed
    These nameservers answer version queries with a string that is not a version number: pns1.cloudns.net: "de3-8"; pns2.cloudns.net: "de3-8"; pns3.cloudns.net: "de3-8"; pns4.cloudns.net: "de3-8".
    #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 2026070801 · primary pns1.cloudns.net

Found

Primary (MNAME)
pns1.cloudns.net
Contact (RNAME)
support.cloudns.net
Serial
2026070801
Refresh / retry
7200 s / 1800 s
Expire
1209600 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
pns1.cloudns.net (185.136.96.111)2026070801
pns1.cloudns.net (2a06:fb00:1::1:111)2026070801
pns2.cloudns.net (185.136.97.111)2026070801
pns2.cloudns.net (2a06:fb00:1::2:111)2026070801
pns3.cloudns.net (185.136.98.111)2026070801
pns3.cloudns.net (2a06:fb00:1::3:111)2026070801
pns4.cloudns.net (185.136.99.111)2026070801
pns4.cloudns.net (2a06:fb00:1::4:111)2026070801

Checks

  • ✓ Serial 2026070801 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 2h, retry 30m, expire 14d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver pns1.cloudns.net is one of the listed nameservers.
  • ✓ Contact support@cloudns.net #25
    The SOA RNAME support.cloudns.net means support@cloudns.net.
  • ✓ Date-based serial #26
    The serial 2026070801 follows the YYYYMMDDnn convention (2026-07-08).

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.136.96.111:53
TypeValueTTL
SOApns1.cloudns.net. support.cloudns.net. 2026070801 7200 1800 1209600 36003600
NSpns1.cloudns.net.3600
NSpns2.cloudns.net.3600
NSpns3.cloudns.net.3600
NSpns4.cloudns.net.3600
A46.18.192.18300
MX10 mx3.mail.ovh.net.3600
MX1 mx4.mail.ovh.net.3600
TXT"v=spf1 include:spf.sendinblue.com ip4:178.32.124.207 ip4:91.121.53.175 ip4:178.32.119.228 mx include:mx.ovh.com ~all"3600
TXT"sendinblue-code:3bd0778f77d8f1c472011978ab138f0c"3600

Checks

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