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: DoD Network Information Center

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

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

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

;; Query time: 2 msec
;; SERVER: 67.207.67.2#53(67.207.67.2)
;; WHEN: Fri Aug 02 01:41:15 CST 2019
;; MSG SIZE  rcvd: 119
Host info
Host 140.179.121.199.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		67.207.67.2
Address:	67.207.67.2#53

** server can't find 140.179.121.199.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
62.234.110.91 attackbotsspam
Jun 30 18:00:53 icinga sshd[34958]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.234.110.91 
Jun 30 18:00:55 icinga sshd[34958]: Failed password for invalid user liming from 62.234.110.91 port 47094 ssh2
Jun 30 18:29:31 icinga sshd[16005]: Failed password for root from 62.234.110.91 port 48230 ssh2
...
2020-07-01 10:03:06
27.50.169.167 attackspambots
2020-06-30T15:16:55.532850upcloud.m0sh1x2.com sshd[30202]: Invalid user sandi from 27.50.169.167 port 47120
2020-07-01 09:46:12
109.167.200.10 attackbots
Multiple SSH authentication failures from 109.167.200.10
2020-07-01 09:30:13
139.162.121.165 attack
 TCP (SYN) 139.162.121.165:51287 -> port 8080, len 40
2020-07-01 09:42:13
45.143.223.130 attackbotsspam
T: f2b postfix aggressive 3x
2020-07-01 10:13:08
94.154.159.137 attack
 TCP (SYN,ACK) 94.154.159.137:33355 -> port 36093, len 44
2020-07-01 09:26:58
113.54.198.114 attackspam
 TCP (SYN) 113.54.198.114:40420 -> port 23, len 44
2020-07-01 09:40:43
13.90.200.181 attackbotsspam
2020-06-30T18:23:32.196693ks3355764 sshd[30938]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=13.90.200.181  user=root
2020-06-30T18:23:34.779991ks3355764 sshd[30938]: Failed password for root from 13.90.200.181 port 24444 ssh2
...
2020-07-01 09:55:32
186.147.129.110 attack
Jul  1 02:53:48 localhost sshd[4160887]: Invalid user public from 186.147.129.110 port 57922
...
2020-07-01 09:38:46
189.4.151.102 attackbotsspam
Multiple SSH authentication failures from 189.4.151.102
2020-07-01 10:08:49
209.17.97.58 attack
Automatic report - Banned IP Access
2020-07-01 09:46:26
190.0.159.86 attackbotsspam
Jun 30 19:04:54 master sshd[28518]: Failed password for invalid user wp-user from 190.0.159.86 port 59883 ssh2
Jun 30 19:27:48 master sshd[30370]: Failed password for root from 190.0.159.86 port 59456 ssh2
Jun 30 19:41:15 master sshd[30903]: Failed password for invalid user atendimento from 190.0.159.86 port 59369 ssh2
2020-07-01 09:31:59
122.160.233.137 attackbotsspam
Invalid user student07 from 122.160.233.137 port 39784
2020-07-01 10:03:52
202.72.243.198 attackspam
Multiple SSH authentication failures from 202.72.243.198
2020-07-01 10:05:50
106.12.59.245 attackbotsspam
Multiple SSH authentication failures from 106.12.59.245
2020-07-01 10:12:21

Recently Reported IPs

197.234.132.115 63.19.19.191 177.223.48.74 73.254.116.87
38.211.28.189 175.100.20.254 203.75.63.141 223.148.148.70
97.134.0.124 47.38.166.141 167.23.161.50 141.117.168.9
161.50.247.82 63.221.250.244 193.29.13.135 75.165.196.3
41.133.37.189 132.232.94.119 84.63.242.33 197.162.10.65