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

;; QUESTION SECTION:
;11.157.149.156.			IN	A

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

;; Query time: 19 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Jan 07 04:21:48 CST 2024
;; MSG SIZE  rcvd: 107
Host info
Host 156.149.157.11.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 156.149.157.11.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
198.108.66.32 attackspam
Unauthorized connection attempt detected from IP address 198.108.66.32 to port 502
2019-12-29 03:39:10
188.226.171.36 attackbots
2019-12-28T14:52:14.391293shield sshd\[6694\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.226.171.36  user=root
2019-12-28T14:52:15.792972shield sshd\[6694\]: Failed password for root from 188.226.171.36 port 53000 ssh2
2019-12-28T14:55:42.941359shield sshd\[7521\]: Invalid user fritz from 188.226.171.36 port 56564
2019-12-28T14:55:42.945548shield sshd\[7521\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.226.171.36
2019-12-28T14:55:45.235283shield sshd\[7521\]: Failed password for invalid user fritz from 188.226.171.36 port 56564 ssh2
2019-12-29 03:43:11
222.106.6.80 attack
Unauthorized connection attempt detected from IP address 222.106.6.80 to port 5555
2019-12-29 03:36:22
39.98.154.31 attackbotsspam
Unauthorized connection attempt detected from IP address 39.98.154.31 to port 355
2019-12-29 03:34:18
77.42.94.231 attack
Unauthorized connection attempt detected from IP address 77.42.94.231 to port 23
2019-12-29 03:06:33
200.0.91.29 attackspam
Unauthorized connection attempt detected from IP address 200.0.91.29 to port 3389
2019-12-29 03:38:11
161.10.238.10 attack
Unauthorized connection attempt detected from IP address 161.10.238.10 to port 1433
2019-12-29 03:22:29
37.202.20.89 attack
Unauthorized connection attempt detected from IP address 37.202.20.89 to port 1433
2019-12-29 03:12:27
170.246.17.189 attackbotsspam
Unauthorized connection attempt detected from IP address 170.246.17.189 to port 8000
2019-12-29 03:21:27
66.42.108.136 attackspam
Unauthorized connection attempt detected from IP address 66.42.108.136 to port 445
2019-12-29 03:31:27
88.250.134.236 attackbots
Unauthorized connection attempt detected from IP address 88.250.134.236 to port 23
2019-12-29 03:27:37
192.81.79.63 attackbotsspam
Unauthorized connection attempt detected from IP address 192.81.79.63 to port 445
2019-12-29 03:16:54
73.57.199.231 attackbotsspam
Unauthorized connection attempt detected from IP address 73.57.199.231 to port 88
2019-12-29 03:28:10
189.190.239.218 attackspambots
Unauthorized connection attempt detected from IP address 189.190.239.218 to port 9090
2019-12-29 03:42:40
189.110.223.163 attackspambots
Unauthorized connection attempt detected from IP address 189.110.223.163 to port 445
2019-12-29 03:42:57

Recently Reported IPs

11.156.90.150 11.156.217.67 11.157.10.6 11.16.246.9
11.156.227.18 11.156.60.66 11.156.182.7 11.156.214.7
11.157.235.185 11.159.120.82 11.157.191.22 11.157.219.87
11.157.209.30 11.156.69.196 11.157.157.136 11.156.186.184
11.159.6.167 11.156.218.16 11.157.0.193 11.156.223.204