assuropoil.fr

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

Registration

info

.fr country-code · FRENCH CONNEXION · expires 2027-02-11

Found

TLD
.fr (country-code)
ICANN policies apply
no
Registrar
FRENCH CONNEXION
Registered
11 February 2010
Last changed
24 October 2025
Expires
11 February 2027
Status
active
Registry nameservers
ns1-06.azure-dns.com, ns2-06.azure-dns.net, ns3-06.azure-dns.org
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-11 #3
    The registration is valid until 2027-02-11 (112 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-06.azure-dns.com, ns2-06.azure-dns.net, ns3-06.azure-dns.org

Found

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

Checks

  • ✓ 3 nameservers #6
    Delegated to ns1-06.azure-dns.com, ns2-06.azure-dns.net, ns3-06.azure-dns.org.
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only in the zone: ns4-06.azure-dns.info. ns1-06.azure-dns.com, ns2-06.azure-dns.net, ns3-06.azure-dns.org, ns4-06.azure-dns.info report NS ns1-06.azure-dns.com ns2-06.azure-dns.net ns3-06.azure-dns.org ns4-06.azure-dns.info.
    #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 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 3 TLDs #12
    Nameserver names use the TLDs .com, .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-06.azure-dns.com 13.107.236.6NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns1-06.azure-dns.com 2603:1061:0:700::6NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns2-06.azure-dns.net 150.171.21.6NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns2-06.azure-dns.net 2620:1ec:8ec:700::6NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns3-06.azure-dns.org 204.14.183.6NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns3-06.azure-dns.org 2a01:111:4000:700::6NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns4-06.azure-dns.info 208.84.5.6NOERROR, 5 ms, authoritativenoyes / yesrefusedKnot DNS 3.1.2.1770717641.d6b376aff
ns4-06.azure-dns.info 2620:1ec:bda:700::6NOERROR, 6 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-06.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 1 · primary ns1-06.azure-dns.com

Found

Primary (MNAME)
ns1-06.azure-dns.com
Contact (RNAME)
azuredns-hostmaster.microsoft.com
Serial
1
Refresh / retry
3600 s / 300 s
Expire
2419200 s
Negative TTL
300 s

Serial per nameserver

NameserverSerial
ns1-06.azure-dns.com (13.107.236.6)1
ns1-06.azure-dns.com (2603:1061:0:700::6)1
ns2-06.azure-dns.net (150.171.21.6)1
ns2-06.azure-dns.net (2620:1ec:8ec:700::6)1
ns3-06.azure-dns.org (204.14.183.6)1
ns3-06.azure-dns.org (2a01:111:4000:700::6)1
ns4-06.azure-dns.info (208.84.5.6)1
ns4-06.azure-dns.info (2620:1ec:bda:700::6)1

Checks

  • ✓ Serial 1 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1h, retry 5m, expire 28d, negative TTL 5m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1-06.azure-dns.com is one of the listed nameservers.
  • ✓ Contact azuredns-hostmaster@microsoft.com #25
    The SOA RNAME azuredns-hostmaster.microsoft.com means azuredns-hostmaster@microsoft.com.
  • ✓ Counter serial #26
    The serial 1 is a plain counter.

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

pass

19 records at the apex

Found

Read from
13.107.236.6:53
TypeValueTTL
SOAns1-06.azure-dns.com. azuredns-hostmaster.microsoft.com. 1 3600 300 2419200 3003600
NSns1-06.azure-dns.com.172800
NSns2-06.azure-dns.net.172800
NSns3-06.azure-dns.org.172800
NSns4-06.azure-dns.info.172800
A20.111.1.9300
MX10 assuropoil-fr.mail.protection.outlook.com.300
TXT"MS=ms13441950"300
TXT"v=spf1 ip4:176.162.176.74 include:spf.protection.outlook.com include:mailgun.org -all"300
TXT"google-site-verification=ap0EYa9Wqw1mNdTBwexaYRZ4MvNmZ_---7TMxnw1wRo"300
TXT"zscaler-verification-44864592-8192025-K3whIOdfc"300
CAA0 issuewild "letsencrypt.org"3600
CAA0 issue "amazonaws.com"3600
CAA0 issue "amazon.com"3600
CAA0 issue "letsencrypt.org"3600
CAA0 issue "awstrust.com"3600
CAA0 issue "thawte.com"3600
CAA0 issue "sectigo.com"3600
CAA0 issue "amazontrust.com"3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 5m, MX 5m, NS 2d. The NS TTL at the parent is 1h and in the zone 2d; resolvers may use either.
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • ✓ No wildcard #34
    Names that don't exist return NXDOMAIN.
  • ✓ CAA restricts issuance #35
    Certificates may be issued by: letsencrypt.org, amazonaws.com, amazon.com, awstrust.com, thawte.com, sectigo.com, amazontrust.com.