Must be a valid IPv4 or IPv6 ip address, e.g. 127.0.0.1 or 2001:DB8:0:0:8:800:200C:417A
Basic Info

City: unknown

Region: unknown

Country: United States of America (the)

Internet Service Provider: unknown

Hostname: unknown

Organization: unknown

Usage Type: unknown

Comments:
No discussion about this IP yet. Click above link to make one.
Comments on same subnet:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 30.118.100.164
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 8824
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;30.118.100.164.			IN	A

;; AUTHORITY SECTION:
.			30	IN	SOA	a.root-servers.net. nstld.verisign-grs.com. 2025012800 1800 900 604800 86400

;; Query time: 34 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Jan 28 20:03:09 CST 2025
;; MSG SIZE  rcvd: 107
Host info
Host 164.100.118.30.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 164.100.118.30.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
85.147.234.46 attack
IP Ban Report : https://help-dysk.pl/wordpress-firewall-plugins/ip/85.147.234.46/ 
 NL - 1H : (20)  
 Protection Against DDoS WordPress plugin :  
 "odzyskiwanie danych help-dysk" 
 IP Address Ranges by Country : NL 
 NAME ASN : ASN33915 
 
 IP : 85.147.234.46 
 
 CIDR : 85.147.128.0/17 
 
 PREFIX COUNT : 142 
 
 UNIQUE IP COUNT : 3653888 
 
 
 WYKRYTE ATAKI Z ASN33915 :  
  1H - 1 
  3H - 1 
  6H - 1 
 12H - 2 
 24H - 2 
 
 DateTime : 2019-10-17 05:52:27 
 
 INFO :  HACK ! - Looking for resource vulnerabilities Scan Detected and Blocked by ADMIN  - data recovery
2019-10-17 15:17:43
188.166.117.213 attack
$f2bV_matches
2019-10-17 15:20:27
114.67.76.63 attack
(sshd) Failed SSH login from 114.67.76.63 (-): 5 in the last 3600 secs
2019-10-17 15:16:51
177.220.205.70 attackspambots
Oct 17 08:05:33 microserver sshd[13045]: Failed password for root from 177.220.205.70 port 9347 ssh2
Oct 17 08:09:56 microserver sshd[13293]: Invalid user mig from 177.220.205.70 port 31565
Oct 17 08:09:56 microserver sshd[13293]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=177.220.205.70
Oct 17 08:09:58 microserver sshd[13293]: Failed password for invalid user mig from 177.220.205.70 port 31565 ssh2
Oct 17 08:22:54 microserver sshd[15232]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=177.220.205.70  user=root
Oct 17 08:22:56 microserver sshd[15232]: Failed password for root from 177.220.205.70 port 51531 ssh2
Oct 17 08:27:17 microserver sshd[15859]: Invalid user burke from 177.220.205.70 port 38218
Oct 17 08:27:17 microserver sshd[15859]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=177.220.205.70
Oct 17 08:27:20 microserver sshd[15859]: Failed password for invalid user burke from
2019-10-17 15:08:25
203.148.53.227 attackspam
Oct 15 01:07:26 uapps sshd[31261]: Address 203.148.53.227 maps to static-ip-227-53-148-203.rev.dyxnet.com, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Oct 15 01:07:28 uapps sshd[31261]: Failed password for invalid user finn from 203.148.53.227 port 58975 ssh2
Oct 15 01:07:28 uapps sshd[31261]: Received disconnect from 203.148.53.227: 11: Bye Bye [preauth]
Oct 15 01:13:03 uapps sshd[31375]: Address 203.148.53.227 maps to static-ip-227-53-148-203.rev.dyxnet.com, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Oct 15 01:13:03 uapps sshd[31375]: User r.r from 203.148.53.227 not allowed because not listed in AllowUsers
Oct 15 01:13:03 uapps sshd[31375]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.148.53.227  user=r.r


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=203.148.53.227
2019-10-17 15:04:39
148.70.24.20 attack
Oct 17 08:59:44 icinga sshd[32063]: Failed password for root from 148.70.24.20 port 46560 ssh2
...
2019-10-17 15:12:41
142.93.99.56 attackbotsspam
WordPress login Brute force / Web App Attack on client site.
2019-10-17 15:06:06
77.40.3.223 attackbots
10/17/2019-06:29:11.988447 77.40.3.223 Protocol: 6 SURICATA SMTP tls rejected
2019-10-17 15:22:41
45.79.110.218 attackbots
" "
2019-10-17 15:09:28
103.114.48.4 attackbots
Invalid user user from 103.114.48.4 port 47090
2019-10-17 15:35:20
41.207.182.133 attack
SSH Brute-Forcing (ownc)
2019-10-17 15:14:45
165.227.49.242 attackspambots
Invalid user admin from 165.227.49.242 port 53813
2019-10-17 15:39:44
182.18.38.69 attackbotsspam
Invalid user vagrant from 182.18.38.69 port 12961
2019-10-17 15:19:41
129.154.67.65 attackbots
2019-10-17T03:51:54.075392abusebot-6.cloudsearch.cf sshd\[31446\]: Invalid user gq from 129.154.67.65 port 13581
2019-10-17 15:34:12
193.112.58.212 attackbotsspam
Oct 16 19:01:20 hanapaa sshd\[6115\]: Invalid user vps from 193.112.58.212
Oct 16 19:01:20 hanapaa sshd\[6115\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.112.58.212
Oct 16 19:01:22 hanapaa sshd\[6115\]: Failed password for invalid user vps from 193.112.58.212 port 38414 ssh2
Oct 16 19:07:22 hanapaa sshd\[6557\]: Invalid user vagrant from 193.112.58.212
Oct 16 19:07:22 hanapaa sshd\[6557\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.112.58.212
2019-10-17 15:07:42

Recently Reported IPs

237.19.0.184 42.99.134.128 23.58.83.189 153.195.66.89
138.103.159.96 107.162.76.131 74.72.55.109 128.82.229.140
207.89.187.150 135.97.18.3 108.68.107.19 71.192.66.239
12.127.34.193 201.164.196.169 75.169.78.0 55.207.180.63
198.71.45.47 91.230.223.8 84.116.83.210 153.29.89.84