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:
IP Type Details Datetime
139.180.134.138 attackspambots
Nov  3 11:18:56 sachi sshd\[379\]: Invalid user com from 139.180.134.138
Nov  3 11:18:56 sachi sshd\[379\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.180.134.138
Nov  3 11:18:58 sachi sshd\[379\]: Failed password for invalid user com from 139.180.134.138 port 33649 ssh2
Nov  3 11:23:19 sachi sshd\[758\]: Invalid user 123456 from 139.180.134.138
Nov  3 11:23:19 sachi sshd\[758\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.180.134.138
2019-11-04 05:30:10
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 139.180.134.44
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 57370
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;139.180.134.44.			IN	A

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

;; Query time: 58 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 12:02:14 CST 2022
;; MSG SIZE  rcvd: 107
Host info
44.134.180.139.in-addr.arpa domain name pointer 139.180.134.44.vultr.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
44.134.180.139.in-addr.arpa	name = 139.180.134.44.vultr.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
43.249.192.94 attack
Unauthorized connection attempt detected from IP address 43.249.192.94 to port 1433 [T]
2020-05-09 02:33:10
120.15.91.6 attackspambots
Unauthorized connection attempt detected from IP address 120.15.91.6 to port 8080 [T]
2020-05-09 02:55:41
122.138.90.63 attackbotsspam
Unauthorized connection attempt detected from IP address 122.138.90.63 to port 23 [T]
2020-05-09 02:53:57
177.86.68.80 attack
Attempted connection to port 23.
2020-05-09 02:48:04
112.193.170.186 attackspambots
Unauthorized connection attempt detected from IP address 112.193.170.186 to port 1133 [T]
2020-05-09 03:00:52
164.52.24.162 attack
Unauthorized connection attempt detected from IP address 164.52.24.162 to port 443 [T]
2020-05-09 02:49:05
187.243.242.166 attackbots
Unauthorized connection attempt detected from IP address 187.243.242.166 to port 445 [T]
2020-05-09 02:43:40
51.15.191.81 attack
Unauthorized connection attempt detected from IP address 51.15.191.81 to port 4567
2020-05-09 03:09:54
122.144.131.141 attack
Unauthorized connection attempt detected from IP address 122.144.131.141 to port 8088 [T]
2020-05-09 02:53:23
60.31.152.59 attackspam
Unauthorized connection attempt detected from IP address 60.31.152.59 to port 23 [T]
2020-05-09 03:09:37
103.145.12.95 attack
REQUESTED PAGE: //a2billing/customer/templates/default/footer.tpl
2020-05-09 03:04:08
210.56.8.83 attackbots
Unauthorized connection attempt detected from IP address 210.56.8.83 to port 1433 [T]
2020-05-09 02:39:31
77.222.107.128 attackspambots
Unauthorized connection attempt detected from IP address 77.222.107.128 to port 445 [T]
2020-05-09 03:08:45
184.105.139.68 attackspam
Unauthorized connection attempt detected from IP address 184.105.139.68 to port 873
2020-05-09 02:44:59
196.52.43.115 attackspam
...
2020-05-09 02:41:55

Recently Reported IPs

139.180.133.45 139.18.16.133 139.180.129.1 139.180.135.49
139.180.135.78 139.180.136.180 139.180.138.58 139.180.139.134
139.180.138.78 139.180.140.77 139.180.140.210 139.180.141.198
139.180.141.152 139.180.153.12 139.180.155.132 139.180.156.103
139.180.143.68 139.180.157.226 139.180.156.24 139.180.157.168