As of our latest check on 2026-07-21, 67.222.153.33 (DFW Datacenter, AS30277, United States) had 4 open ports (21, 22, 80, 443) and 33 known CVEs.
Known CVEs on this host
4open ports
0names pointing here
33known CVEs
0known exploited
Open ports and CVEs as of our latest check of this host, 2026-07-21.
CVEs by severity: CRITICAL 1HIGH 7MEDIUM 14LOW 11
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: 31 on a distribution build — the fix may be backported (openssh 5.3). See them
Not a Tor relay, not a VPN or privacy relay address, and not on a current public blocklist.
Services (4)
21/tcpFTPfirst 2026-07-21 · last 2026-07-21
Banner
220---------- Welcome to Pure-FTPd [privsep] [TLS] ----------
220-You are user number 6 of 50 allowed.
220-Local time is now 06:30. Server port: 21.
220-This is a private system - No anonymous logi
Raw response
220---------- Welcome to Pure-FTPd [privsep] [TLS] ----------
220-You are user number 1 of 50 allowed.
220-Local time is now 06:27. Server port: 21.
220-This is a private system - No anonymous login
220-IPv6 connections are also welcome on this server.
220 You will be disconnected after 15 minutes of inactivity.
22/tcpSSHOpenSSH_5.333 CVEsfirst 2026-07-21 · last 2026-07-21
Server
SSH-2.0-OpenSSH_5.3
Host key
ssh-rsa 4a5c5d7c1acaccd4…
Raw response
SSH-2.0-OpenSSH_5.3
80/tcpHTTPnginx adminfirst 2026-07-21 · last 2026-07-21
Status
500 Internal Server Error
Title
500 Internal Server Error
Server
nginx admin
Raw response
HTTP/1.1 500 Internal Server Error
Server: nginx admin
Date: Tue, 21 Jul 2026 12:27:31 GMT
Content-Type: text/html; charset=iso-8859-1
Content-Length: 745
Connection: keep-alive
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>500 Internal Server Error</title>
</head><body>
<h1>Internal Server Error</h1>
<p>The server encountered an internal error or
misconfiguration and was unable to complete
your request.</p>
<p>Please contact the server administrator at
[email protected] to inform them of the time this error occurred,
and the actions you performed just before this error.</p>
<p>More information about this error may be available
in the server error log.</p>
<p>Additionally, a 500 Internal Server Error
error was encountered while trying to use an ErrorDocument to handle the request.</p>
<hr>
<address>Apache Server at 67.222.153.33 Port 80</address>
</body></html>
HTTP/1.1 400 Bad Request
Date: Tue, 21 Jul 2026 12:27:31 GMT
Server: Apache
Content-Length: 561
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>
<p>Additionally, a 400 Bad Request
error was encountered while trying to use an ErrorDocument to handle the request.</p>
<hr>
<address>Apache Server at marketing.proximityaware.com Port 80</address>
</body></html>
Vulnerabilities
Distribution build — the fix may be backported (31)
These CVEs were matched on software built by an operating-system distribution whose package revision the service does not show. Distributions often fix a flaw without changing the upstream version number, so whether this build is affected cannot be told from its version. They are not counted.
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.