silae.fr

Checked 22 October 2026, 05:13 UTC · via 8.8.8.8
✗Problems found
22 passed 3 warnings 1 failed 5 info

Registration

fail

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

Found

TLD
.fr (country-code)
ICANN policies apply
no
Registrar
OVH
Registered
30 October 2008
Last changed
30 November 2025
Expires
30 October 2026
Status
active
Registry nameservers
ns1-04.azure-dns.com, ns2-04.azure-dns.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 8 days
    The registration expires on 2026-10-30. 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

warn

ns1-04.azure-dns.com, ns2-04.azure-dns.net

Found

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

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1-04.azure-dns.com, ns2-04.azure-dns.net.
    #6
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only in the zone: ns3-04.azure-dns.org, ns4-04.azure-dns.info. ns1-04.azure-dns.com, ns2-04.azure-dns.net, ns3-04.azure-dns.org, ns4-04.azure-dns.info report NS ns1-04.azure-dns.com ns2-04.azure-dns.net ns3-04.azure-dns.org ns4-04.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 2 TLDs #12
    Nameserver names use the TLDs .com, .net.
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

warn

8 of 8 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1-04.azure-dns.com 13.107.236.4NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns1-04.azure-dns.com 2603:1061:0:700::4NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns2-04.azure-dns.net 150.171.21.4NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns2-04.azure-dns.net 2620:1ec:8ec:700::4NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns3-04.azure-dns.org 204.14.183.4NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns3-04.azure-dns.org 2a01:111:4000:700::4NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns4-04.azure-dns.info 208.84.5.4NOERROR, 5 ms, authoritativenoyes / yesrefusedKnot DNS 3.1.2.1770717641.d6b376aff
ns4-04.azure-dns.info 2620:1ec:bda:700::4NOERROR, 5 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-04.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-04.azure-dns.com

Found

Primary (MNAME)
ns1-04.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-04.azure-dns.com (13.107.236.4)1
ns1-04.azure-dns.com (2603:1061:0:700::4)1
ns2-04.azure-dns.net (150.171.21.4)1
ns2-04.azure-dns.net (2620:1ec:8ec:700::4)1
ns3-04.azure-dns.org (204.14.183.4)1
ns3-04.azure-dns.org (2a01:111:4000:700::4)1
ns4-04.azure-dns.info (208.84.5.4)1
ns4-04.azure-dns.info (2620:1ec:bda:700::4)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-04.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

info

29 records at the apex

Found

Read from
13.107.236.4:53
TypeValueTTL
SOAns1-04.azure-dns.com. azuredns-hostmaster.microsoft.com. 1 3600 300 2419200 3003600
NSns1-04.azure-dns.com.172800
NSns2-04.azure-dns.net.172800
NSns3-04.azure-dns.org.172800
NSns4-04.azure-dns.info.172800
A20.188.41.1053600
MX0 silae-fr.mail.protection.outlook.com.3600
TXT"google-site-verification=VxHCI8bgrZPTI7BJ37yA-6T88xGfixa2-xubgNQ8dHQ"300
TXT"arsen-verification=1fe30e3ef29ae499743d108899a16e7414f39993971f469c74eec6c15b7d4353"300
TXT"google-site-verification=1gbSp4YgdVi5c5d152qUr0iCZe8-nAn5CwD8oWCdfDo"300
TXT"google-site-verification=aPjOZx6rbjKnsFRv8xeS9PnpQtEJrprPYsPFU5ePLlU"300
TXT"v=spf1 mx include:mailgun.org ip4:159.26.176.101 ip4:46.18.209.195 ip4:159.183.227.94 ip4:93.93.188.175 ip4:185.92.36.65 ip4:159.183.184.231 ip4:31.172.232.198 ip4:185.92.38.235 ip4:149.72.122.246 ip4:159.183.110.7 ip4:159.183.225.113 ip4:159.183.85.167 i" "p4:167.89.2.56 ip4:185.92.37.57 ip4:185.92.38.236 ip4:195.25.30.223 ip4:159.183.226.76 ip4:159.183.231.237 include:spf.protection.outlook.com include:docebosaas.com include:mail.zendesk.com include:2678922.spf07.hubspotemail.net include:aspmx.pardot.com " "include:spf.mailjet.com ~all"300
TXT"rplhq4yktw7zj0sv1p0s4gt3tydnl4d8"300
TXT"apple-domain-verification=KSRhJ7OuRX3URlQn"300
TXT"sending_domain996182=fc6180a6b6740c61a0a8c3ac52e41af6a33ec27b1653567787b2870f7b9232c0"300
TXT"teamviewer-sso-verification=a0c0f64b1b3d44c2935522736854581d"300
TXT"solBJ5V0=8694b7b1909785637de9041116c684db"300
TXT"jamf-site-verification=daAkMFP02zN5XF2P88Tc9w"300
TXT"_cdv6dmn49fteb7ql2d3tgchl6ayh1fm"300
TXT"openai-domain-verification=dv-ejg6F97WdSRJNQg6KfG8A2vB"300
TXT"lovable_verification=wVd4v8UfJuGSehsWBit9"300
TXT"parallels-domain-verification=d38df354aa47495b96915882a64219a339f60662d16448f486713aa87a740a87"300
TXT"detectify-verification=6efe83acff5ae206a4b2b568ab6aaeca"300
TXT"anthropic-domain-verification-4bgg7h=BPm7BgUwuK467fevsA1lnafmt"300
TXT"brevo-code:483a576be677804946b45d4703c268ff"300
TXT"hpe-greenlake-domain-verification=57696f44446d77644b4c354c7a4179766e336937415a6d43324a6631576a7372"300
TXT"_9v54ie6fqcqxcyoezbbz3kl599iw4yc"300
TXT"notion-domain-verification=SNVW8KklNJbPRhRC6rdyFHATzkWd8zKW3fmtDLLN0iI"300
TXT"cloudflare_dashboard_sso=f45007276001b4676846fe4baafbb796"300

Checks

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