Host
31.24.78.222
As of our latest check on 2026-05-18, 31.24.78.222 (Mediateknik i Varberg AB, AS48803, Sweden) had 6 open ports (22, 25, 80, 443, 587, 993) and 40 known CVEs, 1 known to be exploited.
Known CVEs on this host
Open ports and CVEs as of our latest check of this host, 2026-05-18.
CVEs by severity: CRITICAL 5 HIGH 22 MEDIUM 11 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
All of them on a software version from an earlier observation: a service of that kind is open now.
Not counted: 2 only affect a particular platform; this host's is not known (http_server 2.4.58). See them
- Network
- Mediateknik i Varberg AB AS48803
- Open ports
- 22, 25, 80, 443, 587, 993 · at our latest check, 2026-05-18
- Location
- Sweden SE
- Hostname
- mail1.membit.se · reverse DNS, checked 2026-10-04
- Route
- 31.24.72.0/21 · announced by Mediateknik i Varberg AB AS48803 RPKI valid
- Organisation
- Mediateknik i Varberg AB
- Registry network
- MEDIATEKNIKVARBERG-NET01 · 31.24.78.0 - 31.24.78.255 · RIPE
- Abuse contact
- [email protected] · for MEDIATEKNIKVARBERG-NET01
- Hostnames
- mail1.membit.se, membit.net, www.membit.net
- First seen
- 2026-05-18 06:40 UTC
- Last seen alive
- 2026-05-18 06:41 UTC
- Hosted domains
- 9 names point here
Reputation
Not a Tor relay, not a VPN or privacy relay address, and not on a current public blocklist.
Vulnerabilities
Only affects certain platforms (2)
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: HIGH 2
| CVE | Software |
|---|---|
| CVE-2024-40898 HIGH 7.5 | http_server 2.4.58 |
| CVE-2024-43394 HIGH 7.5 | http_server 2.4.58 |
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.
Hostnames pointing to this address
9 names · as answered by each domain's own name servers