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: Columbus

Region: Ohio

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

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;11.196.91.54.			IN	A

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

;; Query time: 837 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Nov 02 23:11:23 CST 2019
;; MSG SIZE  rcvd: 116
Host info
Host 54.91.196.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 54.91.196.11.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
200.150.99.251 attackbots
Invalid user rack from 200.150.99.251 port 38239
2020-01-15 04:24:12
81.21.30.180 attackbots
Unauthorized connection attempt detected from IP address 81.21.30.180 to port 2220 [J]
2020-01-15 04:49:54
106.12.178.246 attack
2019-12-11 12:55:16,111 fail2ban.actions        [802]: NOTICE  [sshd] Ban 106.12.178.246
2019-12-11 16:02:23,647 fail2ban.actions        [802]: NOTICE  [sshd] Ban 106.12.178.246
2019-12-11 22:25:21,518 fail2ban.actions        [802]: NOTICE  [sshd] Ban 106.12.178.246
...
2020-01-15 04:45:16
144.217.85.55 attackbotsspam
Invalid user pi from 144.217.85.55 port 37908
2020-01-15 04:38:39
197.62.201.148 attackbotsspam
Invalid user admin from 197.62.201.148 port 49001
2020-01-15 04:25:14
178.165.72.177 attack
GET /wp-config2.txt 404
GET /wp-config.ORG 404
GET /wp-config.php______ 404
GET /wp-config.run 404
2020-01-15 04:33:03
182.61.39.254 attackbotsspam
Unauthorized connection attempt detected from IP address 182.61.39.254 to port 2220 [J]
2020-01-15 04:30:56
129.150.70.20 attackspambots
Invalid user tec from 129.150.70.20 port 51091
2020-01-15 04:41:08
106.12.106.78 attackspam
Unauthorized connection attempt detected from IP address 106.12.106.78 to port 2220 [J]
2020-01-15 04:45:45
77.81.230.143 attackbots
Unauthorized connection attempt detected from IP address 77.81.230.143 to port 2220 [J]
2020-01-15 04:51:10
213.181.80.168 attackbotsspam
Invalid user admin from 213.181.80.168 port 43448
2020-01-15 04:21:47
178.127.221.151 attackbots
Invalid user admin from 178.127.221.151 port 35929
2020-01-15 04:33:52
62.210.37.82 attackbotsspam
Invalid user pi from 62.210.37.82 port 43798
2020-01-15 04:52:04
103.83.157.212 attack
Invalid user ubuntu from 103.83.157.212 port 41952
2020-01-15 04:47:09
190.117.62.241 attackspam
Unauthorized connection attempt detected from IP address 190.117.62.241 to port 2220 [J]
2020-01-15 04:28:25

Recently Reported IPs

219.59.162.72 51.157.10.197 211.7.44.158 140.199.221.57
118.9.77.211 113.205.208.189 81.248.180.163 104.78.126.143
229.249.66.79 165.142.125.129 54.142.20.14 152.178.72.44
138.15.31.243 46.243.237.189 95.6.168.197 127.169.117.45
3.9.169.235 58.217.165.29 88.253.244.2 16.53.125.137