Host

176.136.247.94

Tags: Expired certificate

As of our latest check on 2026-06-03, 176.136.247.94 (Bouygues Telecom SA, AS5410, France) had 2 open ports (80, 443) and 122 known CVEs, 4 known to be exploited.

Known CVEs on this host

2open ports
0names pointing here
122known CVEs
4known exploited

Open ports and CVEs as of our latest check of this host, 2026-06-03.

CVEs by severity: CRITICAL 20 HIGH 61 MEDIUM 39 LOW 2

A match is an indication, not proof: it is based on the software version a service reported, and fixes are often backported without changing the version. See the list

Not counted: 1 only affects a particular platform; this host's is not known (php 8.1.12). See them

Network
Bouygues Telecom SA AS5410
Open ports
80, 443 · at our latest check, 2026-06-03
Location
France FR
Hostname
176-136-247-94.abo.bbox.fr · reverse DNS, checked 2026-10-05
Route
176.128.0.0/10 · announced by Bouygues Telecom SA AS5410 RPKI valid
Organisation
Bouygues Telecom SA · Access network (cable / DSL / ISP)
Registry network
BOUYGTEL-ISP-WIRELINE · 176.136.0.0 - 176.138.255.255 · RIPE
Abuse contact
[email protected] · for BOUYGTEL-ISP-WIRELINE
First seen
2026-06-03 22:36 UTC
Last seen alive
2026-06-03 22:37 UTC
Hosted domains
No host name points here

Reputation

Not a Tor relay, not a VPN or privacy relay address, and not on a current public blocklist.

Services (2)

80/tcp HTTP Apache/2.4.54 (Win64) OpenSSL/1.1.1p PHP/8.1.12 122 CVEs first 2026-06-03 · last 2026-06-03
Status
301 Moved Permanently
Server
Apache/2.4.54 (Win64) OpenSSL/1.1.1p PHP/8.1.12
Powered by
PHP/8.1.12
Raw response
HTTP/1.1 301 Moved Permanently
Date: Wed, 03 Jun 2026 22:36:49 GMT
Server: Apache/2.4.54 (Win64) OpenSSL/1.1.1p PHP/8.1.12
X-Powered-By: PHP/8.1.12
Cache-Control: no-cache
X-Redirect-By: WordPress
Location: https://leflocondulac.com/
Content-Length: 0
Content-Type: text/html; charset=UTF-8
443/tcp TLS first 2026-06-03 · last 2026-06-03
TLS
TLSv1.2
Certificate for
leflocondulac.com
Issued by
R13
Valid
2026-03-29 → 2026-06-27
Raw response
HTTP/1.1 400 Bad Request
Date: Wed, 03 Jun 2026 22:36:49 GMT
Server: Apache/2.4.54 (Win64) OpenSSL/1.1.1p PHP/8.1.12
Content-Length: 469
Connection: close
Content-Type: text/html; charset=iso-8859-1

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>400 Bad Request</title>
</head><body>
<h1>Bad Request</h1>
<p>Your browser sent a request that this server could not understand.<br />
Reason: You're speaking plain HTTP to an SSL-enabled server port.<br />
 Instead use the HTTPS scheme to access this URL, please.<br />
</p>
<hr>
<address>Apache/2.4.54 (Win64) OpenSSL/1.1.1p PHP/8.1.12 Server at www.example.com Port 443</address>
</body></html>

Vulnerabilities

Only affects certain platforms (1)

These CVEs only apply when the software runs on a particular platform (for example Windows), and this host's platform is not known. They are not counted.

CVEs by severity: CRITICAL 1

CVESoftware
CVE-2022-31631 CRITICAL 9.1 php 8.1.12 · port 80

Port history

Every port that has answered a connection on this address, and when. A port is listed as open above only when a service was identified on it. Times are UTC.