198.244.236.48 — 2 open ports, 0 known CVEs, network OVH SAS

Known CVEs on this host

2open ports

0names pointing here

0known CVEs

0known exploited

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

No known CVEs on this host.

Network: OVH SAS AS16276
Open ports: 80, 443 · at our latest check, 2026-06-07
Location: United Kingdom GB
Hostname: glowingeyegames.com · reverse DNS, checked 2026-10-05
Route: 198.244.128.0/17 · announced by OVH SAS AS16276 RPKI valid
Organisation: OVHcloud · Content / hosting
Registry network: OVH_423310909 · 198.244.236.48 - 198.244.236.63 · RIPE
Abuse contact: [email protected] · for OVH_423310909
First seen: 2026-06-07 03:29 UTC
Last seen alive: 2026-06-07 03:31 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 first 2026-06-07 · last 2026-06-07

Status: 301 Moved Permanently
Server: Apache
Powered by: W3 Total Cache/2.9.4

Raw response

HTTP/1.1 301 Moved Permanently
Date: Sun, 07 Jun 2026 03:30:07 GMT
Server: Apache
X-Redirect-By: WordPress
X-Pingback: http://dev.glowingeyegames.com/xmlrpc.php
Expires: Sun, 07 Jun 2026 04:30:07 GMT
X-Powered-By: W3 Total Cache/2.9.4
Content-Encoding: gzip
Vary: Accept-Encoding
Upgrade: h2,h2c
Connection: Upgrade
Location: https://dev.glowingeyegames.com/
Referrer-Policy: no-referrer-when-downgrade
Transfer-Encoding: chunked
Content-Type: text/html; charset=UTF-8

14
�
0

443/tcp TLS first 2026-06-07 · last 2026-06-07

TLS: TLSv1.2
Certificate for: dev.glowingeyegames.com
Issued by: R12
Valid: 2026-05-15 → 2026-08-13

Raw response

HTTP/1.1 400 Bad Request
Date: Sun, 07 Jun 2026 03:30:07 GMT
Server: Apache
Content-Length: 521
Connection: close
Content-Type: text/html; charset=iso-8859-1

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<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>
<p>Additionally, a 403 Forbidden
error was encountered while trying to use an ErrorDocument to handle the request.</p>
</body></html>

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.

Report an issue with this page