Hi mrocket,
IP reported for spam and brute-force-attacks, also quite recently;
See: https://cleantalk.org/blacklists/88.99.251.164
also listed here: https://www.abuseipdb.com/check/88.99.251.164
IP also on blocklist: https://www.virustotal.com/gui/ip-address/88.99.251.164/detection
but not flagged here: https://www.virustotal.com/gui/ip-address/88.99.251.164/relations
which is strange, isn’t it?
HTML
-server.midrocket.com/
4,084 bytes, 54 nodes
Javascript 1 (external 0, inline 1)
INLINE: (function() { let alreadyInsertedMetaTag = false function __insertDappDete
1,238 bytes
CSS 3 (external 0, inline 3)
INLINE: <!-- body { color: #444444; background-color: #EEEEEE;
742 bytes INJECTED
INLINE: @media print {#ghostery-purple-box {display:none !important}}
61 bytes INJECTED
INLINE: :root #content > #center > .dose > .dosesingle, :root #content > #right > .dose
170 bytes INJECTED
Website is insecure by default
100% of the trackers on this site could be protecting you from NSA snooping. Tell -midrocket.com to fix it.
All trackers
At least 1 third parties know you are on this webpage.
-server.midrocket.com -server.midrocket.com
Tracker could be tracking safely if this site was secure.
Vulnerable: Nginx, headers - 1.14.0
7.8
CVE-2018-16843
nginx before versions 1.15.6 and 1.14.1 has a vulnerability in the implementation of HTTP/2 that can allow for excessive memory consumption. This issue affects nginx compiled with the ngx_http_v2_module (not compiled by default) if the ‘http2’ option of the ‘listen’ directive is used in a configuration file.
7.8
CVE-2018-16844
nginx before versions 1.15.6 and 1.14.1 has a vulnerability in the implementation of HTTP/2 that can allow for excessive CPU usage. This issue affects nginx compiled with the ngx_http_v2_module (not compiled by default) if the ‘http2’ option of the ‘listen’ directive is used in a configuration file.
7.8
CVE-2018-16845
nginx before versions 1.15.6, 1.14.1 has a vulnerability in the ngx_http_mp4_module, which might allow an attacker to cause infinite loop in a worker process, cause a worker process crash, or might result in worker process memory disclosure by using a specially crafted mp4 file. The issue only affects nginx if it is built with the ngx_http_mp4_module (the module is not built by default) and the .mp4. directive is used in the configuration file. Further, the attack is only possible if an attacker is able to trigger processing of a specially crafted mp4 file with the ngx_http_mp4_module.
5.8
CVE-2019-20372
NGINX before 1.17.7, with certain error_page configurations, allows HTTP request smuggling, as demonstrated by the ability of an attacker to read unauthorized web pages in environments where NGINX is being fronted by a load balancer.
4.3
Excessive server info proliferation: nginx/1.14.0 (Ubuntu) All security headers missing - F-grade status:
https://securityheaders.com/?q=https%3A%2F%2Fserver.midrocket.com%2F
non.document.error
$ is not defined in Bootstrap.js
See: https://sitereport.netcraft.com/?url=http://server.midrocket.com ; SSL check seems OK.
Wait for a final verdict from avast team member, I do not see that server address blocked now?
See outbound links to: -http://www.ispconfig.org & -https://kpntravels.com/
polonus (volunteer 3rd part cold recon website security analyst and website error-hunter)
