franceolympique.com security report

Certificate, security headers, email authentication, DNS, registration, and exposed hosts — from public sources.

60risk

Elevated

Several issues worth triaging this week.

1Critical

0High

1Medium

3Low

2Info

Collected 11 hours ago9.0sfrom cache

Headers—

unavailable

Certificate Transparency205
DNS resolution41
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs64
Registration
DNS posture3
Email authentication2
Certificate
Security headers
Archived URLs
Analysis7

noteFound 205 hostnames; this runtime allows 50 outbound requests per scan, so the 21 most likely to matter were resolved.
noteCertificate inspection is unavailable in this runtime.
noteNetwork ownership lookup is unavailable in this runtime; ASN and org are omitted.
noteCDN/WAF detection is unavailable in this runtime.
noteSecurity headers did not complete (Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits). Results below are partial.
note4 hosts were identified as CDN/edge infrastructure from ASN ownership rather than a cdncheck fingerprint.

Shodan matched these CVEs against the service banners it saw on 104.21.0.86 (sso.franceolympique.com), which advertise php 7.2.30. These are version-fingerprint matches, not confirmed exploits: a distribution may have back-ported the fix while leaving the banner unchanged. Severity reflects the volume of known issues associated with this host, not a CVSS score. CVE-2024-25117 CVE-2024-3566 CVE-2022-37454 CVE-2022-31629 CVE-2022-31628 CVE-2022-4900 CVE-2020-7070 CVE-2020-7069 CVE-2020-7068 CVE-2019-11048 CVE-2017-8923 CVE-2013-2220 CVE-2007-3205
What to do
Confirm the running versions on 104.21.0.86 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2024-25117 ↗CVE-2024-3566 ↗CVE-2022-37454 ↗CVE-2022-31629 ↗CVE-2022-31628 ↗
asset: 104.21.0.86
104.21.0.86 (sso.franceolympique.com) reports php 7.2.30. Publishing precise versions lets anyone match the host against a CVE feed without probing it, which is how targets get shortlisted for mass exploitation after a new advisory lands.
What to do
Suppress version tokens in server banners (for example `ServerTokens Prod` in Apache) and keep the packages current.
asset: 104.21.0.86
dev.franceolympique.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: dev.franceolympique.com
search.dev.franceolympique.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: search.dev.franceolympique.com
Answers for this domain are not signed, so a resolver cannot tell a forged response from a real one.
What to do
Enable DNSSEC at your DNS host and publish the DS record at the registrar.
asset: franceolympique.com
Mail to this domain can be downgraded to plaintext by an on-path attacker, because senders have no way to know TLS is required.
What to do
Publish an MTA-STS policy (a TXT record plus a small HTTPS-hosted file).
asset: franceolympique.com
Any public certificate authority may issue certificates for this domain. CAA lets you name the ones allowed to.
What to do
Add a CAA record naming your CA, e.g. `0 issue "letsencrypt.org"`.
asset: franceolympique.com

✓Receives mail via 1 server
franceolympique-com.mail.protection.outlook.com
!SPFends in ~all
v=spf1 ip4:193.108.197.55 ip4:51.38.234.33 include:spf.protection.outlook.com include:spf.mailjet.com ~all
✓DMARCp=quarantine
v=DMARC1;p=quarantine;pct=100;rua=mailto:dmarc@franceolympique.com,mailto:dmarc@franceolympique.com
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
✓IPv6 (AAAA)
✓3 nameservers
nsa.perf1.fr nsb.perf1.com nsc.perf1.com

✓Registered with Nameshield SAS26.7 years old
franceolympique.com
✓Registration expiry105 days
2026-12-21
✓Transfer lock
client delete prohibited, client transfer prohibited, client update prohibited
✓3 nameservers at registry
nsa.perf1.fr nsb.perf1.com nsc.perf1.com

Address	Ports	CVEs	Edge	Network
104.20.19.32 bo.franceolympique.com +3	80443205220532082208320862087+5	0	Cloudflare~	—
172.66.164.144 bo.franceolympique.com +3	80443205220532082208320862087+5	0	Cloudflare~	—
104.21.0.86 sso.franceolympique.com +3	80443205220532082208320862087+5	13	Cloudflare~	—
172.67.223.172 sso.franceolympique.com +2	80443205220532082208320862087+5	0	Cloudflare~	—
81.92.94.54 franceolympique.com +11	80443	0	direct	—
152.89.172.56 franceolympique.com +11	80443	0	direct	—
81.92.95.55 franceolympique.com +11	80443	0	direct	—
193.108.197.55 ain.franceolympique.com +4	80443	0	direct	—
67.199.248.13 lien.franceolympique.com +3	80443	0	direct	—
67.199.248.12 lien.franceolympique.com +2	80443	0	direct	—
185.34.32.209 dev.franceolympique.com	none known	0	direct	—
185.34.32.208 search.dev.franceolympique.com	none known	0	direct	—

Archived URLs

Endpoints the Wayback Machine has kept — config files, backups, scripts. Slow to fetch, so it is here on request.

franceolympique.com security report

Elevated

Findings

Email authentication

DNS

Registration

Hosts

Hostnames