casinodeparis.fr

Checked 22 October 2026, 02:07 UTC · via 8.8.8.8
!Passed with warnings
25 passed 3 warnings 0 failed 3 info

Registration

info

.fr country-code · NAMESHIELD · expires 2027-02-03

Found

TLD
.fr (country-code)
ICANN policies apply
no
Registrar
NAMESHIELD
Registered
7 August 1997
Last changed
6 February 2026
Expires
3 February 2027
Status
client transfer prohibited
Registry nameservers
ns1-02.azure-dns.com, ns2-02.azure-dns.net, ns3-02.azure-dns.org, ns4-02.azure-dns.info
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-02-03 #3
    The registration is valid until 2027-02-03 (104 days).
  • ✓ Transfer locked #4
    Registry status: client transfer prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

info

ns1-02.azure-dns.com, ns2-02.azure-dns.net, ns3-02.azure-dns.org, ns4-02.azure-dns.info

Found

Parent zone
fr
Delegation from
d.nic.fr (194.0.9.1)
NS at the parent
ns1-02.azure-dns.com, ns2-02.azure-dns.net, ns3-02.azure-dns.org, ns4-02.azure-dns.info
NS in the zone
ns1-02.azure-dns.com, ns2-02.azure-dns.net, ns3-02.azure-dns.org, ns4-02.azure-dns.info
NameserverAddressesNetwork (AS)Glue
ns1-02.azure-dns.com13.107.236.2 2603:1061:0:700::2AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-
ns2-02.azure-dns.net150.171.21.2 2620:1ec:8ec:700::2AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-
ns3-02.azure-dns.org204.14.183.2 2a01:111:4000:700::2AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-
ns4-02.azure-dns.info208.84.5.2 2620:1ec:bda:700::2AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-

Checks

  • ✓ 4 nameservers #6
    Delegated to ns1-02.azure-dns.com, ns2-02.azure-dns.net, ns3-02.azure-dns.org, ns4-02.azure-dns.info.
  • ✓ 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 4 IPv4 /24s and 4 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS8075 (MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US): 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
  • ✓ Nameserver names under 4 TLDs #12
    Nameserver names use the TLDs .com, .info, .net, .org.
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

warn

8 of 8 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1-02.azure-dns.com 13.107.236.2NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns1-02.azure-dns.com 2603:1061:0:700::2NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns2-02.azure-dns.net 150.171.21.2NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns2-02.azure-dns.net 2620:1ec:8ec:700::2NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns3-02.azure-dns.org 204.14.183.2NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns3-02.azure-dns.org 2a01:111:4000:700::2NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns4-02.azure-dns.info 208.84.5.2NOERROR, 4 ms, authoritativenoyes / yesrefusedKnot DNS 3.1.2.1770717641.d6b376aff
ns4-02.azure-dns.info 2620:1ec:bda:700::2NOERROR, 4 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.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns4-02.azure-dns.info: "Knot DNS 3.1.2.1770717641.d6b376aff". Hide or replace the version string.
    #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 2018032011 · primary ns1-02.azure-dns.com

Found

Primary (MNAME)
ns1-02.azure-dns.com
Contact (RNAME)
admin.validname.com
Serial
2018032011
Refresh / retry
10800 s / 600 s
Expire
1209600 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns1-02.azure-dns.com (13.107.236.2)2018032011
ns1-02.azure-dns.com (2603:1061:0:700::2)2018032011
ns2-02.azure-dns.net (150.171.21.2)2018032011
ns2-02.azure-dns.net (2620:1ec:8ec:700::2)2018032011
ns3-02.azure-dns.org (204.14.183.2)2018032011
ns3-02.azure-dns.org (2a01:111:4000:700::2)2018032011
ns4-02.azure-dns.info (208.84.5.2)2018032011
ns4-02.azure-dns.info (2620:1ec:bda:700::2)2018032011

Checks

  • ✓ Serial 2018032011 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 10m, expire 14d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1-02.azure-dns.com is one of the listed nameservers.
  • ✓ Contact admin@validname.com #25
    The SOA RNAME admin.validname.com means admin@validname.com.
  • ✓ Date-based serial #26
    The serial 2018032011 follows the YYYYMMDDnn convention (2018-03-20).

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

warn

24 records at the apex

Found

Read from
13.107.236.2:53
TypeValueTTL
SOAns1-02.azure-dns.com. admin.validname.com. 2018032011 10800 600 1209600 360010
NSns1-02.azure-dns.com.10
NSns2-02.azure-dns.net.10
NSns3-02.azure-dns.org.10
NSns4-02.azure-dns.info.10
A185.128.238.1110
A185.128.238.1210
A185.128.238.1310
A185.128.238.1410
MX0 casinodeparis-fr.mail.protection.outlook.com.10
TXT"v=spf1 ip4:213.41.78.0/24 a:afmail.lagardere.fr include:spf.tickandlive.com include:spf.hubber.fr include:amazonses.com include:spf.protection.outlook.com mx -all"10
TXT"MS=ms43010078"10
TXT"_globalsign-domain-verification=9IIJ8UroTBE93bI4MWIFNwZtyvzD86yVQkk7Zmw9d6"10
TXT"globalsign-domain-verification=pXM6xeuY1jK7nBGab5lLMtd1HI3N8PXc2zEBC7QGGQ"10
TXT"MS=ms60937014"10
TXT"docusign=0580b098-8645-4324-9f92-0e66c1822eae"10
TXT"QuoVadis=87126e11-3f5e-4d7c-9efc-a8235cea29dc"10
TXT"asn-verification=b817102b20647f229d6c45a8a2ff6b6c1d8246c8c2dff191978eafb1c54a3333"10
TXT"QuoVadis=6e7f0f3d-a7bc-4690-9810-9e8535b8044c"10
TXT"tngw2ll5z7wmb0m3nvc9j7hk8cj9xvqd"10
TXT"google-site-verification=QN0VopMx4AsWq6gMZmzFX6DGCWkpmiwlCvTTUBCdGFU"10
TXT"_1lgqzcgip10x8iq2s785qhvburojh91"10
TXT"_yngju6xx0jx3d3h2o9th90ajeqr1gpa"10
TXT"_e8ufa2fcrmw8zbwf3c3g1vxbloev3la"10

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (10s), MX (10s), NS (10s). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1h and in the zone 10s; resolvers may use either.
    #32
  • ✓ 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