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: South Africa

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

;; QUESTION SECTION:
;102.134.180.132.		IN	A

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

;; Query time: 23 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Feb 26 01:53:58 CST 2022
;; MSG SIZE  rcvd: 108
Host info
Host 132.180.134.102.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 132.180.134.102.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
122.55.19.115 attackspambots
Jan 20 08:39:06 icinga sshd[19995]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.55.19.115 
Jan 20 08:39:08 icinga sshd[19995]: Failed password for invalid user administrator from 122.55.19.115 port 33009 ssh2
Jan 20 08:40:18 icinga sshd[21181]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.55.19.115 
...
2020-01-20 17:05:14
195.191.88.76 attack
Jan 20 04:52:34 unicornsoft sshd\[21879\]: Invalid user comfort from 195.191.88.76
Jan 20 04:52:34 unicornsoft sshd\[21879\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=195.191.88.76
Jan 20 04:52:35 unicornsoft sshd\[21879\]: Failed password for invalid user comfort from 195.191.88.76 port 50220 ssh2
2020-01-20 17:00:56
120.202.21.189 attackbots
Jan 20 07:24:35 server sshd\[15576\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=120.202.21.189  user=root
Jan 20 07:24:37 server sshd\[15576\]: Failed password for root from 120.202.21.189 port 54420 ssh2
Jan 20 07:52:58 server sshd\[22984\]: Invalid user labs from 120.202.21.189
Jan 20 07:52:58 server sshd\[22984\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=120.202.21.189 
Jan 20 07:53:00 server sshd\[22984\]: Failed password for invalid user labs from 120.202.21.189 port 59046 ssh2
...
2020-01-20 16:52:16
50.5.52.98 attack
port scan and connect, tcp 1433 (ms-sql-s)
2020-01-20 16:38:28
125.47.65.38 attack
port scan and connect, tcp 1433 (ms-sql-s)
2020-01-20 16:50:29
69.17.158.101 attack
detected by Fail2Ban
2020-01-20 17:07:50
222.186.173.226 attackspam
Jan 20 13:57:14 gw1 sshd[30021]: Failed password for root from 222.186.173.226 port 3225 ssh2
Jan 20 13:57:29 gw1 sshd[30021]: error: maximum authentication attempts exceeded for root from 222.186.173.226 port 3225 ssh2 [preauth]
...
2020-01-20 16:58:28
129.211.130.37 attackspam
21 attempts against mh-ssh on cloud.magehost.pro
2020-01-20 17:12:26
213.59.144.39 attackbots
Jan 19 19:39:59 kapalua sshd\[30806\]: Invalid user vnc from 213.59.144.39
Jan 19 19:39:59 kapalua sshd\[30806\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=213.59.144.39
Jan 19 19:40:01 kapalua sshd\[30806\]: Failed password for invalid user vnc from 213.59.144.39 port 53352 ssh2
Jan 19 19:46:01 kapalua sshd\[31246\]: Invalid user jf from 213.59.144.39
Jan 19 19:46:01 kapalua sshd\[31246\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=213.59.144.39
2020-01-20 16:42:06
74.219.184.26 attack
Wordpress Admin Login attack
2020-01-20 16:50:58
196.213.111.58 attack
$f2bV_matches
2020-01-20 16:35:48
144.91.113.69 attackbots
Unauthorized connection attempt detected from IP address 144.91.113.69 to port 2220 [J]
2020-01-20 17:11:39
62.4.52.59 attack
Unauthorized connection attempt detected from IP address 62.4.52.59 to port 23 [J]
2020-01-20 17:04:27
36.83.219.214 attackbots
Attempt to attack host OS, exploiting network vulnerabilities, on 20-01-2020 06:50:17.
2020-01-20 16:56:03
222.186.30.76 attackbots
Unauthorized connection attempt detected from IP address 222.186.30.76 to port 22 [J]
2020-01-20 16:40:00

Recently Reported IPs

102.134.169.244 102.134.180.142 102.134.180.175 102.134.180.185
102.134.180.158 102.134.180.180 102.134.180.182 103.36.10.105
102.134.180.193 102.134.180.189 125.239.115.40 102.134.180.201
102.134.180.198 102.134.180.186 102.134.180.203 102.134.180.23
102.134.180.195 102.134.180.218 102.134.180.213 102.134.180.247