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

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 <<>> 18.157.139.212
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 23102
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;18.157.139.212.			IN	A

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

;; Query time: 18 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 18:48:39 CST 2022
;; MSG SIZE  rcvd: 107
Host info
212.139.157.18.in-addr.arpa domain name pointer ec2-18-157-139-212.eu-central-1.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
212.139.157.18.in-addr.arpa	name = ec2-18-157-139-212.eu-central-1.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
178.32.44.233 attackspambots
2020-03-24T17:05:04.268935vps773228.ovh.net sshd[32183]: Invalid user lty from 178.32.44.233 port 40710
2020-03-24T17:05:04.279750vps773228.ovh.net sshd[32183]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=ip233.ip-178-32-44.eu
2020-03-24T17:05:04.268935vps773228.ovh.net sshd[32183]: Invalid user lty from 178.32.44.233 port 40710
2020-03-24T17:05:06.671406vps773228.ovh.net sshd[32183]: Failed password for invalid user lty from 178.32.44.233 port 40710 ssh2
2020-03-24T17:05:36.289019vps773228.ovh.net sshd[32408]: Invalid user lty from 178.32.44.233 port 53266
...
2020-03-25 01:04:33
188.166.251.87 attackspambots
20 attempts against mh-ssh on cloud
2020-03-25 01:34:13
92.44.7.162 attack
1585040329 - 03/24/2020 09:58:49 Host: 92.44.7.162/92.44.7.162 Port: 445 TCP Blocked
2020-03-25 00:54:46
156.202.208.23 attack
156.202.208.23 - - [24/Mar/2020:13:34:14 +0100] "POST /wp-login.php HTTP/1.0" 200 2504 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
156.202.208.23 - - [24/Mar/2020:13:34:15 +0100] "POST /wp-login.php HTTP/1.0" 200 2485 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
...
2020-03-25 00:53:29
138.197.166.110 attackspam
Mar 23 11:45:31 hosting180 sshd[7316]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.197.166.110
Mar 23 11:45:31 hosting180 sshd[7316]: Invalid user kuroiwa from 138.197.166.110 port 41686
Mar 23 11:45:33 hosting180 sshd[7316]: Failed password for invalid user kuroiwa from 138.197.166.110 port 41686 ssh2
...
2020-03-25 00:53:46
118.100.181.154 attack
Invalid user yy from 118.100.181.154 port 10982
2020-03-25 00:49:34
89.36.220.145 attack
20 attempts against mh-ssh on cloud
2020-03-25 01:24:33
46.38.145.6 attackbots
[24/Mar/2020 04:48:32] Client with IP address 46.38.145.6 has no reverse DNS entry, connection rejected before SMTP greeting
[24/Mar/2020 04:49:46] Client with IP address 46.38.145.6 has no reverse DNS entry, connection rejected before SMTP greeting
[24/Mar/2020 04:50:59] Client with IP address 46.38.145.6 has no reverse DNS entry, connection rejected before SMTP greeting
[24/Mar/2020 04:52:13] Client with IP address 46.38.145.6 has no reverse DNS entry, connection rejected before SMTP greeting
[24/Mar/2020 04:53:27] Client with IP address 46.38.145.6 has no reverse DNS entry, connection rejected before SMTP greeting
[24/Mar/2020 04:54:41] Client with IP address 46.38.145.6 has no reverse DNS entry, connection rejected before SMTP greeting
[24/Mar/2020 04:55:55] Client with IP address 46.38.145.6 has no reverse DNS entry, connection rejected before SMTP greeting
2020-03-25 01:33:35
42.114.199.82 attackspambots
1585040320 - 03/24/2020 09:58:40 Host: 42.114.199.82/42.114.199.82 Port: 445 TCP Blocked
2020-03-25 01:05:48
113.168.68.35 attackspambots
Honeypot attack, port: 445, PTR: static.vnpt.vn.
2020-03-25 01:23:34
107.170.227.141 attackbotsspam
SSH Login Bruteforce
2020-03-25 01:19:46
80.145.38.55 attackbots
2020-03-24T09:47:52.872465vt3.awoom.xyz sshd[32072]: Invalid user avon from 80.145.38.55 port 40248
2020-03-24T09:47:52.875803vt3.awoom.xyz sshd[32072]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=p50912637.dip0.t-ipconnect.de
2020-03-24T09:47:52.872465vt3.awoom.xyz sshd[32072]: Invalid user avon from 80.145.38.55 port 40248
2020-03-24T09:47:54.818115vt3.awoom.xyz sshd[32072]: Failed password for invalid user avon from 80.145.38.55 port 40248 ssh2


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=80.145.38.55
2020-03-25 01:16:44
51.159.56.164 attackbotsspam
Mar 24 14:28:00 santamaria sshd\[31325\]: Invalid user jira from 51.159.56.164
Mar 24 14:28:00 santamaria sshd\[31325\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.159.56.164
Mar 24 14:28:01 santamaria sshd\[31325\]: Failed password for invalid user jira from 51.159.56.164 port 39260 ssh2
...
2020-03-25 00:57:30
183.102.7.173 attackspam
port scan and connect, tcp 23 (telnet)
2020-03-25 01:28:14
202.168.71.146 attackbots
$f2bV_matches
2020-03-25 01:20:04

Recently Reported IPs

18.157.100.17 18.156.75.15 18.157.114.133 18.157.162.200
18.157.150.37 18.157.128.158 18.157.168.67 18.157.195.203
18.157.135.242 18.157.206.63 18.157.230.29 18.157.253.218
18.157.207.232 18.157.226.196 18.157.170.201 18.157.191.166
18.157.86.172 18.157.254.159 18.158.1.232 18.158.108.166